WCAG 2.4.5 Multiple Ways: Provide Multiple Navigation Methods

Last updated: 2026-03-22

Level AA Operable WCAG 2.4.5

What This Criterion Requires

WCAG 2.4.5 requires that more than one way is available to locate a web page within a set of web pages, except where the page is the result of, or a step in, a process. This means that users should be able to find any page through at least two different navigation mechanisms. Common ways to satisfy this criterion include providing a navigation menu together with a site search function, a sitemap page, a table of contents, related content links, breadcrumb navigation, or an A-to-Z index. The exception for process steps means that individual steps in a checkout flow, multi-step form, or wizard do not each need multiple ways to be reached, because the sequence itself is the intended navigation path. This criterion recognizes that different users navigate in different ways depending on their abilities, preferences, and the task at hand. Providing multiple paths to content makes a website more flexible and accommodating.

Why It Matters

Different users have different strategies for finding content, and what works for one user may be ineffective for another. Users with cognitive disabilities may find it easier to use a site search rather than navigating a complex menu structure. Users with visual impairments using screen readers may prefer to use a sitemap or A-to-Z index rather than navigating through nested menus. Users with motor impairments may find that following links from a sitemap requires fewer interactions than navigating through multiple menu levels. Some users prefer to browse through navigation hierarchies, while others know exactly what they want and prefer to search. By providing multiple ways to locate content, websites accommodate the full range of user preferences and abilities. This also benefits users who are unfamiliar with the site structure and users who have difficulty understanding the organization of the navigation. Multiple navigation methods create redundancy that improves usability for everyone.

Common Failures and How to Fix Them

Only a single navigation menu with no search or sitemap

The website provides only a primary navigation menu as the sole method for finding pages. There is no search function, no sitemap, and no other alternative way to locate content.

Inaccessible 
<header>
  <nav>
    <ul>
      <li><a href="/">Home</a></li>
      <li><a href="/products">Products</a></li>
      <li><a href="/about">About</a></li>
      <li><a href="/contact">Contact</a></li>
    </ul>
  </nav>
</header>
<!-- No search, no sitemap link, no other navigation method -->
Accessible 
<header>
  <nav aria-label="Main navigation">
    <ul>
      <li><a href="/">Home</a></li>
      <li><a href="/products">Products</a></li>
      <li><a href="/about">About</a></li>
      <li><a href="/contact">Contact</a></li>
    </ul>
  </nav>
  <form role="search" action="/search" method="get">
    <label for="site-search" class="visually-hidden">Search this site</label>
    <input type="search" id="site-search" name="q" placeholder="Search...">
    <button type="submit">Search</button>
  </form>
</header>
<footer>
  <a href="/sitemap">Sitemap</a>
</footer>

Search function exists but is inaccessible or non-functional

A search form is present on the page but either does not work, is hidden from assistive technology, or lacks proper labeling, effectively reducing navigation to a single method.

Inaccessible 
<div class="search-box" aria-hidden="true">
  <input type="text" placeholder="Search">
  <div onclick="search()">Go</div>
</div>
Accessible 
<form role="search" action="/search" method="get">
  <label for="search-input" class="visually-hidden">Search the site</label>
  <input type="search" id="search-input" name="q" placeholder="Search...">
  <button type="submit">Search</button>
</form>

How to Test

  1. Identify at least two distinct methods for locating any given page on the website, such as navigation menu plus search, or navigation menu plus sitemap.
  2. Verify that the search function works correctly and returns relevant results when tested with known page titles or content.
  3. Check that alternative navigation aids (sitemap, breadcrumbs, related links) are accessible to screen readers and keyboard users.
  4. Confirm that process pages (checkout steps, multi-step forms) are excluded from this requirement and only need sequential navigation.

CMS-Specific Guidance

This criterion commonly causes issues on these platforms:

Further Reading

Related WCAG Criteria