WCAG 3.2.3 — Consistent Navigation

Inconsistent Navigation

What is this issue?

Inconsistent navigation occurs when navigation menus that appear on multiple pages change their order, structure, or content unpredictably from page to page. WCAG Success Criterion 3.2.3 (Level AA) requires that navigational mechanisms that are repeated on multiple 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 does not mean navigation must be identical on every page -- items may be added or removed as appropriate. But the relative order of the items that do appear must remain consistent. If the main navigation shows "Home, Products, About, Contact" on one page, it should not show "Home, About, Products, Contact" on another page.

Common causes include: different page templates with differently ordered navigation, server-side rendering that reorders navigation based on page-specific logic, JavaScript that dynamically rearranges menu items based on user behavior or A/B testing, and footer navigation that presents links in a different order than the header navigation. CMS-based sites sometimes allow individual page editors to customize navigation order, inadvertently breaking consistency.

Impact on users

Users with cognitive disabilities, low vision, and learning disabilities rely on predictable navigation patterns to orient themselves and find content. When the navigation order changes between pages, these users must re-learn the navigation on every page, increasing cognitive load and the time needed to complete tasks.

Screen reader users memorize the position of navigation items (e.g., "Contact is the fourth item"). When the order changes, their memorized positions become unreliable, forcing them to scan the entire navigation on every page to find the item they need. This is especially frustrating on sites with large navigation menus.

All users benefit from consistent navigation, not just those with disabilities. Inconsistent navigation violates a fundamental usability principle: users build mental models of a site's structure based on repeated patterns. Breaking these patterns creates confusion and reduces confidence in the site.

Code example

Before (non-compliant)

<!-- Page 1: Home, Products, About, Contact -->
<nav>
  <a href="/">Home</a>
  <a href="/products">Products</a>
  <a href="/about">About</a>
  <a href="/contact">Contact</a>
</nav>

<!-- Page 2: Home, About, Contact, Products -->
<nav>
  <a href="/">Home</a>
  <a href="/about">About</a>
  <a href="/contact">Contact</a>
  <a href="/products">Products</a>
</nav>

After (compliant)

<!-- Same order on every page -->
<!-- page1.html -->
<nav aria-label="Main navigation">
  <a href="/">Home</a>
  <a href="/products">Products</a>
  <a href="/about">About</a>
  <a href="/contact">Contact</a>
</nav>

<!-- page2.html -->
<nav aria-label="Main navigation">
  <a href="/">Home</a>
  <a href="/products">Products</a>
  <a href="/about" aria-current="page">About</a>
  <a href="/contact">Contact</a>
</nav>

How Scrutia detects this issue

Scrutia crawls multiple pages of your site and compares the order of navigation items across pages. It flags cases where the same navigation links appear in a different relative order on different pages. The report shows the inconsistent orderings side by side and identifies which pages deviate from the most common order.

Check your site for this issue

Scrutia audits your site against WCAG criteria in minutes.

Free audit

Frequently Asked Questions

Can I add page-specific navigation items?

Yes. WCAG 3.2.3 requires consistent relative order, not identical content. You can add items relevant to specific sections as long as the items that appear on multiple pages maintain their relative order.

Does this apply to footer navigation?

Yes. All repeated navigation mechanisms must maintain consistent order across pages. This includes header navigation, footer links, sidebar menus, and breadcrumbs.

How do I maintain consistency across a large CMS?

Use a single shared navigation component or template that is included on all pages. Avoid allowing individual page editors to customize navigation order. Define the navigation structure centrally and render it consistently across all pages.

Does your site have this issue?

Scrutia scans your pages against WCAG success criteria and delivers actionable fixes. Results in 5 minutes.

Run a free audit