- Success Criterion 2.1.1
- Conformance level A
Control That Ignores Screen Reader Double-Tap Activation
2.1.1 — Keyboard
Scenario
Setting
An insurance company's claims form
What’s wrong
A control responds to touch or mouse but does not activate through screen reader gestures (double-tap with TalkBack/VoiceOver does nothing) — screen reader users can reach it but never use it.
Example
An insurance company's claims form runs into this exact issue: a control responds to touch or mouse but does not activate through screen reader gestures (double-tap with TalkBack/VoiceOver does nothing) — screen reader users can reach it but never use it.
Why it matters
Blind users, people with motor disabilities, and anyone operating the interface without a pointer. On an insurance company's claims form, this barrier means they lose track of where they are on the page.
How to test
With a screen reader active, use its 'activate' gesture (double-tap on touch, or Enter/Space on desktop) on the control: if the click event never fires, it fails.
How to fix
Wire click activation so screen reader double-tap (which fires click) works on the control.
Outcome
Corrected, an insurance company's claims form now lets a visitor complete the task using only the keyboard.
Who is affected
Blind users, people with motor disabilities, and anyone operating the interface without a pointer.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Feature That Only Responds to Mouse Events, Not the Keyboard
- Element That Loses Focus the Instant It’s Reached by Keyboard
- Clickable Element Acting Like a Link With No Real Keyboard Role
- Clickable Div With No Keyboard Focus or Key Handling at All
- Focusable Element That Enter and Space Don’t Actually Activate
- Custom Dropdown That Can’t Be Operated by Keyboard Arrows