Navigation elements are consistent across pages
Why it matters
Navigation that changes location or order between pages violates users' mental model of the site, forcing screen reader users and keyboard navigators to re-learn the layout on every page. WCAG 2.2 SC 3.2.3 (Consistent Navigation) is a Level AA requirement. Users with cognitive disabilities are disproportionately affected — unpredictable navigation increases error rates and abandonment. For any product requiring repeat visits, inconsistent navigation erodes trust.
Severity rationale
High because navigation inconsistency forces users with cognitive or motor disabilities to relearn the interface on every page, violating WCAG 2.2 SC 3.2.3 at Level AA and undermining core usability.
Remediation
Render your navigation from a single shared component in the root layout so it cannot diverge between pages.
// app/layout.tsx — navigation is defined once, appears everywhere
export default function RootLayout({ children }: { children: React.ReactNode }) {
return (
<html lang="en">
<body>
<SiteHeader /> {/* Single source of truth for nav */}
<main>{children}</main>
<SiteFooter />
</body>
</html>
)
}
If some pages need additional navigation (e.g., a docs sidebar), add it as a supplemental landmark, never in place of the primary nav. Audit every distinct layout file to confirm the primary nav component and its link order are identical.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Accessibility WCAG Compliance Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- wcag:2.2 · 3.2.3 — Consistent Navigation
- section-508:2018-refresh · 501.1 — Scope
Taxons
History
- 2026-04-18·v1.0.0·Initial import from accessibility-wcag·automated