Understanding WCAG 2.5.1 Pointer Gestures.
What is it?
WCAG 2.5.1 Pointer Gestures is a Level A criterion.
Anything you can do with a swipe, a drag, a pinch, or any multi-finger move has to also work with a single tap or click. No tracing a path, no second finger required.
The fancy gesture can stay. It just can’t be the only way in.
Why it matters
Plenty of people can’t perform a precise swipe or a two-finger pinch. Someone using a head pointer, a mouth stick, or eye tracking has one point of contact to work with. Someone with a hand tremor can’t hold a steady drag.
If swiping is the only way to see the next photo, those users never see it.
Who it affects
People who are:
- using a head pointer, mouth stick, or eye tracking
- with tremors or limited dexterity who can’t trace a path
- using a single switch or one finger
- using voice control, who name a control rather than swipe it
Common failures
- Carousels where the only interaction is a swipe. The only way to reach the next slide is to swipe. No previous or next buttons, so a single tap gets you nowhere.
- Sliders where the only option is to drag. Setting the value means dragging the handle along its track. There’s no tap-on-the-track, no plus or minus buttons, and no field to type a number.
- List items where you have to swipe to reveal options. The only way to delete an item is to swipe the row open. Tap it and nothing happens, because the action is hidden behind the gesture.
- Maps where the only option for zooming is pinching. To zoom a map or an image, you have to pinch with two fingers. There are no plus or minus buttons to do the same thing with single taps.
Solution
Pair every gesture with a single tap. You don’t remove the gesture. You add a single-tap way to do the same thing, right beside it. Every swipe, drag, or pinch gets a visible control someone can tap, click, or activate with a single pointer.
For carousels
Add Prev and Next buttons and tappable dots. The swipe still works; now a single tap moves it too.
<button aria-label="Previous slide">‹</button>
<button aria-label="Next slide">›</button>For sliders
Add − and + buttons and a field to type the value. Drag still works; now taps and typing do the same job.
For swipe-to-reveal functionality
Put the action in the open: a visible Delete button, or a menu that reveals it. Swipe stays as the shortcut.
For maps
Add buttons that allow the user to tap to zoom in and out. Optionally add arrow buttons for panning as well.
Know the “essential” exception
The rule has one exception. If the gesture is genuinely the function, like drawing a signature or free-hand sketching, a single-tap version isn’t required.
A note on dragging
WCAG 2.2 added a related criterion, 2.5.7 Dragging Movements (Level AA), specifically for drag actions. If you build a single-tap alternative to your drag-and-drop, you cover both 2.5.1 and 2.5.7 in one move.
How to test
- Put one finger down and try to operate the whole page with single taps only. No swiping, no dragging, no second finger.
- For every gesture, ask: can I do this another way with a single tap? Advance the carousel? Set the slider? Zoom the map?
- If the answer is no, ask whether the gesture is essential. If it isn’t, add the simple alternative.
Closing
Gestures are fine. Gesture-only is the problem.
When a single tap can do everything a swipe can, your interface works whether someone swipes with a fingertip or reaches it another way.
Learn more
Read the full breakdown: a20y.com/wcag-plain-english/2-5-1-pointer-gestures/
Want more clear and actionable WCAG breakdowns? Check out wcagInPlainEnglish.com