Skip to main content
Operable WCAG 2.4.5

2.4.5 Multiple Ways

More than one way is available to locate a web page within a set of web pages, except where the page is a result of or a step in a process.

Level AA Moderate WCAG 2.0 (new) WCAG 2.1 WCAG 2.2

What this rule means

WCAG 2.4.5 requires that users can find any page on a website through at least two different mechanisms. Common approaches include: a site-wide navigation menu, a search function, a sitemap page, a table of contents, breadcrumb navigation, or links between related pages.

The exception is pages that are part of a multi-step process (such as a checkout flow or form wizard) — these do not need to be independently locatable since their context depends on the process flow.

Why it matters

Different users have different preferences and abilities when it comes to finding content. Some users prefer to browse through navigation menus, others prefer using search, and still others rely on sitemaps. Users with cognitive disabilities may find hierarchical navigation confusing and prefer a flat search interface. Blind users may prefer keyboard-navigable navigation structures over visual sitemaps.

Providing multiple ways to locate content ensures that every user can find what they need using the method that works best for them. It also serves as a safety net — if one mechanism is difficult to use, the user has alternatives.

Related axe-core rules

There are no automated axe-core rules for this criterion. It requires manual verification that at least two navigation mechanisms exist.

How to test

  1. Identify at least two of the following mechanisms on the website: navigation menu, search function, sitemap, table of contents, breadcrumbs, or related page links.
  2. Attempt to locate a specific content page using each available mechanism and confirm both paths lead to the same page.
  3. Verify that process-step pages (checkout, wizard) are excluded from this requirement.
  • Check that the search function returns relevant results and is keyboard-accessible.
  • Verify the sitemap is up to date and includes all public pages.

How to fix

Implement at least two of the following mechanisms. A global navigation menu plus a search function is the most common pattern.

Search with accessible markup

<form role="search" aria-label="Site search">
  <label for="search-input">Search</label>
  <input
    type="search"
    id="search-input"
    name="q"
    placeholder="Search articles..."
    autocomplete="off"
  />
  <button type="submit">Search</button>
</form>

Breadcrumb navigation

<nav aria-label="Breadcrumb">
  <ol>
    <li><a href="/">Home</a></li>
    <li><a href="/knowledge-base">Knowledge Base</a></li>
    <li><a href="/knowledge-base/operable">Operable</a></li>
    <li aria-current="page">2.4.5 Multiple Ways</li>
  </ol>
</nav>

Sitemap page structure

<main>
  <h1>Sitemap</h1>
  <nav aria-label="Sitemap">
    <h2>Knowledge Base</h2>
    <ul>
      <li><a href="/kb/perceivable">Perceivable</a></li>
      <li><a href="/kb/operable">Operable</a></li>
      <li><a href="/kb/understandable">Understandable</a></li>
      <li><a href="/kb/robust">Robust</a></li>
    </ul>
    <h2>Services</h2>
    <ul>
      <li><a href="/services/audit">Accessibility Audit</a></li>
      <li><a href="/services/training">Training</a></li>
    </ul>
  </nav>
</main>

Common mistakes

  • Providing only a navigation menu with no search function, sitemap, or other alternative.
  • Having a search function that is visually present but not keyboard-accessible.
  • Maintaining a sitemap that is outdated and missing recently added pages.
  • Using JavaScript-only navigation that breaks when scripts fail to load.
  • Hiding the search function behind a tiny icon with no accessible label.

Resources