[Back to 2 Operable index](index.md)

# 2.5.6 Concurrent Input Mechanisms

- Level: AAA
- Guideline: 2.5 Input Modalities
- Principle: 2 Operable

## What it is

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.

## How to test

- Check: 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.
- Use the sufficient techniques below as acceptable methods when applicable.
- Confirm none of the common failures apply.

## Sufficient techniques (W3C)

- Only using high-level, input-agnostic event handlers, such as focus, blur, click, in Javascript (Potential future technique)
- Registering event handlers for keyboard/keyboard-like and pointer inputs simultaneously in Javascript; see Example 1 in Pointer Events Level 2 (Potential future technique)

## Common failures (W3C)

- F98: Failure due to interactions being limited to touch-only on touchscreen devices

## Resources

- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#concurrent-input-mechanisms
- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/concurrent-input-mechanisms.html
- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#concurrent-input-mechanisms

[Back to 2 Operable index](index.md)