- Success Criterion 2.5.1
- Conformance level A
Gesture-Based Unlock Pattern Where a Simpler Input Would Work
2.5.1 — Pointer Gestures
Scenario
Setting
A webinar platform's registration form
What’s wrong
Signature/gesture unlock patterns where the *function* isn't essential to be path-based.
Example
<div ontouchstart="handleSwipe()"></div> <!-- swipe-only delete --> Why it matters
People with limited hand mobility and users of head-pointers, sticks, or eye-gaze systems.
How to test
Check whether a gesture-based unlock/signature pattern is genuinely essential to the function (e.g., an actual signature) or just used for an ordinary action that could be a button: the latter fails.
How to fix
A single-tap/click alternative must exist for every path-based or multi-point gesture.
<div ontouchstart="handleSwipe()"></div><button aria-label="Delete item">🗑</button>Any path-based or multi-touch gesture needs a single-tap alternative that does the same thing.
Outcome
On a webinar platform's registration form, this barrier is gone for people with limited hand mobility and users of head-pointers — they can finish what they came here to do.
Who is affected
People with limited hand mobility and users of head-pointers, sticks, or eye-gaze systems.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Feature Requiring a Swipe Gesture With No Tap Alternative
- Swipe-Only Carousel With No Next or Previous Button
- Map or Image Zoomable Only by Pinch Gesture
- Two-Finger Gesture Required With No Single-Pointer Option
- Pull-to-Refresh as the Only Way to Refresh Content
- Swipe-to-Delete Action With No Tap-Based Alternative