2.4.5 Multiple Ways

WCAG 2.2 · 2.4.5 AA Operable

What it requires

More than one way must be available to locate a page within a set of pages — unless the page is the result of, or a step in, a process. In other words, users should not be forced to navigate in a single linear sequence to reach a given page; a second, independent route must exist.

Two of these mechanisms usually satisfy it: a site-wide navigation menu, a search field, a site map, an A–Z index, a table of contents, or a list of related pages. The process exception covers things like a checkout funnel, where adding a search box could let users skip required steps.

  • People with cognitive and learning disabilities, who may struggle to follow a single navigation structure and benefit from search or a direct index.
  • People who are blind or have low vision, for whom scanning a long menu with a screen reader is slow — search offers a faster path.
  • People with motor disabilities, who tire from extra clicks and prefer the shortest route to content.
  • Anyone who simply thinks differently about where information lives, e.g. searching by keyword rather than browsing categories.

How to detect it

Checks for Multiple Ways
Check How Catches it?
Count the mechanisms Manually confirm at least two of: nav menu, search, site map, index, or table of contents reach the page. Yes — primary manual check.
Process exception Judge whether the page is a step in a process (checkout, wizard); if so, the criterion does not apply. Manual judgement only.
Keyboard / screen reader Tab to each mechanism and confirm it is reachable and operable, not just visually present. Partial — confirms usability.
Automated tools axe and similar scanners cannot judge whether two valid routes exist. No — human review required.

How to fix it

  1. Decide whether the page is part of a process. If it is, the criterion is exempt — leave funnels linear.
  2. Provide a consistent site-wide navigation menu reachable from every page.
  3. Add a second independent mechanism — typically a search field, but a site map or A–Z index also counts.
  4. Expose both mechanisms in landmarks so assistive technology can find them, and keep them consistent across the page set.
<nav aria-label="Primary">
  <ul>…site menu…</ul>
</nav>

<search>
  <form role="search" action="/search">
    <label for="q">Search the site</label>
    <input id="q" name="q" type="search">
    <button type="submit">Search</button>
  </form>
</search>

Copy-paste tests

Automated coverage

There is no fully automated axe-core rule for 2.4.5 — a scanner cannot judge whether two independent ways to locate a page exist. This criterion needs manual review using the console check and steps below.

Run this in the browser console

multiple-ways-check.js 
// Read-only: surfaces wayfinding mechanisms for human review.
const mechanisms = {
  nav: document.querySelectorAll('nav, [role="navigation"]').length,
  search: document.querySelectorAll('search, [role="search"], input[type="search"]').length,
  siteMap: [...document.querySelectorAll('a')]
    .filter(a => /site\s?map|a-?z index/i.test(a.textContent)).length,
};
console.table(mechanisms);
const found = Object.values(mechanisms).filter(Boolean).length;
console.log(found < 2
  ? '⚠ Fewer than 2 mechanisms detected — review manually.'
  : 'At least 2 mechanisms present — confirm each actually reaches this page.');

What to check manually: confirm two of the mechanisms genuinely lead to this page (a disabled or decorative search box does not count), and decide whether the page is a step in a process (e.g. checkout) — if so, the criterion is exempt.