WCAG 2.5.1 Pointer Gestures

Success criterion 2.5.1 helps people who cannot make precise or multi-finger gestures: people with tremors or limited dexterity, people using a head pointer, eye-gaze system or a mouth stick, and anyone using a phone with one hand. It is level A and part of EN 301 549 (clause 9.2.5.1).

What the criterion requires

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.

• A multipoint gesture uses two or more pointers at the same time, such as a two-finger pinch or spread to zoom.
• A path-based gesture is one where the movement along a specific path matters, such as a swipe, or drawing a shape.
• A single pointer without a path means a tap, click, double tap or long press.

The criterion applies to gestures the web content interprets, not to gestures that operate the browser or assistive technology (such as the browser's own pinch zoom). It does not prevent you from offering gestures, only from making them the only way.

Typical failures on an online shop

• a product image gallery that changes images only by swiping, with no previous/next buttons or thumbnails;
• a zoom feature that works only with a two-finger pinch inside a custom viewer;
• "swipe to delete" in the cart or wishlist with no delete button;
• a 360° product viewer that rotates only by drawing across it;
• a store locator map that zooms only with pinch, with no + and − buttons.

How to check it

Automated: there is no axe-core rule for this criterion. Gesture handlers live in scripts, and a scan cannot tell what a swipe does, so it needs a manual check.

By hand: on a phone or a touch-screen laptop, list every place where you swipe, pinch or draw: galleries, sliders, carousels, maps, viewers, cart actions. For each, find a way to do the same with single taps or clicks — buttons, arrows, thumbnails or zoom controls. Try it with a mouse as well, using only clicks.

How to fix it

• Add visible previous/next buttons and thumbnails to galleries and carousels.
• Add + and − controls to maps and zoomable images.
• Offer a delete or "remove" button next to any swipe action.
• Provide rotate buttons for 360° viewers.
• Keep the gestures for users who like them — just do not make them the only way.

Related criteria

• 2.5.7 Dragging Movements — dragging needs a single-pointer alternative.
• 2.5.2 Pointer Cancellation — accidental taps must be easy to cancel.
• 2.1.1 Keyboard — the same functions must also work from the keyboard.

Frequently asked questions

What gestures does WCAG 2.5.1 cover?

Multipoint gestures, such as a two-finger pinch or spread to zoom, and path-based gestures, where the path of the pointer matters, such as a swipe or drawing a shape. Each function they trigger must also work with a single pointer without a path.

Is keyboard support enough to meet 2.5.1?

No. W3C notes that a keyboard alternative alone does not satisfy 2.5.1, because many pointer users cannot use a keyboard. You need single-pointer controls such as buttons.

Does 2.5.1 apply to browser pinch zoom?

No. It applies to gestures that the web content itself interprets, not to gestures that operate the browser or assistive technology.