Start scanning free

( Understandable / WCAG 3.2.3 )

Navigation order is inconsistent across pages

This check maps to Consistent Navigation. Use the guidance below to confirm the issue, understand who it affects and ship a fix.

Moderate Level AA WCAG 3.2.3 — Consistent Navigation

What’s wrong

Navigation components are repeated but appear in a different order between pages.

Why it matters

Keyboard-only users and people with cognitive disabilities build memory for repeated navigation. Reordering repeated menus forces re-learning on every page.

How to fix it

Use semantic HTML and valid ARIA so assistive technology gets the same state and structure as sighted users. Keep labels and states explicit in markup.

Before
<nav>
  <a href="/pricing">Pricing</a>
  <a href="/features">Features</a>
  <a href="/docs">Docs</a>
</nav>
After
<nav>
  <a href="/features">Features</a>
  <a href="/pricing">Pricing</a>
  <a href="/docs">Docs</a>
</nav>

If this pattern is generated by a component, fix it once in the shared component so every instance inherits the accessible behavior.

Learn more