WCAG 2.1 · Level AAA · Operable
2.5.6 Concurrent Input Mechanisms
Manual verification
How to validate 2.5.6 by hand
Check that using a keyboard, pointer, touch, or another input method does not disable the other input methods.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Operate the same feature using keyboard, mouse, touch, and available assistive input in a representative session.
- Switch input methods without reloading and repeat the task after each switch.
- Check whether any input method is unavailable because of a user setting or an essential security constraint.
Evidence to record
Record the feature, input method used first, method that became unavailable, and any user-controlled or essential exception.
Scope and exceptions
This is Level AAA. The criterion does not require every feature to support every conceivable device, but one input method must not disable another unless an exception applies.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.