Skip to content
Barrierefrei²

Success criterion 3.2.3

3.2.3 Consistent Navigation

Level AAUnderstandable

How to bring order to digital chaos.

1. What is the goal of this criterion?

Imagine walking into the same office building every day – but the lifts are sometimes on the left, sometimes on the right and sometimes in the middle. That wouldn’t just be annoying; for people with visual impairments or cognitive disabilities it would be genuinely disorienting.

That’s exactly what happens on many websites: menu items swap places, the search shows up before the main menu on one page and after it on the next, and important links wander around. People who rely on predictable structures quickly lose track.

So the goal of WCAG Success Criterion 3.2.3 is clear: navigation elements that appear on several pages of a website must show up in the same relative order every time. That way everyone can rely on finding things where they expect them.

2. What exactly does it require?

Specifically, it covers all navigation mechanisms that are repeated across multiple pages of a website. They must appear in the same relative order – unless the person changes that order themselves.

In practice, this means:

  • The main menu keeps its order: “Home, Products, Service, Contact” stays “Home, Products, Service, Contact”
  • The search always sits at the same point in the sequence – for example, always after the main menu
  • Skip links such as “Skip to content” consistently appear as the first element
  • The footer navigation follows the same structure on every page

Important clarification: “same relative order” doesn’t mean nothing can be added. Submenus can expand, and extra navigation items can be inserted or removed – as long as the remaining items keep the same order relative to each other. What’s required is the order, not a pixel-perfect identical position.

Exceptions only apply when the person initiates the change – for example through a setting that lets them reorder menu items or pin frequently used links to the front.

3. Why does it matter for accessibility?

Imagine using a screen magnifier that only ever shows a small section of the page. Or relying on a screen reader and using keyboard shortcuts to jump to familiar places. If those places keep moving, every page visit turns into a scavenger hunt.

Consistent navigation supports accessibility because it:

  • lets people with visual impairments rely on visual anchors and spatial memory
  • helps people with cognitive disabilities build a mental model of the website
  • gives screen reader users predictable jump targets and navigation paths
  • gives people with motor impairments efficient routes without constant reorientation
  • gives everyone a website that’s easier to learn

The brain loves patterns – and consistent navigation uses that to make websites more intuitive and accessible.

4. How to meet the criterion

The good news: consistent navigation is usually easier to build than to avoid. Here are the most proven strategies:

Work with templates:

  • Use consistent layout templates for all pages
  • Define fixed places for recurring elements
  • Keep the HTML structure comparable across pages – source order matters, because screen readers and keyboards follow it
  • Use CSS Grid or Flexbox without decoupling the visual order from the source order

Structure navigation properly:

  • Always place the main menu in the same spot (usually at the top or on the left)
  • Keep the order of menu items – even when you add new ones
  • Place search, breadcrumbs and skip links consistently
  • Make sure the footer navigation is consistent

Consider responsive design:

  • Within the same layout variant (e.g. the mobile view), the relative order must be the same on every page
  • A hamburger menu may change the look but should keep the order of the menu items
  • Use consistent breakpoints and wrapping logic

Technical implementation:

  • Work with component-based frameworks (React, Vue, Angular) or your CMS’s template features
  • Build one central navigation component that’s included everywhere
  • Test regularly with a screen reader and the keyboard

What to avoid:

  • Rearranging the navigation depending on page content
  • Sorting menu items differently from page to page
  • Placing the search before the menu on some pages and after it on others
  • Letting different teams build different navigation concepts

Closely related are Consistent Identification (same function, same name) and Consistent Help. Skip links themselves are covered by Bypass Blocks.

5. Why this criterion matters for businesses

With Success Criterion 3.2.3, too, accessibility isn’t an end in itself – it brings tangible benefits for your business.

1. Better user experience

Consistent navigation doesn’t just make websites more accessible – it makes them easier for everyone to use. People find what they’re looking for faster and don’t have to reorient themselves on every page. That reduces frustration and smooths the path to a purchase or enquiry.

2. Clean structure – for search engines too

Accessibility isn’t a direct Google ranking factor. But clear, consistent navigation creates stable internal linking and an understandable site structure – which indirectly helps crawlers just as much as people.

3. Lower development costs

A central, template-based navigation reduces development and maintenance effort. A consistent system is easier to maintain, test and extend, and new team members get up to speed faster.

And then there’s the legal side: since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) has applied to many consumer-facing digital services, such as online shops and banking services. Germany implements it through the Barrierefreiheitsstärkungsgesetz (BFSG). The technical benchmark is the harmonised standard EN 301 549, which refers to WCAG 2.1 Level AA for web content – and 3.2.3 is part of that. Public sector bodies are covered separately by the Web Accessibility Directive (EU) 2016/2102. This section is general information, not legal advice.

6. The success criterion in the W3C’s words

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.

In short: navigation that repeats across several pages appears in the same relative order every time – unless the person changes it themselves.

Official explanation from the W3C

The W3C explains every success criterion in depth – with intent, examples and techniques.

Understanding 3.2.3 (opens in a new tab)