Success Criteria

WCAG 2.4.5 Multiple Ways

Success Criterion 2.4.5 requires that more than one way is available to locate a web page within a set of related pages — except where the page is the result of, or a step in, a process. It's a Level AA criterion under Guideline 2.4 (Navigable).

Why one path isn't enough

Different users navigate most effectively in different ways: some prefer typing a specific search query, others prefer browsing a hierarchical menu, others rely on a sitemap page to see the full structure at a glance. Relying on only one of these excludes users for whom that particular method isn't the most effective, or genuinely isn't usable — a search box alone doesn't help someone who doesn't know the right terminology to search for; a deep, unlabeled navigation menu alone doesn't help someone who'd find a direct search faster.

Accepted "ways" under this criterion

• A site search function
• A site map listing pages in a structured overview
• Site-wide navigation present consistently across pages, letting users browse to any section
• A table of contents (for a single long document, functioning similarly to a site map)
• Links between related pages (a list of related articles, breadcrumb navigation) that collectively provide alternate paths to reach content

Any two of these, present together, typically satisfy the criterion.

The process-step exception

Pages that are one step in a multi-step process (a checkout flow, a multi-page form submission) are exempt — it wouldn't make sense to require multiple discovery paths to "step 3 of checkout," since that page only has meaning as part of a specific sequential flow, not as an independently-discoverable destination.

Where this fits into a broader site-architecture check

This criterion is really a proxy for overall site navigability — a site with only a single, narrow way to find content (no search, no real navigation menu, no sitemap) tends to be difficult to use for reasons well beyond formal WCAG compliance. Satisfying it usually falls out naturally from otherwise-reasonable information architecture, rather than requiring dedicated extra accessibility work.

Common questions

What is WCAG 2.4.5?

A Level AA criterion requiring at least two ways to find a given page on a site, such as navigation menus, a search, a sitemap, or an A-Z index.

What is the exception to 2.4.5?

Pages that are a step within a process (like a checkout flow) are exempt, since reaching them out of order wouldn't make sense.

How do I comply?

Provide any two of: persistent navigation, a search feature, a sitemap, a site index, or links between related pages.