Skip to content
Barrierefrei²

Success criterion 2.5.1

2.5.1 Pointer Gestures

Level AOperable

One finger is enough – complex gestures are optional.

1. What is the goal of this criterion?

Touchscreens are everywhere today – from phones and tablets to self-service kiosks. But what happens when someone can’t move two fingers at once or can’t perform precise swipes? People who use a single finger or aids like a head or mouth stick hit a wall with apps and websites that rely on complex gestures.

The goal of WCAG Success Criterion 2.5.1 is clear: every function operated by multi-finger or path-based gestures must also work with a single pointer and no prescribed path.

2. What exactly does it require?

This criterion covers two kinds of gestures:

Multipoint gestures: actions that need several fingers or pointers at once – like the classic two-finger pinch to zoom or a three-finger swipe.

Path-based gestures: movements where not only the start and end points matter, but also the path in between. Examples include drawing a pattern to unlock or a swipe that has to start in a particular direction.

Every such gesture needs a single-pointer alternative – a tap, double tap or long press, for example on a button.

Exception: the multipoint or path-based gesture is essential to the function – such as drawing a signature.

Applies to your content only: gestures used by the browser, the operating system or assistive technology (such as zooming the whole page, or screen reader gestures) are not covered.

How it relates to dragging: simple dragging without a prescribed path, like drag and drop, is not a path-based gesture. Since WCAG 2.2, however, Dragging Movements applies, which also requires an alternative.

3. Why does it matter for accessibility?

Imagine you want to zoom into a map but can only use one finger – because of a motor disability or because you use an assistive device. Without an alternative to the two-finger gesture, that function is out of reach.

Simple pointer alternatives improve accessibility because they:

  • let people with motor disabilities use every function
  • make things easier for people who control a pointer with a head or mouth stick, eye tracking or voice control
  • help people with cognitive disabilities who find complex gestures hard to remember
  • allow people with tremors or other movement disorders to operate content reliably
  • make interfaces easier to understand for everyone – buttons are visible, gestures have to be known

And finally: they reduce frustration for everyone, for example when one hand is busy.

4. How to meet the criterion

The quality of your touch interactions decides whether your app or website is truly accessible. Here are some proven tips:

For multi-finger gestures:

  • Always provide additional buttons or controls.
  • Zoom in maps or image viewers: plus and minus buttons alongside pinch to zoom.
  • Navigation: a menu button rather than only a multi-finger swipe.

For path-based gestures:

  • Carousels and galleries: previous and next buttons in addition to swiping.
  • Pattern unlock: alternatives such as a PIN or password.
  • Swipe to delete in lists: an additional delete button or menu item.
<div class="map-controls">
  <button type="button" aria-label="Zoom in">+</button>
  <button type="button" aria-label="Zoom out">−</button>
</div>

Tools and techniques:

  • Use standard components and libraries that already come with controls.
  • Test your implementation with a single finger and with a mouse.
  • Make sure your own gestures don’t clash with browser or screen reader gestures.
  • Think in layers: simple controls as the foundation, gestures as a shortcut on top.

5. Why this criterion matters for businesses

2.5.1 is part of WCAG 2.1 Level A and therefore part of EN 301 549, the standard behind the European Accessibility Act. In Germany, the EAA is implemented by the BFSG, which has applied since 28 June 2025 to online shops, banking services and other consumer services, among others. Public sector bodies must meet it as well. This section is general information, not legal advice.

1. Reach more people

One-finger operation makes your app or website usable not only for people with disabilities, but also for anyone temporarily limited: with an arm in a cast, carrying a child or standing on a train holding on with the other hand.

2. Better usability

Visible controls are easier to discover than gestures. Nobody has to memorize gesture sequences – that reduces frustration for all age groups.

3. Technical robustness

Simple alternatives work reliably across devices, browsers and input methods. That cuts down on problems caused by misrecognized gestures.

6. The success criterion in the W3C’s words

Success Criterion 2.5.1 Pointer Gestures (Level A)

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.

Note: This requirement applies to web content that interprets pointer actions (i.e., this does not apply to actions that are required to operate the user agent or assistive technology).

In short: anything operated with multi-finger or path-based gestures must also work with a single pointer and no path-based gesture – unless the gesture is essential.

Official explanation from the W3C

The W3C explains every success criterion in depth – with intent, examples and techniques.

Understanding 2.5.1 (opens in a new tab)