2.4.5 Multiple Ways

Level: AA | Principle: Operable | Since: WCAG 2.0 | Automation: Manual

What This Means

Users must have more than one way to locate and navigate to any page within a website. Different people find content in different ways — some prefer navigation menus, others use search, and some rely on sitemaps or breadcrumbs. Providing multiple mechanisms ensures everyone can find what they need efficiently.

Who This Affects

Screen reader users — may prefer search or a sitemap over complex nested navigation
Cognitive disability users — some find hierarchical menus confusing and prefer a flat sitemap or search
Keyboard-only users — long navigation menus are tedious; search is faster
All users — different tasks call for different navigation strategies

Common Pitfalls

1. Only providing a navigation menu

A single nav bar is the most common failure. Users who struggle with menus have no alternative.

2. Search that doesn't cover all pages

A search feature that only indexes blog posts but not product pages or help articles leaves gaps.

3. Sitemap that is outdated or incomplete

A sitemap page that hasn't been updated in years doesn't count as a usable alternative.

4. Breadcrumbs without any other secondary mechanism

Breadcrumbs alone only help if you already know where you are — they don't help you find a page from scratch.

How to Fix

Provide at least two of these mechanisms

<!-- 1. Primary navigation -->
<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>

<!-- 2. Search -->
<form role="search" aria-label="Site search">
  <label for="search">Search</label>
  <input id="search" type="search" name="q" />
  <button type="submit">Search</button>
</form>

<!-- 3. Breadcrumbs -->
<nav aria-label="Breadcrumb">
  <ol>
    <li><a href="/">Home</a></li>
    <li><a href="/products">Products</a></li>
    <li aria-current="page">Widget Pro</li>
  </ol>
</nav>

<!-- 4. Sitemap (linked in footer) -->
<footer>
  <a href="/sitemap">Sitemap</a>
</footer>

Common combinations

| Combination | Good For | |-------------|----------| | Nav + Search | Most websites — fast for both browse and find | | Nav + Sitemap | Content-heavy sites — flat view of all pages | | Nav + Breadcrumbs + Search | Large e-commerce or documentation sites | | Nav + Table of Contents | Single-page documentation or long articles |

Exception

This criterion does not apply to pages that are part of a process (e.g., checkout step 2 of 3 or a multi-step form). Those pages are reached as part of a sequence.

How to Test

Check the site for at least two navigation mechanisms that allow users to reach any page: primary navigation menu, site search, sitemap, breadcrumbs, A-Z index, or table of contents.
Test the search feature to confirm it returns results from all sections of the site (not just one content type).
If a sitemap exists, verify it is up to date and covers all pages.
Navigate to a deep subpage and confirm you can reach it through at least two different paths.
Pass: At least two distinct mechanisms (e.g., navigation + search, or navigation + sitemap) allow users to locate any page on the site.
Fail: Only one navigation mechanism exists, or a secondary mechanism (search, sitemap) is broken or incomplete.

axe-core Rules

| Rule | What It Checks | |------|---------------| | — | No automated axe-core rule for this criterion. It requires manual review of navigation mechanisms. |