Skip to content
Barrierefrei²

Success criterion 2.5.6

2.5.6 Concurrent Input Mechanisms

Level AAAOperable

Flexibility in how you interact.

1. What is the goal of this criterion?

The digital world is as varied as a well-stocked toolbox – and so are the ways people interact with it. Some prefer tapping a touchscreen, others use a mouse, a keyboard, voice input or a switch. We often switch between input methods in the middle of a task.

The goal of WCAG Success Criterion 2.5.6 is that websites and apps don’t restrict this flexibility. People should be able to use all the input methods their device offers and switch freely between them.

2. What exactly does it require?

The rule itself is simple: web content does not restrict the input methods available on a platform – unless the restriction is essential, required for the security of the content, or needed to respect user settings.

In detail, that means:

  • A website must not block certain input methods just because it detected another one – someone using a tablet by touch can still use an attached keyboard or mouse.
  • Switching between input methods must be possible at any time, even in the middle of a task.
  • The criterion does not require every function to work with every conceivable input method. That everything works with a keyboard, for example, is covered by Keyboard.

Exceptions only apply to:

  • Essential restrictions: a touch-typing tutor may require the keyboard as the only input.
  • Security requirements: certain security-critical processes may require a specific input method.
  • User settings: if someone has disabled an input method themselves, that choice is respected.

The criterion is Level AAA – the highest level in WCAG.

3. Why does it matter for accessibility?

Imagine you’re on the go with a tablet and want to fill in a long form. The on-screen keyboard is tedious, so you connect a Bluetooth keyboard – but the website has detected a touch device and no longer responds to keyboard input. Frustrating, right?

Concurrent input mechanisms improve accessibility because they:

  • let people with motor disabilities choose the right input method for each situation and task
  • support people whose abilities vary, for example when strength fades over the course of the day
  • don’t get in the way of assistive technologies like switches, voice control or eye tracking, which are often recognized as a keyboard or mouse
  • increase efficiency, because everyone can pick the method that suits them
  • respect device diversity – from touch-only devices to tablets with keyboard and mouse

And finally: content stays future-proof because it doesn’t depend on one particular input technology.

4. How to meet the criterion

The good news: modern development practices often get you there automatically. Here are the key ground rules:

Use device-independent events:

  • Use general events like click, focus and blur rather than only touchstart or mousedown.
  • The click event is fired by mouse, touch, keyboard and many assistive technologies alike.

Don’t make assumptions about the input method:

  • Don’t detect the device and then switch off certain input methods.
  • Just because a touchscreen is detected doesn’t mean there’s no keyboard or mouse.
  • Don’t hide controls just because a particular primary input method was detected.

Support several inputs in parallel:

  • Use W3C Pointer Events, which handle mouse, touch and stylus in a unified way.
  • Add keyboard support on top of pointer events.
  • Don’t call preventDefault() on touch events in a way that suppresses mouse or keyboard events.
// Problematic: turns off keyboard and mouse as soon as touch is detected
if ("ontouchstart" in window) {
  enableTouchOnlyControls();
}

// Better: use real buttons – click responds to mouse, touch and keyboard
button.addEventListener("click", action);

Practical tips:

  • Connect an external keyboard and mouse to your tablet or phone and check that everything still works.
  • Use CSS media queries like pointer and hover only to optimize presentation, not to exclude input methods.
  • Switch input methods in the middle of a task when testing.

5. Why this criterion matters for businesses

2.5.6 is a Level AAA criterion and not legally required under the European Accessibility Act or its German implementation, the BFSG – the underlying standard EN 301 549 requires WCAG 2.1 Level AA. In practice, it’s often met with little effort, as long as nobody deliberately locks out input methods.

1. A better user experience

People are more efficient and satisfied when they can choose the input method that works best for them. A form that works smoothly with both touch and keyboard leads to fewer drop-offs.

2. Reach more people

You reach people with different abilities and preferences – people with motor disabilities as well as everyone who switches between tablet, keyboard and mouse.

3. Future-proof development

New devices and input methods keep appearing. Websites that aren’t tied to one particular input need fewer adjustments when new devices arrive.

This section is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 2.5.6 Concurrent Input Mechanisms (Level AAA)

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 short: content must not restrict the input methods a device offers – except for essential reasons, for security, or to respect user settings.

Official explanation from the W3C

The W3C explains every success criterion in depth – with intent, examples and techniques.

Understanding 2.5.6 (opens in a new tab)