Loading...
Loading content...
Loading content...
Allow users to switch between input methods (mouse, keyboard, touch) at any time.
Why it matters: Users may need to switch input methods depending on the task or fatigue.
Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.
What This Means: This success criterion requires that web content doesn't prevent users from switching between different input methods (mouse, keyboard, touch, voice, etc.) unless the restriction is essential for security or functionality. Users should be able to use whatever input method works best for them at any given time.
Why It's Important: Users may need to switch input methods for various reasons: fatigue, task requirements, device capabilities, or accessibility needs. Some users may start with one method and need to switch mid-task. Restricting input methods limits user choice and can create barriers for users with disabilities who rely on specific input methods.
Don't disable keyboard input on touch devices. Don't disable touch input on desktop. Allow users to switch between mouse, keyboard, and touch at any time. The only acceptable restrictions are for essential security (like password fields) or when the restriction is essential to the function itself. Even then, provide alternatives when possible.
This criterion ensures that all users can access and understand the content, improving their overall experience and ability to use the website effectively.
This criterion ensures that users with motor disabilities can access and understand the content, improving their overall experience and ability to use the website effectively.
Impact: When this criterion is properly implemented, it removes barriers for these user groups and creates a more inclusive web experience for everyone.
A form only accepts touch input and disables keyboard input.
<form ontouchstart="enableForm()" onkeydown="disableForm()">
<!-- Form only works with touch -->
</form>A form accepts input from any method (mouse, keyboard, touch).
<form>
<!-- Form works with any input method -->
<input type="text" name="name">
<button type="submit">Submit</button>
</form>This success criterion benefits the following user groups:
Tip: Use this checklist during development and testing to ensure all requirements for 2.5.6 Concurrent Input Mechanisms are met. Check off items as you complete them.
To meet this success criterion, ensure the following requirements are met:
While meeting the minimum requirements ensures compliance, consider these enhancements for a better user experience:
If my app is designed for touch, I don't need to support keyboard.
Users should be able to use whatever input method works for them. Even touch-first apps should support keyboard navigation.
Security features can restrict any input method.
Security restrictions are acceptable, but they should be minimal and clearly necessary. Don't use security as an excuse to restrict accessibility.
Touch-only interfaces that don't support keyboard.
Add keyboard support for all functionality. Ensure all interactive elements are keyboard accessible.
Mouse-only interactions without keyboard alternatives.
Provide keyboard alternatives for all mouse interactions. Use standard keyboard navigation patterns.
Unnecessary restrictions on input methods.
Remove restrictions unless absolutely essential. Allow users to use their preferred input method.
Note: These are official W3C resources for 2.5.6. For the most up-to-date information and detailed technical guidance, always refer to the official W3C documentation.
Implementing 2.5.6 Concurrent Input Mechanisms correctly requires understanding your specific context. Code solutions vary significantly based on multiple factors:
HTML, React, Vue, Angular, PHP, Python, and other frameworks each have different patterns and best practices.
Server-side rendering, client-side rendering, static generation, and hybrid approaches require different solutions.
Your existing components, styling approach, and UI library influence how accessibility must be implemented.
Your specific user base, content type, and interaction patterns determine the most appropriate implementation.
We provide tailored implementation guidance by analyzing your specific technology stack, coding patterns, design system, and project requirements. Our team reviews your codebase and provides custom solutions that integrate seamlessly with your existing architecture.
Get Custom Implementation HelpPart of
Operable PrincipleGuideline
2.5 Input Modalities