Loading Developer Playground

Loading ...

Skip to main content

Success Criterion · WCAG 2.5.1

Pointer Gestures

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.

Level AWCAG 2.1Operable2.5 · Input Modalities
Copy button ready

Goal

Ensure complex pointer gestures have simpler alternatives.

What to do

If functionality uses multi-point or path-based gestures (pinch, swipe paths), provide a single-pointer alternative.

Why it matters

Many users cannot perform complex gestures due to motor impairments or assistive technology limitations.

Success criterion

What WCAG 2.5.1 requires

Summarized directly from the official Understanding document so teams can quote the requirement accurately.

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.

Intent

Why WCAG created this requirement

  • Complex gestures can exclude users with limited dexterity.
  • Assistive technologies may not support multipoint gestures.
  • Provide simple controls (buttons, plus/minus, menu actions) as alternatives.

Benefits

Who gains when you pass

  • Users with motor impairments can operate features without complex gestures.
  • Switch and alternative input users can access functionality.
  • Users on devices that don’t support multipoint gestures can still use features.

Why it matters

User impact when this criterion fails

Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.

Users may be unable to zoom, rotate, or navigate content if only pinch/swipe gestures exist.

Path-based gesture requirements can block completion of core tasks.

Exception guidelines

Use the WCAG 2.5.1 exceptions correctly

Document the rationale for each exception and note which alternative support you provide.

Essential gesture

The gesture is essential to the activity.

Requirement

Only when the gesture itself is the purpose (e.g., a drawing app requiring freehand paths).

Overview

If your UI requires gestures like pinch-to-zoom, multi-finger swipes, or drawing paths, you must also provide a way to perform the same function with a single pointer and without requiring a path-based gesture—unless that gesture is essential.

  • Provide UI controls such as buttons for zoom, rotate, pan, and next/previous.
  • “Single pointer” includes mouse, stylus, single finger, and many AT outputs.
  • “Essential” is rare; most gestures can have control-based alternatives.

Reference: All summaries and highlights originate from Understanding WCAG 2.5.1 and the W3C quick reference.

Fast facts

Conformance level
Level A
WCAG version introduced
WCAG 2.1
Principle
Operable
Guideline
2.5 · Input Modalities

Examples

Make success tangible for teams

Share pass/fail snapshots to coach designers, engineers, QA, and content authors.

Map zoom

Pass

Pinch-to-zoom is supported, and plus/minus buttons also zoom.

Fail

Zoom works only via pinch gesture.

Carousel navigation

Pass

Swipe changes slides and there are Next/Previous buttons.

Fail

Carousel can be navigated only by swipe path gestures.

Evidence to keep

Document conformance decisions

Capture artifacts for VPATs, procurement reviews, and regression testing.

  • Document gesture alternatives and where controls are located.
  • Maintain a list of gesture-based features and their accessible controls.

Official resources

Deep dives and supporting material

Keep these links handy when writing acceptance criteria or responding to audits.

Implementation checklist

Capture progress and blockers

  • Inventory gesture-based interactions (pinch, swipe, drag paths, two-finger operations).
  • Add single-pointer, non-path alternatives (buttons, menus, step controls).
  • Ensure alternatives are keyboard accessible as well.
  • Document any essential-gesture cases and rationale.
  • Test on touch and mouse input devices.

Testing ideas

Prove conformance with evidence

  • Identify features requiring multipoint/path gestures.
  • Verify the same outcome can be achieved with a single pointer without path gestures.
  • Test with keyboard and switch-like input (single-point activation) where possible.
  • Confirm any claimed essential gesture is truly essential.

Related success criteria

More from Input Modalities (2.5)

View all criteria