- Success Criterion 2.4.5
- Conformance level AA
Website With No Real Second Way to Find Content
2.4.5 — Multiple Ways
Scenario
Setting
A ride-hailing app's trip booking screen
What’s wrong
No numbered W3C failure technique exists for this rule — it fails simply when the required feature/behavior is missing or inadequate (see the scenarios below).
Example
Here's a real case from a ride-hailing app's trip booking screen: no numbered W3C failure technique exists for this rule — it fails simply when the required feature/behavior is missing or inadequate (see the scenarios below).
Why it matters
People with cognitive or visual disabilities who prefer search, sitemaps, or alternate nav styles. On a ride-hailing app's trip booking screen, this barrier means they can't tell what's going on without extra effort.
How to test
Try to reach a deep page through at least two independent routes (navigation menu, search, sitemap, related links): if only one path exists, it fails.
How to fix
At least two working ways (navigation menu, search, sitemap, index) must exist to reach the content.
Outcome
Corrected, a ride-hailing app's trip booking screen now lets a visitor understand how the page is organized.
Who is affected
People with cognitive or visual disabilities who prefer search, sitemaps, or alternate nav styles.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Deep Pages Reachable Only Through One Navigation Path
- Site Search That’s Broken or Doesn’t Index Most Pages
- Sitemap Link That Leads to an Empty or Outdated Page
- Sequential-Only Article Pagination With No Table of Contents
- Search Results Page That Can Only Be Reached via Search
- Second Way to Navigate Available on Desktop but Not Mobile