Skip to content

WAS Notes: WCAG 2.5 Input Modalities

I'm studying for the WAS certification. These are some of the notes I've taken recently.

Published:

2.5.1 Pointer Gestures - Level A

All functionality that uses path-based gestures or has multiple points can be operated with a single pointer without a path-based gesture unless it is essential. An example of a multipoint gesture is a two-finger pinch to zoom, and its single-point activation equivalent could be double tapping or clicking a zoom button.

How to Succeed

How to Fail

Allow users to operate functionality with pointer input, but not single-point activation alone.

2.5.2 Pointer Cancellation - Level A

For functionality that is operated with a single pointer, at least one of the following is true:

How to Succeed

How to Fail

Activate a button on the initial touch location rather than the final touch location.

2.5.3 Label in Name - Level A

For user interface components with labels including visible text, the accessible name contains that visible text.

How to Succeed

How to Fail

2.5.4 Motion Actuation - Level A

Functionality that can be operated through device or user motion can also be operated by user interface components, and the motion activation can be disabled to prevent accidental activation (e.g. shaking a phone to turn on the flashlight). This applies unless the motion is used through an accessibly supported interface or motion is an essential component.

How to Succeed

How to Fail

2.5.5 Target Size - Level AAA

The targets for pointer events are at least 44 by 44 pixels, unless:

How to Succeed

How to Fail

2.5.6 Concurrent Input Mechanisms - Level AAA

Web content does not restrict input modalities, except for when it is essential, required for security reasons, or required to respect user settings.

How to Succeed

Use high-level, input-agnostic event handlers like click, focus, and blur to ensure wide support for input mechanisms.

How to Fail

Limit interactions to touch-only on touchscreen devices.