Pointer Gestures
Tier 1 · The normative floor
Baseline compliance
What the normative text of WCAG 2.2 requires, and nothing more. Only a failure of this tier is a WCAG failure.
The bare minimum
Functionality that uses multipoint gestures (such as pinch) or path-based gestures (such as a swipe pattern) can also be operated with a single pointer without a path-based gesture, unless the gesture is essential.
Normative text
Verbatim from WCAG 2.2, W3C Recommendation 12 December 2024. Underlined terms are defined below.
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.
Not required by the normative text
Common claims that this criterion does not support. Don't log these as WCAG failures.
- Alternatives for browser or OS gestures such as pinch-zoom. W3C's informative note says it applies to gestures the content itself interprets.
Definitions used (3)
Glossary definitions are normative. Their notes are informative.
- functionality
-
processes and outcomes achievable through user action
- single pointer
-
an input modality that only targets a single point on the page/screen at a time – such as a mouse, single finger on a touch screen, or stylus.
Informative notes (1)
Single pointer interactions include clicks, double clicks, taps, dragging motions, and single-finger swipe gestures. In contrast, multipoint interactions involve the use of two or more pointers at the same time, such as two-finger interactions on a touchscreen, or the simultaneous use of a mouse and stylus.
- essential
-
if removed, would fundamentally change the information or functionality of the content, and information and functionality cannot be achieved in another way that would conform
Notes in the criterion Informative
WCAG 2.2 lists notes among its informative material, which "does not create requirements that impact a conformance claim." They help interpret the criterion but are not part of the floor.
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).
Tier 2 · The gap
Usability & user impact
Where content can meet this criterion and still make things harder for people with disabilities. These are not failures of SC 2.5.1, so raise them as usability defects. Known failures, including failures of related criteria, are listed in Tier 1.
A single-pointer alternative hidden in a menu technically passes but is rarely discovered.
Tier 3 · The golden path
Recommended best practice
The pattern that meets the floor, closes the gap, and avoids audit disputes. A recommendation, not a requirement.
Pair gestures with visible buttons, such as previous and next arrows on carousels and zoom buttons on maps.
W3C's Understanding document and techniques for SC 2.5.1 ↗ are informative: sufficient techniques show ways to pass, and documented failures show common ways to fail, but neither changes what the criterion requires.
How SC 2.5.1 maps to the WCAG 3 draft
From this site's reviewed map to the WCAG 3 editor's draft. It's an interpretation: W3C has not published a mapping.
Successor provisions
From WCAG 2.2, section 5.1: “The main content of WCAG 2.2 is normative and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative", diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.”