People do not all explore websites in the same way. Some users scan menus, some search by keywords, some rely on structured lists, and others move page by page. This success criterion exists to prevent content from being locked behind a single navigation path.
WCAG Success Criterion
2.4.5 Multiple Ways (Level AA)
More than one way is available to locate a web page within a set of web pages, except where the web page is the result of, or a step in, a process.
Key Definitions
Set of web pages
A set of web pages usually means an entire website or a clearly defined section of a site that shares navigation, purpose, and structure.
Sequential navigation
Sequential navigation means moving through content page by page using controls such as “Previous” and “Next,” commonly found in tutorials, articles, documentation, or paginated content.
Why This Matters
A single navigation method assumes that all users think, read, and explore content the same way.
That assumption fails for many people:
- Screen reader users may avoid large navigation menus and rely on search
- Screen magnifier users may struggle to visually scan dense navigation
- Users with cognitive disabilities may prefer overview-style navigation
- Some users understand content best by moving sequentially
Providing multiple ways to locate content reduces the number of steps required to find information and helps users understand how pages relate to one another.
Who This Helps
This criterion benefits:
- Screen reader users who locate pages using search or link lists
- Screen magnifier users who avoid visually complex menus
- Users with cognitive or memory limitations
- Users unfamiliar with a site’s structure
- Users who prefer exploration over hierarchy, or hierarchy over exploration
What “Multiple Ways” Means
To pass this criterion, users must be able to locate the same page using at least two different navigation methods.
Valid methods include:
- Global or local navigation menus
- Search functionality
- A site map or table of contents
- Sequential navigation (previous and next links)
- Categorised or related link lists
The methods do not need to be equally prominent. They must exist and be usable.
What Does Not Count as Multiple Ways
The following do not count as separate ways:
- Multiple links to the same page within the same menu
- Repeating the same navigation in different visual locations
- Cosmetic variations of the same navigation mechanism
This criterion is about choice, not duplication.
Assistive Technology Perspective
Different users rely on different navigation strategies:
- Screen reader users may skip navigation landmarks entirely and use site search to find pages by keyword
- Some screen reader users navigate by link lists rather than menus
- Screen magnifier users often rely on search or simplified lists because only part of the page is visible at once
Providing multiple ways allows users to choose the strategy that works best for them.
The Process Exception
This success criterion does not apply when a page is:
- The result of completing a task, or
- A required step within a process
Examples include:
- Checkout confirmation pages
- Search results pages
- Form submission success screens
- Account transaction confirmations
These pages are intentionally reachable only through the process itself. Requiring additional navigation paths would be misleading or impractical.
Common Ways to Satisfy This Criterion
Any two of the following are usually sufficient:
- Navigation menu and search
- Navigation menu and site map
- Sequential navigation and home page links
- Category lists and search
Even small sites can comply. For a site with only a few pages, linking all pages from the home page and providing return links may be enough.
Common Myths
Breadcrumbs alone satisfy Multiple Ways
Breadcrumbs show location, not alternative ways to locate content. They do not satisfy this criterion on their own.
Footer navigation alone is sufficient
Footer links count only if they provide a genuinely different way to locate content, not just a repeated menu.
Having search is enough, even if it barely works
Search must return relevant results. A broken or ineffective search does not satisfy the criterion.
Common Failure Patterns
Failures often occur when:
- Content is reachable only through a complex menu
- Search exists, but returns poor or irrelevant results
- Pages are accessible only through deep navigation paths
- There is no overview or orientation mechanism
- Navigation assumes visual scanning only
Technical Notes for Compliance
- Search must be usable with a keyboard
- Navigation mechanisms must be programmatically determinable
- A search that exists but does not reliably find content is a failure
- Navigation must work consistently across pages in the set
Relevant WCAG techniques include providing a site map and providing a search function, but no single technique is required.
Examples
Passing example
- A recipe website allows users to:
- Browse recipes by category
- Search recipes by ingredient
Both methods lead to the same recipe pages.
- A small business site includes:
- A navigation menu on every page
- Direct links to all pages from the home page
Users can reach any page either through the menu or via the home page.
Passing example (process exception)
An online banking confirmation page appears only after completing a transfer. There is no alternative way to locate this page, which is acceptable because it is the result of a process.
Failing example
A documentation site hides all articles behind a multi-level navigation tree and provides no search, site map, or index. Users must follow the exact hierarchy to find content.
Rule Description
Users must be able to locate a page using more than one method, unless the page is part of a task or process where alternative access would not make sense.
How to Evaluate This Criterion
- Choose a page within a set of web pages
- Identify all ways a user can locate it
- Count distinct navigation methods
- If at least two valid methods exist, the criterion passes
- If only one method exists and the page is not part of a process, the criterion fails
Wrapping Up
Multiple Ways is about flexibility, not redundancy. Users should not be forced to understand a site the same way the author does. By providing more than one path to content, authors reduce unnecessary steps, support different navigation strategies, and make content easier to find and understand.
When users can choose how they explore, they are far more likely to succeed.
