Level AAAOperableNew in 2.1
2.5.6

Concurrent Input Mechanisms

Don't lock people into one way of interacting; let them switch freely between touch, mouse, keyboard, and other inputs.

In plain English

Lots of people use more than one input at once: a keyboard attached to a touchscreen tablet, a stylus alongside their fingers, a switch device with a mouse. This AAA rule says your store must not lock people into one input method. If it detects a touchscreen, it should not then ignore the keyboard or mouse.

This is almost never done on purpose. It usually creeps in when a component listens only for touch events, or a script assumes “touch device, so no keyboard.”

Who this is for

  • People who combine inputs, including many assistive-tech users pairing a specialised device with a mainstream one.

How to check and fix it yourself

On a touchscreen laptop (or a tablet with a keyboard), try operating your store with touch, then the keyboard, then the trackpad, without reloading. All should keep working together.

Touchscreen laptop: tap, then use keyboard, then trackpad, all live.  ✓
Site disables keyboard once a touch is detected.                      ✗

Where we can help

We test whether your store honours multiple input methods at once or silently drops one after detecting another. It is a subtle failure that only shows up on hybrid devices, exactly the kind of thing a manual review catches.

Frequently asked questions

What does concurrent input mechanisms require?+

Success Criterion 2.5.6 (Level AAA, added in WCAG 2.1) says a page must not restrict which input methods a person can use, they should be able to use touch, mouse, keyboard, stylus, or any combination, unless a restriction is essential or needed for security.

When would a site ever restrict input?+

It usually happens by accident: a site detects a touchscreen and disables mouse or keyboard handling, or a component only listens for touch events and ignores keyboard input. People who mix inputs (touchscreen laptop plus keyboard) then get stuck.

Who does this help?+

People often pair an assistive input with a mainstream one, a keyboard plugged into a tablet, a stylus alongside touch, a switch device with a mouse. Not locking them to a single detected input keeps all those combinations working.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 2.5.6?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit