How accessible is your website?Start free check
WCAG 2.5.1Level AOperable

Pointer Gestures: A Single Tap Must Do It Too

Also called: Multipoint gestures, Path-based gestures, Swipe alternative, WCAG 2.5.1

Definition

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 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 swipes – are out of scope. Dragging is not a path-based gesture either; it has its own rule, 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.

Examples

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.

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

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

    Is swiping allowed under WCAG?

    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.

    Does a keyboard alternative meet 2.5.1?

    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.

    What is the difference between pointer gestures and dragging movements?

    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.

    When is a gesture essential?

    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.

    • Dragging Movements: Offer a Click Alternative

      Dragging Movements is WCAG success criterion 2.5.7. All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the browser provides it.

      Read definition: Dragging Movements: Offer a Click Alternative
    • Target Size: 24 × 24 px for Every Click Target

      Target Size (Minimum) is WCAG success criterion 2.5.8. The size of the target for pointer inputs is at least 24 by 24 CSS pixels, unless spacing, an equivalent control, inline text, the user agent or an essential presentation makes an exception.

      Read definition: Target Size: 24 × 24 px for Every Click Target
    • Keyboard Navigation: WCAG 2.1.1 Explained

      Keyboard navigation means that every function of a website can be reached and operated with a keyboard alone – usually with Tab, Shift+Tab, Enter, Space and the arrow keys. WCAG 2.1.1 requires it at Level A.

      Read definition: Keyboard Navigation: WCAG 2.1.1 Explained
    • Pointer Cancellation: Act on Release, Not on Press

      Pointer Cancellation is WCAG success criterion 2.5.2 (Level A). For functions operated with a single pointer, the down-event does not trigger the function, or completion on the up-event can be aborted or undone, or the up-event reverses it, unless the down-event is essential.

      Read definition: Pointer Cancellation: Act on Release, Not on Press

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done