- Success Criterion 2.4.1
- Conformance level A
Page With No Way to Skip Repeated Navigation
2.4.1 — Bypass Blocks
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
On a ride-hailing app's trip booking screen, a visitor hits this wall: 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
Keyboard and screen-reader users who otherwise re-traverse repeated headers on every page. On a ride-hailing app's trip booking screen, this barrier means they can't operate the feature without a mouse.
How to test
Press Tab once on page load: check for a skip link or equivalent bypass mechanism — if nothing appears and no landmarks/headings substitute, it fails.
How to fix
A working bypass (a skip link visible on focus, landmarks (coded page regions), or headings) must let users jump straight to the main content.
Outcome
Corrected, a ride-hailing app's trip booking screen now lets a visitor keep track of where they are on the page.
Who is affected
Keyboard and screen-reader users who otherwise re-traverse repeated headers on every page.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- No Skip Link, Landmarks, or Headings to Bypass Navigation
- Skip Link That’s Broken and Doesn’t Actually Move Focus
- Skip Link That’s Never Visible, Even on Keyboard Focus
- Skip Link Placed After the Navigation It’s Meant to Skip
- Landmarks Used as a Bypass but Missing Key Content
- Bypass Mechanism With No Heading to Land On