What this criterion requires
Content must not restrict which input mechanisms are used - users may switch freely between touch, keyboard, mouse and stylus.
Who it helps
People who combine input methods, such as touch plus an external keyboard.
Example: fails vs passes
if (isTouchDevice) { disableKeyboardHandlers(); }/* handle pointer, touch AND keyboard events everywhere, always */
Users switch inputs mid-task (tablet + keyboard). Never gate features by detected input type.
How to meet and fix it
- Never gate features by input type detection; handle all input events
Common failures auditors find
- Touch-only handlers that ignore keyboard or mouse on hybrid devices
Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.
Sources
- W3C, Understanding 2.5.6: Concurrent Input Mechanisms - w3.org/WAI
- W3C, How to Meet 2.5.6 (quick reference) - w3.org/WAI/quickref
Last updated . Reviewed by the EqualWeb accessibility team.
Does your site pass 2.5.6?
Run a free automated check now, or have certified IAAP/CPWA auditors test every criterion and document the result.