Goal
Support multiple input methods without disabling user-preferred ones.
Success Criterion · WCAG 2.5.6
Concurrent Input Mechanisms
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.
Level AAAWCAG 2.1Operable2.5 · Input Modalities
Copy button ready
What to do
Do not restrict interaction to a single input mechanism; allow keyboard, mouse, touch, stylus, etc. to work concurrently.
Why it matters
Users may switch between input methods (e.g., keyboard + mouse, touch + keyboard, AT) and should not be blocked.
Success criterion
What WCAG 2.5.6 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
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.
Intent
Why WCAG created this requirement
- Users rely on a mix of input methods and assistive technologies.
- Input restrictions often break accessibility (e.g., disabling paste in password fields).
- Exceptions exist for essential needs, security, or respecting user settings.
Benefits
Who gains when you pass
- Users can choose their preferred input methods and switch as needed.
- Assistive technology users aren’t blocked by modality restrictions.
- Users with fatigue can alternate between input methods.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may be unable to complete tasks if keyboard or paste is blocked.
AT users may be locked out when scripts prevent default platform behaviors.
Exception guidelines
Use the WCAG 2.5.6 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Essential
Restriction is essential to the content.
Requirement
Only when truly essential.
Security
Restriction is required to ensure security.
Requirement
Only when demonstrably required for security.
Respect user settings
Restriction is needed to respect user settings.
Requirement
Do not override user preferences or platform settings.
Overview
Do not block input mechanisms (like disabling keyboard, disabling touch, preventing copy/paste, or overriding platform input behaviors) unless it’s essential, required for security, or respects user settings.
- Avoid preventing default input behaviors unnecessarily.
- Be cautious with security “hardening” that blocks paste or keyboard access.
- Respect user settings (e.g., OS keyboard navigation, reduced motion).
Reference: All summaries and highlights originate from Understanding WCAG 2.5.6 and the W3C quick reference.
Fast facts
- Conformance level
- Level AAA
- WCAG version introduced
- WCAG 2.1
- Principle
- Operable
- Guideline
- 2.5 · Input Modalities
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Paste in password field
Pass
Users can paste passwords from a password manager.
Fail
Paste is disabled to “improve security,” blocking password managers and AT.
Keyboard navigation
Pass
Keyboard navigation works alongside touch/mouse.
Fail
Keyboard shortcuts are blocked when touch is detected.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document a policy: do not block platform input modalities without strong justification.
- List any intentional restrictions and the exception category.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Audit event handlers for `preventDefault` that blocks keyboard/mouse/touch behaviors.
- Avoid disabling text selection, copy/paste, or context menus unless necessary.
- Ensure interactive controls work via mouse, touch, and keyboard.
- Document any input restrictions and justify them under exceptions.
- Test with assistive technologies that rely on platform input behaviors.
Testing ideas
Prove conformance with evidence
- Test the UI using mouse, keyboard, touch (if applicable), and trackpad.
- Verify copy/paste works in form fields where appropriate.
- Check that keyboard navigation is not disabled in any area.
- Confirm any restrictions are essential/security/user-setting based and not arbitrary.
Related success criteria