Resource guide
2.5.6 Concurrent Input Mechanisms
Content must not restrict use of input modalities. Users must be able to switch between keyboard, mouse, touch, and other inputs freely.
By Calling All Minds·Last updated April 2026
Success criterion
Conformance level
Enhanced accessibility — beyond the legal minimum.
What it means
Some applications detect the input type being used and switch to a mode that only supports that input. For example, switching to a touch-only mode when a touchscreen is detected, removing keyboard controls.
Users may switch between input methods mid-task: beginning with a mouse and finishing with a keyboard, or using voice control alongside a touchscreen. Content must not restrict this.
The exception is when restricting to a specific input is essential to the security or validity of the function, such as a handwritten signature requirement.
In practice
Do not use JavaScript to detect input type and then disable other input methods.
Ensure that adding a mouse or keyboard does not break touch functionality, and vice versa.
Test applications with multiple input methods connected simultaneously.
Common failures
- Application that detects touch input and hides keyboard navigation
- Site that removes hover states when a touchscreen is detected, breaking keyboard focus styles
AXS Audit
AXS Audit checks your site against 2.5.6 and flags issues your team can act on straight away. It covers criteria that automated scanners often miss.