Success criterion 2.5.6
Concurrent Input Mechanisms
Content does not restrict the input modalities available on a platform.
- Level AAA
- Principle 2: Operable
- Guideline 2.5: Input Modalities
In a user’s words
“I plugged in my keyboard and your app told me to use the touchscreen. I'll decide how I type, thanks.”
What each role can do
- Product manager
- Support touch, keyboard, mouse and voice together.
- Designer
- Do not design flows that assume one input type.
- Developer
- Avoid input-type detection that disables other inputs; listen for pointer and keyboard events together.
- Tester
- Switch between touch, keyboard and mouse in the middle of a task and confirm everything keeps working.
Once it is fixed
“Touch, keys, mouse, whatever my day calls for. Thanks for not picking for me!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 2.5.6 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.