2.5.6 Concurrent Input Mechanisms (Level AAA) — WCAG 2.1
WCAG 2.1 Success Criterion 2.5.6 Concurrent Input Mechanisms (Level AAA): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Operable → 2.5.6 Concurrent Input Mechanisms
2.5.6 Concurrent Input Mechanisms (Level AAA)
What it requires: Content doesn’t restrict use to only one input method (touch-only, mouse-only) when the underlying platform supports multiple concurrently — a user should be able to switch between touch, mouse, and keyboard freely, even on the same device session.
Common failure: A touch-optimized product configurator disables keyboard and mouse input entirely once it detects a touchscreen, even though the device (e.g., a touchscreen laptop) also has a keyboard and trackpad available.
Fix it: Avoid input-method detection that locks out other input types; support keyboard, mouse, and touch concurrently whenever the underlying device does.
In 2.5 Input Modalities: ← 2.5.5 Target Size
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.