Consistent Navigation: Same Menus, Same Order
Also called: Consistent menus, Predictable navigation, Navigation order
Definition
Consistent Navigation is WCAG success criterion 3.2.3. Navigational mechanisms that are repeated on multiple web pages within a set of web pages must occur in the same relative order each time they are repeated, unless a change is initiated by the user.
Consistent Navigation is the WCAG rule that menus, search fields and other repeated navigation stay in the same order on every page of a website. Visitors learn your layout once and can rely on it everywhere. For people who see only part of the screen, listen to the page or depend on routines, that predictability decides whether they find their way at all.
What it means
WCAG 3.2.3 Consistent Navigation is a Level AA criterion of WCAG 2.2. Navigational mechanisms that repeat across a set of pages – main menu, search, breadcrumbs, footer links, a skip link – must appear in the same relative order each time, unless the user changes it.
"Same relative order" means the same position relative to the other items. It does not mean pixel-identical pages:
| Situation | Passes 3.2.3? |
|---|---|
| A sub-menu expands and inserts items into the main menu | Yes – the others keep their order |
| One page has an extra item, e.g. a secondary navigation | Yes |
| The search field is always the last item of the header | Yes |
| "Pricing" comes before "Features" on one page and after it on another | No (failure F66) |
| The user rearranges the menu in their own settings | Yes – change initiated by the user |
Who benefits? Screen magnifier users see only a small part of the page and look for navigation where they found it before. Screen reader users move through the content in order and rely on reaching the menu at the same point. People with cognitive disabilities and anyone who relies on visual memory find things faster when nothing moves around.
Examples
<!-- Every page: same header template, same order -->
<header>
<a href="#main" class="skip">Skip to main content</a>
<nav aria-label="Main">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/services">Services</a></li>
<li><a href="/about">About</a></li>
<li><a href="/contact">Contact</a></li>
</ul>
</nav>
<form role="search" action="/search">
<label for="q">Search</label>
<input id="q" name="q" type="search">
</form>
</header>W3C's examples include a "skip to main content" link that is the first link on every page, and a site whose navigation sits at the end of each page with a skip link at the start that leads to it. Both are consistent placements.
Build header, menu and footer from one shared template. Keep the order of menu items stable and add page-specific links in a separate sub-navigation. Put the search field in the same place on every page.
Reorder menu items per page – for example moving the current section to the top. Don't use a different header on landing pages or in the shop with the same links in another order. Don't swap header and footer navigation between templates.
How to check Consistent Navigation
Questions
Does the navigation have to be identical on every page?
No. WCAG 3.2.3 requires the same relative order, not identical menus. Items can be added or removed, for example a sub-menu for one section, as long as the repeated items keep their order.
Does consistent navigation apply to mobile and desktop?
The criterion compares pages within a set of pages and does not single out screen sizes. In practice, compare each layout across pages: the repeated items of the mobile menu should keep their order from page to page, just like those of the desktop menu.
Is a skip link required by 3.2.3?
No. Skip links appear in W3C's examples only as a consistently placed element. Letting users bypass repeated content is a separate requirement, WCAG 2.4.1 Bypass Blocks.
What is the difference between consistent navigation and multiple ways?
Consistent navigation is about the order of repeated menus. Multiple ways (2.4.5) requires more than one way to find a page, such as a menu plus a search or a sitemap.
Related terms
Consistent Identification: Same Function, Same Name
Consistent Identification is WCAG success criterion 3.2.4. Components that have the same functionality within a set of web pages must be identified consistently – with the same labels, names and text alternatives.
Read definition: Consistent Identification: Same Function, Same NameConsistent Help: Keep Support in the Same Place
Consistent Help is WCAG success criterion 3.2.6. If help mechanisms such as contact details, a contact form, a self-help page or a chatbot are repeated on multiple pages of a site, they occur in the same order relative to other page content, unless the user changes it.
Read definition: Consistent Help: Keep Support in the Same PlaceMultiple Ways: More Than One Path to a Page
Multiple ways is WCAG success criterion 2.4.5. More than one way must be available to locate a web page within a set of web pages – for example navigation plus search or a site map – except where the page is the result of, or a step in, a process.
Read definition: Multiple Ways: More Than One Path to a PageSkip Link: Jump Straight to the Main Content
A skip link is a link at the very top of a page that jumps to the main content, so keyboard and screen reader users do not have to pass the whole menu on every page. It is a sufficient technique for WCAG 2.4.1.
Read definition: Skip Link: Jump Straight to the Main Content