- Success Criterion 2.5.1
- Conformance level A
Custom Scroll Area Operable Only by a Flick Gesture
2.5.1 — Pointer Gestures
Scenario
Setting
An online marketplace's seller dashboard
What’s wrong
Custom scroll areas operable only via flick gestures.
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
Try scrolling a custom scroll area with a scrollbar, buttons, or keyboard instead of flicking: if flick gesture is the only way to scroll it, it 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 an online marketplace's seller dashboard, this barrier is gone for people with limited hand mobility and users of head-pointers — they reach the same outcome without extra effort.
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