WCAG 2.5.1 Pointer Gestures
Success Criterion 2.5.1 requires that functionality using multipoint gestures (pinch-to-zoom, two-finger rotate) or path-based gestures (a swipe following a specific trajectory) can also be operated with a single pointer, without needing to follow a specific path — unless the multipoint or path-based gesture is essential. It's a Level A criterion under Guideline 2.5 (Input Modalities), added in WCAG 2.1.
Who this protects
Someone using a single stylus, a mouth stick, or someone with limited hand/finger mobility may be able to perform simple, single-point taps or clicks but genuinely can't execute a two-finger gesture or trace a precise path with a pointer. If a two-finger pinch is the only way to zoom an image, or a specific swipe path is the only way to trigger an action, those users are excluded entirely from that functionality.
What needs a single-pointer alternative
- Pinch-to-zoom on an image gallery or map — needs alternative zoom controls (buttons, a slider) operable with a single tap
- Two-finger rotate on a photo editor — needs a single-pointer alternative (rotate buttons, a dial control)
- Swipe-to-delete on a list item — needs an alternative single-tap action (a visible delete button)
- Drawing/signature with a required specific path — see Dragging Movements for the closely related requirement around drag interactions specifically
The "essential" exception
Where the specific gesture is fundamentally what the function is about — a freehand drawing or signature-capture tool, where the actual path traced IS the content being created — no single-pointer alternative is required, since providing one would defeat the purpose of the feature itself.
Practical guidance
The safest default for any touch interaction: always provide a conventional single-tap/click alternative alongside a more elaborate gesture, rather than making the gesture the only path. Most well-designed touch interfaces already do this naturally (a zoom slider next to pinch-to-zoom, an explicit delete button next to swipe-to-delete) — the failure mode is specifically when the gesture is implemented instead of a simpler alternative, not alongside one.
Common questions
- What is WCAG 2.5.1?
- A Level A criterion: functionality relying on complex gestures (multi-finger or path-based) must offer a simple single-pointer alternative like a tap or button.
- What is an example?
- A map that only zooms by pinch should also offer +/- buttons; a carousel that only advances by swipe should also have arrow controls.
- Why does 2.5.1 matter?
- Users with motor impairments, and those using a head pointer or single switch, often can't perform multi-finger or precise path gestures.
Related articles
Want to see how your own site scores?
Run a free accessibility scan