How accessible is your website?Start free check
WCAG 2.4.5Level AAOperable

Multiple Ways: More Than One Path to a Page

Also called: Site search and site map, Several ways to find a page, Navigation alternatives

Definition

Multiple ways is WCAG success criterion 2.4.5. More than one way must be available to locate a web page within a set of web pages – for example navigation plus search or a site map – except where the page is the result of, or a step in, a process.

Multiple ways means visitors can reach a page by more than one route – through the main menu and also through a search field, a site map or a list of links. People find content differently: one person browses the menu, another types a word into search. WCAG 2.4.5 makes sure no one depends on a single path.

What it means

WCAG 2.4.5 Multiple Ways is a Level AA criterion in WCAG 2.2. More than one way must be available to locate a web page within a set of web pages. A "set of web pages" is a collection that shares a common purpose and comes from the same author or organization. Language versions count as separate sets.

W3C lists sufficient techniques – any two of them together meet the criterion:

Way Typical example
Site search A search field in the header
Site map A page that links to every page of the site
Table of contents A contents list for a multi-page guide
Links to related pages "See also" links between articles
List of links to all other pages A small site's menu that lists every page
Links from the homepage to all pages Every page reachable from the start page

Exception: pages that are the result of, or a step in, a process do not need multiple ways. W3C names a shopping checkout, a bank transfer confirmation and search result pages as examples. Small sites still need some orientation: on a three- or four-page site linked from the homepage, links to and from the homepage can be enough.

Who benefits: screen reader and magnifier users often find search quicker than working through a large menu. People with cognitive disabilities may prefer an overview such as a site map. Others prefer to move through pages in sequence.

Examples

Example
<header>
  <nav aria-label="Main">
    <a href="/services">Services</a>
    <a href="/about">About us</a>
    <a href="/contact">Contact</a>
  </nav>
  <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>
</header>
<footer>
  <a href="/sitemap">Site map</a>
</footer>

The page offers three ways at once: the main menu, a labeled search form and a site map link in the footer. Each page should also have a clear page title, so visitors know where they landed.

Do

Combine the main menu with a site search or a site map, keep the site map up to date, put the search and site map link in the same place on every page, and link related pages to each other.

Don't

Leave pages reachable only through one deep menu path, publish pages that no menu, link or search can find, or offer a search that only covers part of the site.

How to check multiple ways

    Questions

    Does every website need a search function?

    No. Search is one option, not a must. A site map, a table of contents or links to all pages can serve as the second way next to the main navigation.

    Is a site map enough to meet WCAG 2.4.5?

    A site map together with the main navigation gives two ways and meets the criterion, as long as it really links to all pages of the set.

    Do small websites need multiple ways?

    W3C says even small sites should offer orientation, but on a three- or four-page site linked from the homepage, links to and from the homepage may be enough, as they also act as a site map.

    Are checkout pages covered by multiple ways?

    No. Pages that are a step in a process or its result – checkout steps, a confirmation page, search results – are exempt.

    How do I check other accessibility issues on my pages?

    Multiple ways needs a manual look at your navigation. The free WCAG scanner checks your pages for code-level issues such as missing page titles or unlabeled search fields.

    • Skip Link: Jump Straight to the Main Content

      A skip link is a link at the very top of a page that jumps to the main content, so keyboard and screen reader users do not have to pass the whole menu on every page. It is a sufficient technique for WCAG 2.4.1.

      Read definition: Skip Link: Jump Straight to the Main Content
    • ARIA Landmarks: Page Regions for Screen Readers

      ARIA landmarks are roles such as banner, navigation, main and contentinfo that identify the large regions of a page. Screen readers list them and let users jump directly to each region.

      Read definition: ARIA Landmarks: Page Regions for Screen Readers
    • Page Title: Write a Descriptive Title for Every Page

      The page title is the text in a page's <title> element. Browsers show it in the tab, screen readers announce it first when the page loads, and it should describe the page's topic or purpose.

      Read definition: Page Title: Write a Descriptive Title for Every Page
    • Consistent Help: Keep Support in the Same Place

      Consistent Help is WCAG success criterion 3.2.6. If help mechanisms such as contact details, a contact form, a self-help page or a chatbot are repeated on multiple pages of a site, they occur in the same order relative to other page content, unless the user changes it.

      Read definition: Consistent Help: Keep Support in the Same Place

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done