This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung

Accessibility

Why do swipe gestures need a simple click alternative?

Swipe and multi-finger gestures need a simple alternative, because many people can't perform them: anyone operating a device with a mouth stick, a stylus, or shaking hands can manage a single tap — but not precise swiping or two-finger zooming. WCAG criterion 2.5.1 therefore requires an equivalent route with simple clicks or taps for every path-based or multi-finger gesture.

Image galleries, map zoom, and page-turning: the most common gesture traps

Three patterns keep coming up. First, the image gallery that can only be advanced by swiping — the solution is visible next and previous buttons beside the images. Second, the embedded map that only zooms with a two-finger gesture — the solution is plus and minus buttons at the edge of the map. Third, lists or tiles where a swipe reveals actions like delete — the solution is a visible menu button on each entry. The gesture may stay; it's the faster route for many people. What's required is the second, simple route to the same goal.

How the audit service reports this criterion

Whether every gesture function on your page has a click alternative can't be reliably determined by machine: the check would have to actually perform swipe gestures on the page and compare their effect against all visible buttons. Our measurement engine deliberately works passively and doesn't trigger gestures. The report therefore openly marks the criterion as a manual check point — part of our catalogue, which names every WCAG criterion individually: passed, violated, needs manual review, or not automatable. That way every seal claim stays backed by the measurement.

Examples

Image gallery only by swiping

Not met

<div class="galerie" data-swipe="true">…</div>

Passes

<div class="galerie" data-swipe="true">
  <button type="button" class="zurueck">Vorheriges Bild</button>
  <button type="button" class="weiter">Nächstes Bild</button>
  …
</div>

Each gesture with several fingers or a path gets an alternative with one click.

Check every image gallery on your website: are there visible next and previous buttons in addition to swiping?
Add plus and minus buttons for zoom on embedded maps.
Offer a visible button with the same function for every swipe action in lists.
Test your website once completely with a single finger and no swiping — every function must stay reachable.

Deutsche Fassung dieser Seite

FAQ

Which gestures does WCAG 2.5.1 cover?

All gestures that follow a path or need multiple fingers: swiping to page forward, dragging along a line, two-finger zoom, three-finger taps. An equivalent route with simple clicks or taps must exist for every such function — buttons for paging or zooming, for instance. Simple taps and double-taps already count as simple input.

Who can't perform swipe gestures?

People with motor impairments — from tremors, paralysis, or joint conditions, for instance —, users of mouth sticks and input aids, and people who operate their device with one hand or a stylus. For them, a precise, continuous movement across the screen is difficult or impossible, while a single tap on a button works well.

Do I have to remove swipe gestures from my website?

No. Gestures may stay, and for many users they're the most convenient route. What's required is a second, equivalent route with simple taps or clicks: forward buttons next to the swipe gallery, zoom buttons next to the two-finger gesture. Having both routes side by side makes the function operable for everyone, without taking anything away from anyone.