- Success Criterion 2.1.1
- Conformance level A
Overlay or Menu With No Keyboard-Operable Close Control
2.1.1 — Keyboard
Scenario
Setting
An e-book reader's library page
What’s wrong
An overlay or menu has no close control that keyboard or screen reader users can operate — it can only be closed by tapping or clicking outside it.
Example
A tester reviewing an e-book reader's library page finds this: an overlay or menu has no close control that keyboard or screen reader users can operate — it can only be closed by tapping or clicking outside it.
Why it matters
Blind users, people with motor disabilities, and anyone operating the interface without a pointer. The practical effect on an e-book reader's library page: they can't operate the feature without a mouse.
How to test
Tab into an open overlay/menu and look for a close control: if the only way to close it is clicking outside, keyboard users can't dismiss it.
How to fix
Provide a visible, focusable close button (and Esc support) in every overlay/menu.
Outcome
That one change on an e-book reader's library page means they reach and operate the control without a mouse.
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