What this criterion requires
Functionality that uses multipoint gestures (pinch) or path-based gestures (swipe, drag-to-reveal) must also work with a single pointer without a path - taps and clicks.
Who it helps
People with motor disabilities using head pointers, eye trackers or one finger.
Example: fails vs passes
carousel.addEventListener("touchmove", handleSwipe); /* swipe is the only way */
<button class="car-prev">Previous</button>
<button class="car-next">Next</button> <!-- alongside the swipe -->Every path-based or multipoint gesture needs a single-tap alternative.
How to meet and fix it
- Add buttons alongside gestures: +/- next to pinch-zoom, prev/next next to swipe carousels
Common failures auditors find
- Swipe-only carousels and pinch-only maps with no button equivalents
Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.
Sources
- W3C, Understanding 2.5.1: Pointer Gestures - w3.org/WAI
- W3C, How to Meet 2.5.1 (quick reference) - w3.org/WAI/quickref
Last updated . Reviewed by the EqualWeb accessibility team.
Does your site pass 2.5.1?
Run a free automated check now, or have certified IAAP/CPWA auditors test every criterion and document the result.