Accessible Interactions
Keyboard and screen reader users run into small failures fast. A dialog closes and focus jumps back to the top of the page. A menu takes twenty Tab presses to get through. A status message changes and nothing is announced.
A lot of this is settled. All 11 systems that document it return focus to the element that opened a dialog, and all 11 make a menu, tab list, or toolbar one Tab stop with arrow keys inside. All 13 that set a bar for body text ask for 4.5:1 contrast. Where focus lands when a dialog opens is still argued over, with 4 of 10 picking the first interactive element and the rest picking the title, the safest action, or whatever suits the dialog.
- systems tracked
- 19
- sources cited
- 21
- evidence cards
- 177
- questions tallied
- 9
Popular questions
Each one is researched across every system we track. Pick one and it opens in chat, ready to send.
Systems tracked
The same core design systems are tallied on every topic, so answers compare like with like. See every source
- GOV.UK
- IBM Carbon
- Shopify Polaris
- Google Material 3
- Atlassian
- GitHub Primer
- Adobe Spectrum
- Microsoft Fluent
- Salesforce Lightning
- Ant Design
- Mozilla Acorn
- Stripe Apps
- shadcn/ui
- Porsche Design System
- Base Web
- GitLab Pajamas
- Radix UI
- USWDS
- Pinterest Gestalt
Got a accessible interactions question?
Your first 3 questions are free. Every answer comes with the sources behind it.