- Success Criterion 2.2.2
- Conformance level A
Pause Control That’s Present but Not Keyboard Accessible
2.2.2 — Pause, Stop, Hide
Scenario
Setting
A bank's mobile money-transfer screen
What’s wrong
Pause control present but not keyboard accessible or not labeled (mechanism unusable).
Example
Watch a bank's mobile money-transfer screen closely and you'll spot this: pause control present but not keyboard accessible or not labeled (mechanism unusable).
Why it matters
People with attention disabilities, low vision, or screen-reader users who lose place when content moves. On a bank's mobile money-transfer screen, this barrier means they are interrupted before they can finish reading.
How to test
Tab to the pause control: if it's not keyboard accessible, or has no accessible label, it's effectively unusable and fails.
How to fix
A visible, keyboard-usable control must pause, stop, or hide the moving, blinking, or auto-updating content.
Outcome
Corrected, a bank's mobile money-transfer screen now lets a visitor read the content without losing their place, specifically for the “Pause Control That's Present but Not Keyboard Accessible” issue on a bank's mobile money-transfer screen.
Who is affected
People with attention disabilities, low vision, or screen-reader users who lose place when content moves.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Auto-Scrolling Ticker or Slider With No Pause Button
- Embedded Animation That Blinks for Over 5 Seconds Nonstop
- Script-Driven Blinking Content With No Way to Stop It
- Content That Blinks Past 5 Seconds With No Stop Control
- Auto-Rotating Carousel Running Past 5 Seconds With No Pause
- Autoplaying Background Video With No Way to Pause It