Verify consistent navigation
Description
This rule does not automatically validate anything. It simply reminds you to manually verify that 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. It scans for landmark and navigation elements such as <nav>, <header>, <footer>, .sidebar, and [role="navigation"], and reports their presence for a human auditor to evaluate across pages.
This requirement comes from WCAG Success Criterion 3.2.3 (Consistent Navigation), which states that 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.
For example, if the main navigation bar appears as Home, Products, About, Contact on one page, it should not appear as Contact, About, Products, Home on another page. Users depend on predictable placement of navigation controls to orient themselves and move efficiently through a site.
Disabilities impacted
- Cognitive disabilities – Users with cognitive impairments, learning disabilities, or memory challenges rely on predictable, repeatable navigation patterns to build a mental model of the site. When navigation order shifts between pages, these users may become disoriented, lose track of where they are, and struggle to find the information they need. The effort required to re-learn the navigation on each page can lead to task abandonment and frustration.
- Screen reader users (blindness and low vision) – Screen reader users navigate via landmarks, headings, and tab order rather than visual layout. They depend on a consistent DOM order to move quickly between sections. If the
<nav>landmark appears in a different position on different pages, users cannot reliably use keyboard shortcuts (e.g., jumping to the navigation landmark) and must manually explore each page to locate familiar controls. - Motor disabilities – People who rely on switch devices, eye-tracking, or speech recognition software benefit from motor efficiency through muscle memory. If the navigation buttons appear in a different order on each page, a user cannot automate the sequence of switch activations needed to reach a specific link. They must re-discover the button positions on every page, increasing physical effort and fatigue.
- Low vision users with screen magnification – Magnification users see only a small portion of the page at any time. They rely on consistent spatial positioning to locate navigation elements quickly. When navigation order changes, they must pan and scan the page to find the controls, which is time-consuming and visually exhausting.
Why it matters
Consistent navigation is a cornerstone of usable, accessible web design. When users can rely on the same controls in the same order across pages, they develop confidence, navigate faster, and make fewer errors. WCAG 3.2.3 is a Level AA requirement, meaning it must be satisfied for a site to claim conformance at that level. Beyond compliance, inconsistent navigation is a frequent source of user confusion, support requests, and abandoned sessions – particularly on transactional sites with multi-step workflows such as checkout, account management, or form submission.
For organizations subject to ADA or Section 508 regulations, failing to meet this criterion can expose the site to legal risk. The European Accessibility Act (EAA) also reinforces the same principles across EU member states. Consistent navigation benefits all users, not just those with disabilities: it reduces cognitive friction, improves task completion rates, and creates a professional, trustworthy brand experience.
Coding problems and solutions
Since this rule is a manual-only reminder with no automated element validation, the following checklist describes what a human reviewer should manually verify when auditing for consistent navigation compliance:
Common coding problems
- Navigation order differs across page templates – The main navigation bar lists Home, About, Services, Contact on the homepage but reorders to Home, Services, About, Contact on the services page, breaking the expected sequence.
- Skip-to-nav links or landmark order varies – Some pages place the
<nav>element before the<header>while others reverse this order, causing inconsistency in how assistive technology traverses the page. - Responsive breakpoints reorder the DOM – On desktop the sidebar navigation appears on the left, but the mobile version moves it below the main content in the DOM, changing the relative order for screen reader users.
- Dynamic content injection inserts navigation at different positions – A JavaScript component appends navigation links to the top of a container on some pages and to the bottom on others, depending on when the script executes.
- Conditional navigation elements appear inconsistently – Logged-in users see Profile, Logout as the last items in the nav, but on some pages a promotional banner is injected between the main links and the user menu, altering the relative order.
- Footer navigation order differs between pages – Footer links (Privacy, Terms, Sitemap) appear in a different sequence on the privacy page when the template mistakenly duplicates a different page’s footer.
How to fix it
Use a shared template or includes for navigation markup
The most reliable way to guarantee the same navigation order across all pages is to define the navigation markup once in a shared template, partial, or server-side include. Every page renders the same HTML in the same order, eliminating the risk of manual copy-paste errors.
<!-- Shared navigation partial – included on every page -->
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/about">About</a></li>
<li><a href="/services">Services</a></li>
<li><a href="/contact">Contact</a></li>
</ul>
</nav><!-- Page A: hand-coded navigation -->
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/about">About</a></li>
<li><a href="/services">Services</a></li>
<li><a href="/contact">Contact</a></li>
</ul>
</nav>
<!-- Page B: developer copied markup but reordered links -->
<nav aria-label="Main navigation">
<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>Maintain landmark order consistently across all pages
Landmark elements such as <header>, <nav>, <main>, <aside>, and <footer> should appear in the same DOM order on every page. Assistive technology users rely on landmark navigation to jump between sections; inconsistent landmark order forces them to re-scan the page structure each time.
<!-- Consistent landmark order on every page -->
<header>
<a href="#main" class="skip-link">Skip to main content</a>
</header>
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/products">Products</a></li>
</ul>
</nav>
<main id="main">
<h1>Page title varies here</h1>
</main>
<footer>
<p>© 2026 Company Name</p>
</footer><!-- Page A: nav before header -->
<nav aria-label="Main navigation">...</nav>
<header>...</header>
<main>...</main>
<footer>...</footer>
<!-- Page B: header before nav – different landmark order -->
<header>...</header>
<nav aria-label="Main navigation">...</nav>
<main>...</main>
<footer>...</footer>Ensure JavaScript does not reorder navigation dynamically
Client-side code that sorts, filters, or appends navigation items must preserve the original relative order of repeated controls. When dynamic content is injected, use insertAdjacentElement or targeted DOM manipulation rather than innerHTML concatenation that could reposition existing items.
// Preserve existing order by appending new items at the end
const navList = document.getElementById('main-nav-list');
const newItem = document.createElement('li');
newItem.textContent = 'New Page';
navList.appendChild(newItem);// Repositions navigation items based on arbitrary sorting logic
const navList = document.getElementById('main-nav-list');
const items = Array.from(navList.children);
items.sort((a, b) => a.textContent.localeCompare(b.textContent));
navList.innerHTML = '';
items.forEach((item) => navList.appendChild(item));Keep keyboard and focus order consistent with visual order
The tab order (via tabindex or DOM order) must match the visual navigation sequence. Avoid positive tabindex values or CSS order on flexbox/grid items that visually reposition navigation elements but leave the DOM order unchanged, creating a mismatch between sighted and keyboard users.
<!-- Visual and DOM order match – no CSS reordering -->
<nav aria-label="Main navigation">
<ul style="display: flex; gap: 1rem;">
<li><a href="/">Home</a></li>
<li><a href="/about">About</a></li>
<li><a href="/contact">Contact</a></li>
</ul>
</nav><!-- CSS order property breaks visual vs DOM sequence -->
<nav aria-label="Main navigation">
<ul style="display: flex; flex-direction: column;">
<li style="order: 3;"><a href="/">Home</a></li>
<li style="order: 1;"><a href="/about">About</a></li>
<li style="order: 2;"><a href="/contact">Contact</a></li>
</ul>
</nav>Test navigation order across all page templates and states
Create a test matrix that includes every unique page template (home, category, product, article, search results, error pages) and user state (logged-out, logged-in, admin). For each combination, verify that the relative order of navigation landmarks, links, and controls is identical. Automated visual regression tools can help detect layout shifts, but the accessibility order must be confirmed manually or with assistive technology.
<!-- All pages render the same navigation partial -->
<!-- Page A: home page -->
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/blog">Blog</a></li>
<li><a href="/faq">FAQ</a></li>
</ul>
</nav>
<!-- Page B: product page – same order, same partial -->
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/blog">Blog</a></li>
<li><a href="/faq">FAQ</a></li>
</ul>
</nav><!-- Different templates produce different navigation order -->
<!-- Page A: home page -->
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/blog">Blog</a></li>
<li><a href="/faq">FAQ</a></li>
</ul>
</nav>
<!-- Page B: FAQ page – order is reversed -->
<nav aria-label="Main navigation">
<ul>
<li><a href="/faq">FAQ</a></li>
<li><a href="/blog">Blog</a></li>
<li><a href="/">Home</a></li>
</ul>
</nav>Known Limitations
- Manual-only rule – Because this rule relies on
requiresManualVerification: true, it cannot detect navigation order inconsistencies automatically. It only reports which navigation elements exist on the current page. The auditor must compare results across multiple pages and exercise their own judgment. - Single-page scope – The rule analyzes only the page currently loaded in the browser. It cannot compare navigation order across different URLs, page templates, or sections of the site. Cross-page consistency must be verified manually by the auditor.
- Single-page applications (SPAs) – In SPAs where the DOM is dynamically rebuilt on client-side navigation, the navigation order may change due to route guards, lazy-loaded modules, or state-managed re-renders. The rule captures elements at initial scan time; it does not monitor mutations triggered by client-side routing.
- Shadow DOM – Navigation elements rendered inside open shadow roots are included in the scan, but elements in closed shadow roots are not reachable. If the site uses closed shadow DOM for navigation components, those elements will not appear in the report and must be audited separately.
- Responsive and adaptive layouts – CSS media queries may visually reposition navigation components on different viewport sizes, but the DOM order may remain the same or change depending on the responsive technique used. The auditor must verify that both the visual order and the DOM order are consistent across breakpoints.
- Third-party and embedded widgets – Navigation elements injected by third-party scripts (e.g., chat widgets, cookie consent banners, social media embeds) may appear at unpredictable positions in the DOM across different pages. These are outside the site owner’s direct control and require separate auditing.
Resources
- WCAG 2.2 Success Criterion 3.2.3 – Consistent Navigation
- Understanding SC 3.2.3 – W3C WAI
- WCAG Guideline 3.2 Predictable – MDN Web Docs
- Technique G61: Presenting repeated components in the same relative order
- WCAG 3.2.3 Examples and Benefits – W3C WAI
Rule
- Audit: accessibility
- Standard: WCAG
- Level: AA
- Success Criteria: 3.2.3
- Rule ID:
consistent-navigation