What WCAG 2.5.1 Requires
Functionality that uses a multi-point or path-based gesture (pinch to zoom, swipe to delete) must also be operable with a single, simple pointer action, unless the gesture is essential.
Can AccessBell Test This Automatically?
Not fully. Like most WCAG criteria that depend on meaning or context, this one needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it never gets missed.
How to Test It by Hand
Try operating every touch-based interaction with a single tap or click instead of a multi-point gesture.
Common Failures
- A carousel can only be advanced by swiping, with no visible next/previous buttons.
- A "swipe to delete" list item has no button-based alternative.
Related Criteria in Input Modalities
WCAG 2.5.1 Questions
What does WCAG 2.5.1 require?
Functionality that uses a multi-point or path-based gesture (pinch to zoom, swipe to delete) must also be operable with a single, simple pointer action, unless the gesture is essential.
Can AccessBell test WCAG 2.5.1 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 2.5.1?
Level A, added in WCAG 2.1.
Sources
- W3C: Understanding 2.5.1 Pointer Gestures (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.