Success Criteria

WCAG 3.2.3 Consistent Navigation

Success Criterion 3.2.3 requires that navigational mechanisms repeated across multiple pages occur in the same relative order each time they appear, unless the user has deliberately changed that order themselves. It's a Level AA criterion under Guideline 3.2 (Predictable).

Why consistency matters for navigation specifically

A user builds a mental model of "where things are" after visiting a few pages of a site — the main nav is first, then a search box, then a secondary utility menu. If that relative order shifts unpredictably from page to page (search moves from second to fourth position, a utility menu appears before the main nav on some pages but after on others), the user has to re-locate familiar controls on every single page rather than relying on memorized muscle memory — a much larger burden for screen reader and keyboard users navigating linearly than for a sighted user who can visually re-scan a page quickly.

What "relative order" means precisely

This is about relative sequence, not exact pixel position — navigation items can be styled differently, or a page can insert unique, page-specific content between or around the repeated elements. What's required is that if a page has a global nav, then a search box, then a utility menu, every other page with that same set of elements presents them in that same relative sequence — global nav, then search, then utility menu — even if additional page-specific elements appear elsewhere.

This is a differentiator opportunity for automated tools

Checking this criterion requires comparing structure across multiple pages of the same site — a genuinely multi-page analysis, not something a single-page scan can verify in isolation. This is one of a handful of WCAG criteria (alongside Consistent Identification and Consistent Help) that specifically rewards cross-page comparison rather than per-page checking, making it a natural area where a multi-page scanning tool can catch issues a single-page audit would miss entirely.

Common causes of failure

• A/B testing or gradual rollouts that leave some pages on an older navigation layout while others have a newer one
• CMS templates that drifted apart over time as different authors edited different page templates independently
• Third-party embedded widgets that insert their own navigation-like elements inconsistently across pages

Common questions

What is WCAG 3.2.3?

A Level AA criterion requiring repeated navigation (menus, search, breadcrumbs) to stay in the same relative order across pages, so users can predict where things are.

Does it forbid changing navigation?

No — it requires a consistent order. Users can still trigger changes themselves, and you can add page-specific items, as long as the shared order is stable.

How is 3.2.3 different from 3.2.4?

3.2.3 is about the order of repeated navigation; 3.2.4 is about consistently identifying components that have the same function.