Goal
Keep navigation consistent across pages.
Success Criterion · WCAG 3.2.3
Consistent Navigation
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.
Level AAWCAG 2.0Understandable3.2 · Predictable
Copy button ready
What to do
Place repeated navigation mechanisms in the same relative order on each page.
Why it matters
Consistency reduces cognitive load and helps users build reliable mental models of your site.
Success criterion
What WCAG 3.2.3 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
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.
Intent
Why WCAG created this requirement
- Consistency supports orientation and efficiency.
- Unexpected nav rearrangements increase confusion.
- User-initiated customization is allowed.
Benefits
Who gains when you pass
- Users with cognitive disabilities can navigate more confidently.
- Screen reader users can predict where navigation items are.
- All users benefit from consistent information architecture.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users get lost when nav items move around between pages.
Users may miss important links due to inconsistent ordering.
Exception guidelines
Use the WCAG 3.2.3 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
User initiated change
User changes navigation order (personalization).
Requirement
If the user initiates reordering, it is allowed.
Overview
Repeated navigation (header links, sidebars, menus) should be consistent across pages in order and placement. This helps users find things without relearning navigation.
- Keep global nav consistent across the site.
- If context-specific nav exists, keep its internal order consistent.
- Allow user personalization (e.g., reorder favorites) as an exception.
Reference: All summaries and highlights originate from Understanding WCAG 3.2.3 and the W3C quick reference.
Fast facts
- Conformance level
- Level AA
- WCAG version introduced
- WCAG 2.0
- Principle
- Understandable
- Guideline
- 3.2 · Predictable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Header nav
Pass
Header links appear in the same order across all pages.
Fail
Header link order changes between pages with no user action.
Sidebar
Pass
Sidebar sections remain consistent across the dashboard.
Fail
Sidebar moves “Settings” between sections on different pages.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document navigation structure and ordering rules.
- Capture screenshots of nav across key templates as evidence.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Standardize navigation components across page templates.
- Keep ordering of repeated nav links consistent.
- Avoid A/B tests that reorder nav without user initiation in AA scope.
- Document any user-customizable navigation behavior.
Testing ideas
Prove conformance with evidence
- Compare navigation menus across multiple pages and verify consistent order.
- Test user-customizable nav and confirm the change is user initiated.
- Use a screen reader to verify nav structure is consistent.
Related success criteria