2.5.1 Pointer Gestures (Level A) — WCAG 2.1
WCAG 2.1 Success Criterion 2.5.1 Pointer Gestures (Level A): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Operable → 2.5.1 Pointer Gestures
2.5.1 Pointer Gestures (Level A)
What it requires: Any functionality that requires a multi-point or path-based gesture (pinch-to-zoom, swipe) also has a single-pointer alternative (tap, click) — unless the gesture is essential.
Common failure: A product image gallery only supports swipe-to-advance on mobile, with no visible tap-to-advance arrow buttons, locking out users who use a single-switch or adaptive pointer device that can’t perform a swipe.
Fix it: Add visible tap/click controls (arrow buttons) alongside any swipe gesture, so the same function is reachable with a single, simple pointer action.
In 2.5 Input Modalities: 2.5.2 Pointer Cancellation →
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.