- Level
- AA
- Since
- WCAG 2.0
3.2.3 Consistent Navigation
Menus, search boxes and other navigation that repeat across the pages of a site must come in the same order on every page, unless the user changes it.
/ What it requires
A site repeats its navigation on almost every page: the main menu, the search box, the breadcrumb trail, the footer links. This criterion asks that wherever those blocks repeat within a set of web pages, they come in the same order relative to each other. People who magnify the screen and see only a small part of it at a time find the menu by remembering where it was. Screen reader users who move through a page in sequence learn that the search comes after the menu and before the main content. When the order shifts from page to page, both groups have to search again on every page.
The rule is about relative order, not identical pages. W3C counts items as being in the same relative order even when other items are inserted or removed, so a section menu that appears in one part of the site only, or a menu that expands to show a deeper level, does not fail. It covers navigation that repeats within one set of web pages, meaning pages with a common purpose from the same author, and different language versions count as separate sets. The one exception is a change the user starts, for example through a preference or an adaptive tool that rearranges the page.
/ How pages fail it
- The main menu lists Products, Pricing and Support on the home page and Support, Products and Pricing on the inner pages.
- The search field comes before the menu in the source of some templates and after it in others, so a screen reader meets them in a different order.
- A landing page built in a separate page builder puts the shared footer links in a different sequence from the rest of the site.
- The skip link, the language switcher and the account menu swap places between the shop and the blog of the same site.
- A script moves the menu item of the current section to the front of the list, so the menu order changes from section to section.
/ How to check it yourself
- Pick a sample of pages built from different templates: the home page, a listing, a detail page, a form, a help page and any landing page.
- On each, write down the order of the repeated blocks, such as header items, main menu, search, breadcrumb, sidebar and footer, and the order of the links inside each menu.
- Compare the lists. A block may be missing on one page or gain extra items, but whatever repeats has to keep its order.
- Check the order in the source too. Press Tab from the top of each page, or open the accessibility tree in the browser developer tools, because CSS can show one order on screen while the markup holds another.
- With a free screen reader such as NVDA, list the landmarks or the links on two pages and check that the repeated ones come up in the same sequence.
/ How to fix it
- Render the header, the main menu and the footer from one shared component or template partial, so every page gets the same markup in the same order.
- Keep the menu items in one data source, such as a single navigation config, instead of lists written by hand for each page.
- Mark the current page with aria-current="page" and a visual style instead of moving its item to another position.
- Do not reorder repeated blocks with the CSS order property, flex-direction: row-reverse or absolute positioning in some templates only. Keep the visual order and the DOM order the same.
- When a section needs its own sub-menu, insert it beside the shared navigation and leave the order of the shared items untouched.
/ What our scanner checks
No check in our scan covers this. Every rule looks at one rendered page at a time, so the order of the menu on one page is never set against another. The HTML_CodeSniffer pass raises only a reminder for this criterion, and reminders are dropped. Comparing the repeated navigation across a sample of templates is part of the manual audit.
/ Who fails it, in our own measurements
The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Does consistent navigation mean every page needs the same menu?
No. The criterion asks that navigation which repeats keeps its order. A page may leave a block out, and a section may add a sub-menu, because W3C counts items as being in the same relative order even when others are inserted or removed. What fails is the same repeated links showing up in a different sequence on different pages.
What level is 3.2.3 Consistent Navigation?
Level AA. It has been part of WCAG since 2.0 and is unchanged in 2.1 and 2.2. It applies within a set of web pages, which W3C defines as pages that share a common purpose and are created by the same author, group or organization. Different language versions of a site are separate sets.
What is the difference between 3.2.3 and 3.2.4?
3.2.3 Consistent Navigation is about where repeated navigation sits: the same relative order on every page. 3.2.4 Consistent Identification is about what components with the same function are called: the same label, name or icon wherever they appear. A site can keep its menu in order and still fail 3.2.4 by calling the search button Search on one page and Find on another.
