2.5.1 Pointer Gestures
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless the multipoint or path-based gesture is essential.
Last reviewed: September 9, 2026
Understanding 2.5.1
Gestures like pinch-to-zoom, two-finger scroll, or swipe-to-navigate require precise, coordinated pointer movement that many people cannot perform reliably. Users with tremors, limited range of motion, missing limbs, or those using a mouse, head pointer, or single-switch device may only be able to produce a simple tap or click at one location. This criterion requires that any gesture-driven function also be reachable through a single-pointer action (a tap, click, or press-and-release at one point) so it isn't locked behind fine-motor or multi-touch dexterity.
How to Meet It
Frequently Asked Questions
Does this mean I can't offer swipe gestures at all?
No. You can still offer gestures as a convenience for users who can perform them, but you must also provide a single-pointer alternative that achieves the same result, such as arrow buttons alongside a swipeable image gallery.
What actually counts as "essential" here?
Essential means the path or multipoint nature of the gesture is inherent to what the function does: for example, a two-finger rotate gesture in a drawing app that specifically teaches rotation, or a signature pad that must capture the actual path drawn. A carousel or map doesn't meet this bar because the same navigation/zoom outcome can be reached another way.
Related Success Criteria
Quick Facts
- Criterion2.5.1
- LevelA
- IntroducedWCAG 2.1
Automate Compliance
AccessiSight automatically scans and identifies 2.5.1 issues in your codebase.
Try Scanner Free