Level
A
Since
WCAG 2.1
/ WCAG criterion

2.5.1 Pointer Gestures

Anything done with a two-finger pinch, a swipe or a drawn path must also work with a single tap or click, unless the gesture itself is essential.

/ What it requires

Some gestures need two fingers at once or a precise path. A multipoint gesture is a pinch to zoom, a two-finger tap or swipe, or a split tap with one finger resting while another taps. A path-based gesture depends on the route the pointer takes: a swipe or flick recognised only along a fairly straight line, or a shape that has to be drawn. This criterion asks that everything operated that way can also be operated with a single pointer and no path, such as a tap, a click, a double tap or a long press. It protects people who point with one finger, a stick, a head pointer, eye gaze or a speech-driven mouse, and anyone who cannot move precisely.

The exception is a gesture that is essential, such as a signature drawn by hand. The criterion covers gestures the content interprets, not those of the browser, the operating system or assistive technology, such as swiping back through history or a screen reader's own swipes. Dragging freely in any direction is not a path-based gesture; WCAG 2.2 covers it in 2.5.7 Dragging Movements, and the single-pointer alternative here may not rely on dragging alone. Keyboard support does not satisfy this criterion, because many pointer users have no keyboard at hand.

/ How pages fail it

  • A map zooms only with a pinch and has no plus and minus buttons.
  • A carousel moves to the next slide only on a horizontal swipe, with no previous and next buttons.
  • Swiping a row in a list to the left reveals a delete action that cannot be reached by tapping the row.
  • Drawing a Z on the screen undoes the last action, and there is no undo button.
  • A custom slider loses its thumb as soon as the pointer strays from the track, and clicking the track does nothing.

/ How to check it yourself

  1. On a phone or tablet, find everything that reacts to a pinch, a multi-finger tap or a swipe: maps, carousels, image galleries, swipeable list rows, sliders and drawing areas.
  2. For each one, try to reach the same result with single taps or clicks only: a button, a tappable track, a menu.
  3. Check that the alternative covers every outcome of the gesture, such as both directions of a swipe and every action a swipe reveals.
  4. Search the scripts for touchstart, touchmove and pointermove handlers and for gesture libraries such as Hammer.js. They show where the page interprets gestures itself.
  5. Confirm that the alternative is not itself a drag, which moves the problem to 2.5.7, and not a keyboard shortcut alone.

/ How to fix it

  • Add zoom in and zoom out buttons to every map and zoomable image, as button elements with accessible names such as "Zoom in" and "Zoom out".
  • Give carousels and galleries previous and next buttons that move one item per tap or click.
  • Expose every action hidden behind a swipe as a button in the row, or in a menu that opens on a tap.
  • Let the track of a slider take a click or tap to set the value, and add step buttons on either side. A slider built on input type="range" gets track clicks from the browser.
  • Pair any command drawn as a shape, such as a gesture for undo, with an ordinary button that does the same thing.

/ What our scanner checks

Nothing in our scan checks this criterion. A gesture lives in script, and the scan neither reads event handlers nor performs a pinch or a swipe. The HTML_CodeSniffer sniff for 2.5.1 raises only a notice, which the scan drops. In a manual audit each gesture and its single-pointer alternative is tried by hand on a touch device.

/ Who fails it, in our own measurements

The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.

One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.

/ Questions about this criterion

Is swiping a carousel a WCAG failure?

Not by itself. Swiping is allowed as long as the same result is available with a single pointer and no path, such as previous and next buttons that move one slide per tap or click. A carousel that moves only on a swipe fails 2.5.1.

Does keyboard support meet 2.5.1 Pointer Gestures?

No. Keyboard operation is required separately by 2.1.1 Keyboard, and it does not stand in for a pointer alternative. Many people who use a touch screen, a head pointer or eye gaze have no keyboard at hand, so they need a control they can tap or click.

Which gestures are outside the scope of 2.5.1?

Gestures that the browser, the operating system or assistive technology provide, such as swiping back through history, scrolling a page or a screen reader's navigation swipes. Gestures that are essential, such as signing your name, are excepted too. Dragging in any direction is not a path-based gesture and falls under 2.5.7 Dragging Movements.