What it asks for, in plain English
If something on your page is operated by a gesture that needs more than one finger (pinch to zoom, two-finger rotate) or that depends on the path the pointer takes (swipe to dismiss, drag along a slider, draw a shape to unlock), the same thing must also be possible with a single pointer doing simple presses: a tap, a click, or a double tap.
Buttons are the usual alternative: plus and minus for zoom, next and previous for a carousel, arrows for a slider. The gesture can stay for people who like it.
The exception is where the gesture is essential to the thing itself, such as a signature pad or a drawing tool. Dragging specifically is covered in more detail by 2.5.7.
This is an independent explanation. The binding wording is the W3C Recommendation, and the W3C's own Understanding 2.5.1 page has the full intent, techniques and definitions.
Who it affects
Someone with one working hand cannot pinch a map to zoom it and needs plus and minus buttons.
A person using a head pointer or mouth stick can click but cannot swipe in a smooth line.
Someone with a tremor cannot trace a path reliably and keeps triggering the wrong thing.
How to check it
- On a touch device, list every gesture the page responds to: pinch, two-finger scroll in a map, swipe between slides, drag to reorder.
- For each one, find a way to do the same with single taps: buttons, links or a form control.
- Try the page with a mouse only. Anything that cannot be done with clicks fails here too.
- Check embedded maps and carousels from third parties; they are the usual source.
What Websight checks for 2.5.1
Websight has no automated check for this criterion. It lists it in the manual checklist that comes with every report, so it is not forgotten.
Only a person can check this. A scanner cannot perform gestures or know what the page does in response.
Practical tips
- Add visible next and previous buttons to carousels and zoom buttons to maps.
- For swipe-to-dismiss, add a close button as well.
- Keep the gesture; the rule is about adding an alternative, not removing anything.
Other criteria in guideline 2.5, Input Modalities
- 2.5.2 Pointer Cancellation (level A)
- 2.5.3 Label in Name (level A)
- 2.5.4 Motion Actuation (level A)
- 2.5.7 Dragging Movements (level AA)
- 2.5.8 Target Size (Minimum) (level AA)