Skip to main content
Accessibility.com, LLC
Category: Input and Navigation

Consistent Navigation

Also known as: WCAG Success Criterion 3.2.3, SC 3.2.3
Simply put

Consistent Navigation is the practice of keeping navigation menus, links, and other repeated wayfinding features in the same relative order on every page where they appear. When these elements stay predictable from page to page, people can more easily learn a site's layout and find what they need. This is one of the requirements in the Web Content Accessibility Guidelines (WCAG).

Formal definition

Consistent Navigation is WCAG Success Criterion 3.2.3, a Level AA criterion under the Understandable principle. It requires that navigational mechanisms repeated across 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. The intent is to promote consistent visual layout and source order for repeated content, which supports users of assistive technologies and users who rely on predictable placement to locate and operate navigation. Meeting this criterion addresses ordering consistency; it does not, on its own, guarantee an accessible experience across all criteria, and it should be verified through manual and assistive technology testing rather than automated checks alone.

Why it matters

Predictable placement of navigation is one of the ways websites become learnable. When menus, search fields, and other repeated wayfinding elements appear in the same relative order on every page, people can build a mental model of the site once and reuse it everywhere. This benefits everyone, but it is especially important for users of assistive technologies, people with cognitive or memory-related disabilities, and anyone who relies on knowing where an element will be rather than visually scanning the whole page each time. When navigation shifts position from page to page, users must re-orient repeatedly, which increases effort and the chance of getting lost.

Consistent Navigation is codified as WCAG Success Criterion 3.2.3, a Level AA criterion under the Understandable principle. Because Level AA is the conformance level most commonly cited as a target in accessibility policies, procurement requirements, and settlement benchmarks, this criterion frequently appears in conformance evaluations. It is worth noting that meeting SC 3.2.3 addresses only the ordering consistency of repeated navigation; it does not by itself guarantee an accessible experience across all other criteria, nor does conformance guarantee immunity from legal claims.

Who it's relevant to

UX and interaction designers
Designers determine where repeated navigation, search, and wayfinding elements sit across templates. Establishing a consistent layout pattern early, and preserving relative order across all page types, is the most direct way to satisfy this criterion and to reduce cognitive load for users learning the site.
Front-end developers
Because the criterion applies to both visual layout and source order, developers should ensure that shared navigation components render in the same relative order in the DOM across pages, so keyboard and screen reader users encounter a predictable sequence. Reused component libraries and shared templates help maintain this consistency.
Accessibility testers and QA teams
Verifying SC 3.2.3 generally requires manual comparison of repeated navigation across representative pages and testing with assistive technologies, since automated tools cannot fully confirm consistent relative ordering. Testers should check both visual placement and tab/reading order.
Content authors and site administrators
People building multiple pages, subpages, or modules, such as instructors creating course content in a learning platform, contribute to consistency by laying out similar elements in the same way across pages. Ad hoc reordering on individual pages can undermine an otherwise consistent site.
Compliance officers and legal counsel
SC 3.2.3 is a Level AA criterion, the level most commonly referenced as a conformance target. It is one piece of a broader WCAG evaluation and does not on its own establish overall accessibility or legal compliance. Applicable obligations depend on jurisdiction and evolving regulation and case law; this entry is not legal advice, and organizations should consult qualified counsel and current agency guidance.

Inside Consistent Navigation

Consistent Navigation (WCAG 3.2.3)
A WCAG success criterion, introduced in WCAG 2.0 at Level AA, requiring that navigational mechanisms repeated across multiple 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.
Repeated navigational mechanisms
Menus, search fields, breadcrumb trails, and other navigation components that appear on more than one page. The criterion applies specifically to these repeated elements rather than to unique, page-specific content.
Relative order
The requirement addresses the order in which navigation items appear relative to one another, not their exact pixel position. Items may shift with responsive layouts as long as their sequence remains the same.
User-initiated change exception
The consistency requirement does not apply when the user has requested a change, such as reordering or customizing navigation, since the change originates from user action rather than an inconsistent design.
Relationship to predictability
Consistent Navigation falls under the WCAG 'Predictable' guideline (3.2), which aims to make the operation and appearance of content predictable, benefiting users of assistive technologies, users with cognitive disabilities, and those relying on spatial or sequential memory.

Common questions

Answers to the questions practitioners most commonly ask about Consistent Navigation.

Does Consistent Navigation mean every page on my site must have identical navigation?
No. The requirement, defined by WCAG Success Criterion 3.2.3 Consistent Navigation (a Level AA criterion introduced in WCAG 2.0), addresses navigational mechanisms that are repeated across multiple pages. When those repeated mechanisms appear, they should occur in the same relative order each time, unless the user initiates a change. It does not require that every page contain the same navigation, nor does it prohibit pages from having unique navigational elements appropriate to their content. The focus is on the consistency of order for the mechanisms that do repeat.
If my navigation meets the Consistent Navigation criterion, does that mean my site is accessible and legally compliant?
Not on its own. Consistent Navigation is one success criterion among many, and satisfying it does not guarantee an accessible experience or immunity from legal claims. Conformance with individual WCAG criteria is distinct from overall usability and from legal compliance. Automated testing detects only a portion of potential issues, so manual review and testing with assistive technologies are generally needed. This entry is not legal advice; questions about compliance obligations should be directed to qualified legal counsel and current agency guidance.
What counts as a repeated navigational mechanism under this criterion?
The criterion applies to navigational components that appear on multiple pages within a set of pages, such as a primary menu, a persistent search field, or breadcrumb structures that recur across a site. When these appear on more than one page, they should be presented in the same relative order on each occurrence. The emphasis is on the relative order rather than on pixel-perfect placement.
Can I change the order of navigation items if a user chooses to?
Yes. The criterion allows changes to the order of repeated navigation when the user initiates them. For example, if a user rearranges or customizes their menu through a provided setting, the resulting order reflects the user's own choice and is generally consistent with the intent of the criterion. The concern the criterion addresses is unexpected, system-driven reordering that the user did not request.
How does Consistent Navigation help users of assistive technologies?
Predictable ordering of repeated navigation helps users who rely on screen readers, screen magnification, keyboard navigation, or who benefit from cognitive predictability, because they can learn where recurring elements are located and rely on that arrangement across pages. When repeated mechanisms shift order unexpectedly, these users may need to reorient themselves on each page, which can increase effort and confusion.
How can I verify that my navigation meets this criterion during testing?
Verification generally involves manual review across a representative set of pages to confirm that repeated navigational mechanisms appear in the same relative order. Because this criterion concerns ordering and predictability, automated tools may not fully evaluate it, so manual inspection and testing with assistive technologies such as screen readers are commonly recommended. Reviewing the tab order and the reading order alongside the visual order can help confirm consistency for different modes of interaction.

Common misconceptions

Consistent Navigation requires navigation to appear in the exact same visual position on every page.
The criterion generally concerns the same relative order of repeated navigational mechanisms, not identical pixel placement. Responsive designs may reposition elements as long as their sequence is preserved.
Meeting Consistent Navigation means a site is fully accessible or legally compliant.
Consistent Navigation is a single Level AA success criterion. Satisfying it does not guarantee overall accessibility or immunity from legal claims, and automated tools detect only a portion of issues, so manual and assistive technology testing are commonly needed. This is not legal advice.
The ADA specifically mandates this WCAG criterion.
Consistent Navigation is defined by the W3C's WCAG, not codified in the ADA text. WCAG (commonly Level AA) is often cited as a benchmark in settlements and agency guidance, but any specific requirement should be attributed to the relevant regulation, settlement, or guidance and reviewed with qualified legal counsel.

Best practices

Keep repeated navigational mechanisms, such as primary menus, search fields, and breadcrumbs, in the same relative order across all pages in a set.
Preserve navigation sequence when adapting layouts for responsive breakpoints, allowing repositioning while maintaining the order of items.
Only alter navigation order in response to a user-initiated action, such as a customization or reordering feature the user chooses to use.
Test navigation consistency with assistive technologies and manual review, since automated checks detect only a portion of potential issues.
Document navigation patterns in a design system so consistency is maintained as pages are added or updated over time.
Treat Consistent Navigation as one part of broader WCAG conformance (commonly targeting Level AA) rather than a standalone measure of accessibility.