Understanding WCAG SC 2.5.1 Pointer Gestures
Version and Level: 2.1/2.2 (Level A)

WCAG SC 2.5.1 ensures that all functionality using multipoint or path-based gestures can also be operated with a single pointer without requiring a path-based gesture, unless such gestures are essential. This guideline applies to web content that interprets pointer actions, not to actions needed to operate the user agent or assistive technology.

Benefits:

  1. Accessibility for Users with Limited Motor Abilities: Enables users who cannot perform complex gestures to interact with content using simpler methods.
  2. Support for Users with Cognitive Disabilities: Simplifies interactions for users who may find multipoint or path-based gestures confusing.

Main Objective:

To provide alternative methods for controlling content that do not rely solely on multipoint or path-based gestures, ensuring that all users can interact with the content effectively, this success criterion focuses on the use of touch on screens. Authors often include many touch interactions with screens to enhance user excitement and engagement. However, tasks that are easy for most users can be very difficult or even impossible for others.

A path-based gesture involves touch interactions requiring sliding, dragging or drawing across the screen, reaching from point A to point B, and following a specific route with a midpoint. An example of this could be a slider component controlled by a thumb, which must follow a specific path to reach the endpoint. This can be challenging or impossible for some users, especially those who use head-pointer devices requiring a high level of coordination or speech-assistive technology where the user speaks into a microphone to perform tasks.

Multipoint gestures, on the other hand, require more than one touch input, such as using two fingers to pinch the screen to zoom in.

For example, a path-based gesture might be used to slide an image on a touchscreen. If a page contains a slider where only one image is visible in the viewport, users can slide right or left to bring the next image into view. However, users must follow a specific route on the touchscreen to complete the action. Users with motor disabilities who utilize speech-to-text assistive technologies may not be able to complete this task.

Success Criterion 2.5.1 requires that if multipoint or path-based gestures are used, the functionality must also be operable through single pointer methods such as tapping, clicking, double tapping, double-clicking, pressing, or clicking and holding.

Best Practices:

  • Use single-pointer gestures: Try to use single-pointer gestures if you can avoid multi-pointer or path-based gestures.

  • Provide alternatives for complex gestures: Provide alternatives like single taps, double taps, single clicks, or double clicks when multipoint or path-based gestures are available.

  • Provide single-point alternatives: Provide alternative mechanisms for multipoint or path-based gestures, such as buttons that require single-point activation to achieve the same result.

Examples & Explanation:

Example: A Custom Control Slider is provided to change the amount of a donation on the screen.

What Should Be Avoided

On touchscreens, users can operate the control only by sliding to the right or left to change the amount of the donation. They have to follow a specific path to reach their endpoint, with some midpoints along the way. There is no single-point activation or alternative mechanism available to complete the task.

Explanation:This is a failure because a path-based gesture is the only methodology used to operate the control. Users with head pointers will have a very difficult time sliding to the right in a straight line, as they will likely go up and down and fail the task.

What Should Be Done

The custom control slider should include both single-pointer activation along the slider, allowing single-tapping to move the thumb control along the slider and increment/decrement the donation amount. Right and left arrow buttons could also be available for incrementing and decrementing.

*Please access an example on the W3C WCAG working group website here. https://www.w3.org/WAI/WCAG22/working-examples/providing-single-point-control-slider/ .

Explanation:Since single-pointer activation and an additional single-pointer activation are available to users, this success criterion passes.

Next Up

Enhance your understanding with SC 2.5.2 - Pointer Cancellation. Learn to make pointer cancellations accessible for all users.

Go to SC 2.5.2