2.4.5 Multiple Ways

Who it helps

People who use screen readers often prefer search over long menus. People with cognitive disabilities may find a sitemap or table of contents easier than nested navigation. Each person can pick the method that suits them.

How to meet it

• Offer at least two of these: a navigation menu, site search, a sitemap, a table of contents, or links between related pages.
• Make sure each method reaches every page in the set, not just the top-level sections.
• Link the sitemap or search from a consistent place, such as the header or footer.
• Know the exception: pages that are a step in a process, such as checkout, or the result of one, such as an order confirmation, are exempt.
• A small site where every page links to every other page already gives several routes, but check that each route is real.

Examples

<header>
  <nav aria-label="Main">
    <ul>
      <li><a href="/products/">Products</a></li>
      <li><a href="/support/">Support</a></li>
    </ul>
  </nav>
</header>

<header>
  <nav aria-label="Main">
    <ul>
      <li><a href="/products/">Products</a></li>
      <li><a href="/support/">Support</a></li>
    </ul>
  </nav>
  <form role="search" action="/search">
    <label for="q">Search the site</label>
    <input id="q" name="q" type="search">
  </form>
</header>
<footer><a href="/sitemap/">Sitemap</a></footer>

Common mistakes

• Counting the header menu and the footer menu as two ways when they contain the same links.
• Leaving pages out of the sitemap or search index, such as new blog posts or help articles.
• Offering search that only covers products and not the rest of the site.
• Removing the menu on mobile and leaving search as the only route.

Related criteria

• 2.4.8 Location
• 2.4.1 Bypass Blocks
• 3.2.3 Consistent Navigation

Official W3C explanation of 2.4.5