2.5 Input Modalities · SC 2.5.6

AAA2 min read

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.

In plain language

A site shouldn't restrict people to one way of interacting (like only touch, or only mouse). People should be able to use any input method their device supports, and switch between them.

Why it matters

Someone might use a touchscreen laptop with an external keyboard and mouse plugged in, switching between touch, keyboard, and mouse as needed. If a site blocks one of those methods for no good reason, it takes away an option that person may depend on.

In practice

Fails this criterion

A web app only responds to touchscreen taps and ignores keyboard or external mouse input, even on devices that support both.

Meets this criterion

The same app works with touch, keyboard, mouse, or any combination, and the user can switch between input methods at any point.

Test it yourself

On a device with more than one way to interact (like a touchscreen laptop), switch between touch, mouse, and keyboard while using the site. Does everything keep working whichever input you use?

Read SC 2.5.6 on the official WCAG 2.2 specification ↗