- Success Criterion 2.4.1
- Conformance level A
Single-Page App That Loses Its Skip Link After Navigation
2.4.1 — Bypass Blocks
Scenario
Setting
A subscription box service's account settings
What’s wrong
single-page app route changes rebuilding the page without any bypass because the "skip" only existed on first load.
Example
Picture a subscription box service's account settings: single-page app route changes rebuilding the page without any bypass because the "skip" only existed on first load.
Why it matters
Keyboard and screen-reader users who otherwise re-traverse repeated headers on every page. Here, on a subscription box service's account settings, the result is they can't operate the feature without a mouse.
How to test
Navigate within a single-page app to a new view: check whether the skip link (present on first load) still works or was never rebuilt for the new view.
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
After the fix, the same visitor to a subscription box service's account settings can now complete the task using only the keyboard.
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
- Page With No Way to Skip Repeated Navigation
- 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