Does each set of pages provide at least two different navigation systems (except in special cases)?
A user who isn't comfortable with hierarchical menus will look for a search field. Another, lost in a deep tree structure, will open the site map. If your only navigation system is a menu, you exclude everyone who doesn't work that way. Two systems is the minimum.
RGAA recognizes three valid combinations: a navigation menu with a site map, a navigation menu with a search engine, or a search engine with a site map. One of these three combinations must be present on each set of pages on the site, not just on the home page.
The simplest combination to deploy remains the main menu associated with a search engine. A <form role="search"> visible in the header is enough, provided it returns relevant results. The site map works better for sites with complex tree structures where keyword search doesn't cover everything.
Un test to verify that at least two navigation systems are offered
Presence of two complementary navigation systems
For each set of pages on the site:
- Identify the navigation systems present: navigation menu, site map, search engine.
- Verify that at least one of the following three combinations is available on all pages of the set:
- Navigation menu and site map
- Navigation menu and search engine
- Search engine and site map
- If no valid combination is found, the test fails.
Examples
❌ Non-compliant : Only one navigation system: menu without search or site map
<header>
<nav aria-label="Main menu">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/services">Services</a></li>
<li><a href="/blog">Blog</a></li>
<li><a href="/contact">Contact</a></li>
</ul>
</nav>
</header>This site offers only a navigation menu. No search engine, no site map. A user who loses their way in the tree structure has no other way to find a page. Criterion 12.1 fails.
✅ Compliant : Two navigation systems: main menu and search engine
<header>
<nav aria-label="Main menu">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/services">Services</a></li>
<li><a href="/blog">Blog</a></li>
<li><a href="/contact">Contact</a></li>
</ul>
</nav>
<form role="search" aria-label="Search the site">
<label for="q">Search</label>
<input type="search" id="q" name="q" placeholder="Keyword...">
<button type="submit">Launch search</button>
</form>
</header>The navigation menu and search engine are two distinct and complementary systems. A user can navigate by tree structure or by keyword according to their preference. This combination satisfies criterion 12.1.
Tips and pitfalls
⚠️ Breadcrumb navigation doesn't count for this criterion
Breadcrumb navigation helps with orientation, but RGAA doesn't recognize it as one of the three valid systems for criterion 12.1. Only these count: navigation menu, site map, and search engine. A site with a menu associated with only a breadcrumb fails test 12.1.1.
⚠️ A responsive menu is not two navigation systems
Two versions of the same menu — a mobile version hidden in CSS and a desktop version visible — remain a single navigation system. RGAA evaluates functional systems, not HTML implementations. A real second modality is needed: a search engine or site map.
⚠️ Sites with very few pages
The criterion is not applicable for sites consisting of a single page or a very limited number of pages, that is, sites where all pages are reachable directly from the home page. A portfolio of five or six pages all linked from the home page generally falls into this case. The assessment remains at the auditor's discretion; there is no official numerical threshold.
⚠️ Pages in a sequential process
Pages that are part of a process — shopping tunnel, multi-step registration form, online payment — are exempt from criterion 12.1. Displaying a full menu or search engine on these steps would be counterproductive. Regular pages on the site outside the process remain subject to the requirement.
💡 Test that the search engine is actually functional
A search field present in the HTML but that systematically returns zero results, or redirects to Google while leaving the domain, does not constitute a valid internal search engine. In an audit, run a few obvious queries to verify that the system works. This is a common mistake on sites that have integrated a search widget without configuring it.
Frequently asked questions
Why doesn't a breadcrumb replace the site map according to RGAA?
No. RGAA 12.1 recognizes only three valid systems: navigation menu, site map, and search engine. Breadcrumb appears in criterion 12.8 (navigation consistency), but it doesn't fall into the combinations accepted by test 12.1.1.
When must a small site still offer two RGAA navigation systems?
Probably not. If all your pages are accessible from the home page and the site has very few pages, the criterion is not applicable. RGAA doesn't set a precise numerical threshold; the auditor assesses based on context. A four to six page brochure site linked from the home page generally falls into this case.
How to audit RGAA criterion 12.1 on navigation systems in practice?
Browse the site and identify the navigation systems present on each set of pages. Verify that at least one of the three valid combinations is accessible on the set in question. Test the search engine with a few queries to confirm it returns results. A non-functional search engine doesn't count.
What RGAA 12.1 rule applies to navigation systems in a payment tunnel?
None. Pages that are part of a sequential process (order, payment, registration) are explicitly exempt from criterion 12.1. Only regular pages on the site, outside processes, are subject to this requirement.