# Pointer Gestures: A Single Tap Must Do It Too

Source: https://allyway.ai/glossary/pointer-gestures

Pointer Gestures is WCAG success criterion 2.5.1 (Level A). All functionality that uses multipoint or path-based gestures can also be operated with a single pointer without a path-based gesture, unless the gesture is essential.

Pointer gestures are touch or mouse movements that need two fingers at once or a precise path: pinch to zoom, two-finger taps, swipes and flicks, or drawing a shape. WCAG 2.5.1 asks that whatever these gestures do can also be done with a single tap or click. Many people cannot pinch, swipe accurately or use more than one finger.

## What it means

[WCAG 2.5.1 Pointer Gestures](https://www.w3.org/WAI/WCAG22/Understanding/pointer-gestures.html) is a Level A criterion. All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture – unless a multipoint or path-based gesture is essential.

| Gesture type | What it is | Typical examples |
|---|---|---|
| Multipoint | Two or more pointers at the same time | Pinch or spread to zoom, two-finger tap |
| Path-based | The movement along a specific path matters | Swipe or flick, tracing a shape |
| Single pointer (the alternative) | One tap, click, double tap or long press | Plus and minus buttons, previous and next buttons |

Only gestures your own content interprets count. Gestures of the operating system, the browser or assistive technology – swiping a notification away, the browser's back gesture, [screen reader](https://allyway.ai/glossary/screen-reader) swipes – are out of scope. Dragging is not a path-based gesture either; it has its own rule, [dragging movements](https://allyway.ai/glossary/dragging-movements) (2.5.7).

W3C names who benefits: people who cannot perform path-based gestures accurately, people using a head pointer or another device that works like a single pointer, and people with cognitive or learning disabilities who do not know a custom gesture.

> **Warning:** > **Keyboard support is not enough**
> W3C states that being operable by keyboard does not satisfy 2.5.1 on its own. [Keyboard navigation](https://allyway.ai/glossary/keyboard-navigation) is checked separately – pointer users also need simple taps or clicks.

## Examples

```html title="Example"
<!-- Map: pinch zoom stays, buttons offer the single-pointer way -->
<div class="map" id="map" aria-label="Store locations map"></div>
<div class="map-controls">
  <button type="button" aria-label="Zoom in">+</button>
  <button type="button" aria-label="Zoom out">−</button>
</div>

<!-- Carousel: swiping works, buttons do the same -->
<section aria-label="News">
  <button type="button" aria-label="Previous story">‹</button>
  <ul class="slides">…</ul>
  <button type="button" aria-label="Next story">›</button>
</section>
```

Both are W3C examples: a map with zoom buttons next to pinch zoom, and a carousel with previous and next buttons next to swiping. Give these buttons a clear name and enough [target size](https://allyway.ai/glossary/target-size).

**Do:** Do

Keep gestures as a shortcut, add buttons for zoom, previous and next, offer a "Confirm" button instead of "swipe to confirm", and let people sign by typing their name where a drawn signature is not required.

**Don't:** Don't

Make pinch the only way to zoom a product image, hide the carousel arrows on touch devices, or ask people to draw a pattern or swipe to unlock or confirm an order.

## How to check pointer gestures



## Questions

Q: Is swiping allowed under WCAG?
A: Yes. Swipe and pinch gestures can stay. WCAG 2.5.1 only asks that the same result is also possible with a single pointer without a path-based gesture, such as a tap on a button.

Q: Does a keyboard alternative meet 2.5.1?
A: No. W3C states that keyboard operability alone does not satisfy the criterion. People who use a pointer but cannot perform the gesture need simple taps or clicks.

Q: What is the difference between pointer gestures and dragging movements?
A: 2.5.1 covers multipoint gestures and gestures where the path matters, such as swipes. Dragging is not limited to a path and is covered by 2.5.7 Dragging Movements, which also asks for a single-pointer alternative.

Q: When is a gesture essential?
A: Rarely. W3C gives a signature as an example where the path itself may be the point. Confirming, unlocking or navigating are not essential and need a simple alternative.
