WCAG 3.2.3: Consistent Navigation
Level AAQuick answer: Repeated navigation should stay in the same relative order across the store so users can build familiarity.
What This Means
On ecommerce sites, Consistent Navigation usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like header nav order changes between homepage, pdps, and help center. or mobile menu puts account before search on some templates and after search on others., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Header nav order changes between homepage, PDPs, and help center.
- Mobile menu puts account before search on some templates and after search on others.
- Footer policy links swap order by campaign page.
- Checkout side navigation differs from account navigation patterns without reason.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Keep repeated nav items in a stable order across templates.
- Only change navigation order when the change serves a strong user need.
- Use shared navigation components rather than per-template custom menus.
- Audit CMS-managed landing pages that often drift from the system menu order.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
<nav><a>Shop</a><a>Help</a><a>Account</a></nav>
<!-- After -->
<nav><a>Shop</a><a>Account</a><a>Help</a></nav>FAQ
What is WCAG 3.2.3?
Repeated navigation should stay in the same relative order across the store so users can build familiarity.
How does WCAG 3.2.3 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with header nav order changes between homepage, pdps, and help center. and mobile menu puts account before search on some templates and after search on others. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 3.2.3 violations?
Start by auditing the live storefront, then Keep repeated nav items in a stable order across templates.; Only change navigation order when the change serves a strong user need.; Use shared navigation components rather than per-template custom menus.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 3.2.3 → Free ADA Compliance Scan