People learn how to use a website through repetition. When navigation appears in different orders on different pages, users must repeatedly reorient themselves instead of relying on memory. This slows navigation and increases errors, and for some users, it can make a site difficult or impossible to use.
Users who rely on screen readers, keyboard navigation, screen magnification, or cognitive strategies depend on predictable structure. When navigation reshuffles or changes order without user control, finding familiar links becomes harder and more mentally demanding.
WCAG addresses this by requiring that navigation repeated across pages remains consistent.
Why Level AA Matters
WCAG success criteria are organised under principles and guidelines. Each success criterion has a conformance level:
- Level A – basic accessibility
- Level AA – expected and commonly required
- Level AAA – advanced support
Level AA is the most widely required level in laws, policies, and procurement standards.
Consistent Navigation (3.2.3) sits under Guideline 3.2: Predictable, which focuses on ensuring that interfaces behave in ways users can anticipate.
WCAG Success Criterion
3.2.3 Consistent Navigation (Level AA)
Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
This requirement applies to navigation that appears on more than one page.
What Counts as “Navigational Mechanisms”
Navigational mechanisms are ways users move around a site, including:
- Primary navigation menus
- Secondary or sub-navigation menus
- Breadcrumbs
- Search fields that are part of site navigation
- Skip links (for example, “Skip to main content”)
- Footer navigation
The criterion applies only to navigation that is repeated across pages.
Page-specific or contextual navigation is handled differently (see below).
What “Consistent” Means in Practice
Consistency refers to relative order, not identical layout or appearance.
In practice, this means:
- Navigation items appear in the same sequence across pages
- Key navigation controls appear in predictable locations
- Users can rely on memory to find items again
It does not mean:
- Every page must look identical
- Navigation can never expand or collapse
- Contextual or page-specific navigation is forbidden
WCAG allows flexibility, as long as repeated navigation stays predictable.
Plain-Language Requirements of SC 3.2.3
If navigation appears on multiple pages:
- It must appear in the same relative order each time
- Its placement must be predictable for users
- Any reordering must happen only if the user initiates it
Users should not have to re-learn where navigation items are on each page.
Contextual vs Global Navigation
Understanding this distinction prevents many false positives.
Global navigation (subject to 3.2.3):
- Main site menus
- Repeated headers or footers
- Persistent search controls
Contextual navigation (allowed to vary):
- Section-specific menus
- In-page tables of contents
- Navigation tied to a specific task or workflow
Problems occur when global navigation changes order based on page context.
Relative Order Means DOM Order, Not Just Visual Order
This is a critical technical point.
- Screen readers follow DOM order, not visual layout
- CSS reordering (
order,flex-direction, grid placement) can create hidden failures - Responsive layouts must preserve logical sequence across breakpoints
A navigation menu that looks consistent but has a different DOM order on different pages can still fail this criterion.
Realistic Examples
Reordered global navigation (failure)
- Page A navigation order: Home → Services → Pricing → Contact
- Page B navigation order: Home → Contact → Services → Pricing
Even though all links exist, users cannot rely on memory.
Consistent order with expansion (pass)
- Navigation always lists: Home → Services → Pricing → Contact
- Selecting “Services” reveals a submenu without changing the top-level order
Consistent skip links (pass)
- “Skip to main content” appears as the first link on every page
Why This Matters for Users
Screen Reader Users
Navigation is often explored linearly or via landmark lists. Consistent ordering allows users to jump quickly to known items.
Screen Magnifier Users
Users see only a portion of the page at once and rely heavily on spatial memory. Changing order breaks that mental map.
Users with Cognitive Disabilities
Repeated patterns reduce cognitive load. Inconsistent navigation forces repeated re-learning.
Keyboard Users
Predictable order reduces keystrokes and navigation time.
Common Real-World Failure Patterns
- Moving the search field between the header and the footer across pages
- Reordering navigation based on page type or analytics
- Using A/B tests that reshuffle menus
- CMS templates that output navigation differently by content type
- CSS reordering that changes the DOM sequence across layouts
These failures are usually accidental, but still violations.
User-Initiated Changes Are Allowed
This criterion allows navigation order to change when the user chooses to, such as:
- Browser or assistive technology preferences
- User-controlled personalisation settings
- Explicit sorting or filtering controls
The key rule is simple: Authors must not change navigation order automatically.
Relationship to Other Criteria
- 3.2.1 On Focus — prevents unexpected changes when focus moves
- 3.2.2 On Input — prevents unexpected changes when values change
- 2.4.5 Multiple Ways — ensures alternative navigation paths exist
Consistent Navigation ensures users can reuse learned structure across pages.
How to Test
- Identify navigation that appears on multiple pages
- Compare item order page-to-page
- Verify that:
- Order remains the same
- Placement is predictable
- Changes require user action
- Test using:
- Keyboard navigation
- Screen reader landmark lists
- Zoomed or magnified views
If users must re-learn navigation on each page, the criterion is not met.
Rule Description
Repeated navigation mechanisms must appear in the same relative order across pages unless users explicitly choose to change that order.
Wrapping Up
Consistent navigation is not about visual uniformity; it is about orientation and memory. WCAG 3.2.3 protects users from unnecessary re-learning by ensuring navigation behaves the same way wherever it appears. Getting this right reduces cognitive load, speeds up navigation, and prevents avoidable confusion.
It is one of the most impactful and most commonly broken Level AA requirements.
