Standards · WCAG 2.2

SC 2.5.1 Level A WCAG 2.1

Pointer Gestures

Any function that uses a multi-point or path-based gesture — pinch-zoom, two-finger rotate, swipe to delete — must also be operable with a single-point activation that does not require a path.

What it asks

If a feature can be triggered with a complex gesture — pinch, two-finger rotate, three-finger swipe, drawing a shape, flicking to dismiss — there has to be a simpler way to do the same thing with a single tap or click. A single-point activation does not depend on a path through space; tapping a button counts, dragging along a line does not.

The exemption is when the gesture is essential to the function: signing a signature, freehand drawing, a piano-keyboard app.

How to meet it

  • Pinch-zoom on an image or map: pair with visible zoom-in and zoom-out buttons.
  • Two-finger rotate on a photo editor: add a rotate-90 button or a numeric input.
  • Swipe-to-delete in a list: also surface a Delete button on tap or in a context menu.
  • Swipe-to-reveal actions (iOS mail-style): expose the same actions in a long-press menu or visible action row.
  • Drawing-pattern unlock: offer PIN or password as alternative.
  • Multi-touch UI controls (rotate, scale handles on a canvas): add input fields or button stepping.

Common failures

  • Image galleries with pinch-zoom but no zoom button.
  • “Pull to refresh” with no Refresh button visible.
  • Multi-finger gestures in custom widgets with no documented or visible single-tap equivalent.
  • Map widgets where the only zoom mechanism is the two-finger pinch.

Why it matters

Multi-point and path-based gestures rule out users with one functional hand, users on a head-pointer or mouth-stick, users with tremor that breaks the gesture mid-path, and anyone using a stylus or assistive pointing device that only emits single points. The single-tap alternative also helps everyone using the site one-handed on a phone — a much larger audience than the spec’s target population.