WCAG 2.5.6: Concurrent Input Mechanisms

WCAG 2.5.6 Concurrent Input Mechanisms is a level AAA success criterion from WCAG 2.1. People can switch between keyboard, mouse, touch and other inputs without restriction, unless the restriction is essential.

Someone may tab through a form and then use the mouse, or the reverse.

How to test

Mix keyboard and mouse on the same page. Nothing should lock you to one.

How to fix

Do not block input types with scripts that assume only touch or only mouse.

Example that fails

A script calls preventDefault on all mouse events after the first Tab.

Example that passes the check

Mouse and keyboard both work throughout checkout.

Shopify

Remove scripts that disable mouse after detecting a keyboard.

WooCommerce

Keep both input types on the checkout.

WordPress

Do not restrict input type.

Wix

Do not add code that blocks a pointer after keyboard use.

Related fixes