Goal
Give users more than one way to find pages.
Success Criterion · WCAG 2.4.5
Multiple Ways
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.
Level AAWCAG 2.0Operable2.4 · Navigable
Copy button ready
What to do
Provide at least two ways to locate a page within a set (e.g., nav, search, sitemap), except for steps in a process.
Why it matters
Different users prefer different navigation strategies; multiple paths reduce cognitive load and improve findability.
Success criterion
What WCAG 2.4.5 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
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.
Intent
Why WCAG created this requirement
- Multiple navigation methods support diverse user preferences and needs.
- Findability reduces frustration and abandonment.
- Process flows are exempt because they are accessed sequentially.
Benefits
Who gains when you pass
- Users with cognitive disabilities can use search when navigation is hard.
- Screen reader users can locate content through navigation, sitemap, or search.
- All users benefit from improved information architecture.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may be unable to find content if only one navigation method exists.
Deep pages may be “hidden” without search or sitemap.
Exception guidelines
Use the WCAG 2.4.5 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Process steps
Pages that are steps in a process are exempt.
Requirement
If a page is part of a process flow, it may be exempt.
Overview
Users should be able to find pages using more than one method—like site navigation plus search, or navigation plus a sitemap. Process steps (like checkout pages) are exempt.
- Common combinations: global navigation + search; navigation + sitemap; navigation + site map page.
- Ensure navigation structures are consistent and predictable.
- For single-page apps, provide internal navigation and search where appropriate.
Reference: All summaries and highlights originate from Understanding WCAG 2.4.5 and the W3C quick reference.
Fast facts
- Conformance level
- Level AA
- WCAG version introduced
- WCAG 2.0
- Principle
- Operable
- Guideline
- 2.4 · Navigable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Tool page
Pass
Tool is reachable via homepage category and via site map page.
Fail
Tool is only reachable from a single deep link with no navigation path.
Search
Pass
Search finds “contrast checker” tool page.
Fail
No search and no site map; only one nav path exists.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document information architecture (categories, navigation) and search coverage.
- Maintain a sitemap/index page and verify it stays updated.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Ensure global navigation exists for primary sections.
- Provide an additional findability mechanism (search, sitemap, category index, site map page).
- Ensure internal pages are linked from at least two places (nav + category listing).
- Document process flows and confirm exemption applies only to true process steps.
Testing ideas
Prove conformance with evidence
- Pick a representative page and verify at least two findability methods exist.
- Verify sitemap/search (if present) includes the page.
- Check navigation can reach the page through category paths.
Related success criteria
More from Navigable (2.4)
WCAG 2.4.1Bypass BlocksLevel AWCAG 2.4.2Page TitledLevel AWCAG 2.4.3Focus OrderLevel AWCAG 2.4.4Link Purpose (In Context)Level AWCAG 2.4.6Headings and LabelsLevel AAWCAG 2.4.7Focus VisibleLevel AAWCAG 2.4.8LocationLevel AAAWCAG 2.4.9Link Purpose (Link Only)Level AAAWCAG 2.4.10Section HeadingsLevel AAAWCAG 2.4.11Focus Not Obscured (Minimum)Level AAWCAG 2.4.12Focus Not Obscured (Enhanced)Level AAAWCAG 2.4.13Focus AppearanceLevel AAA