spec 4 linked patterns checked
W3C WAI: Understanding SC 2.5.1 Pointer Gestures
Documents that functionality using multipoint or path-based gestures must also be operable with a single pointer without a path-based gesture, including examples such as pinch, two-finger gestures, swipes, carousels, map zoom controls, and simple pointer alternatives.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Long press | Choose long press when the design problem is a sustained-contact gesture and its threshold, feedback, cancellation, and equivalent action path. | Long press starts only from a target that intentionally supports sustained contact. | Supports non-gesture alternatives where gesture behavior is demanding or path-based. |
| Pull to refresh | Choose pull to refresh when the design problem is the vertical top-of-scroll drag that refreshes the current data set. | Pull-to-refresh begins only when the intended scroll container is at its top boundary and the user drags downward beyond normal scroll tolerance. | Supports alternatives for path-based gestures. |
| Swipe action | Choose swipe action when the design problem is a horizontal item-level gesture that reveals or commits row-scoped commands. | Swipe action starts only from the intended row and horizontal axis; vertical scroll and pull-to-refresh win when movement is primarily vertical. | Supports alternatives for path-based gestures. |
| Touch gesture | Choose touch gesture when the design question is the recognition, feedback, fallback, and cancellation behavior of touch input itself. | The gesture starts only from the intended target or gesture region, not from unrelated content. | Supports single-pointer alternatives for multipoint and path-based gestures such as pinch, two-finger gestures, and carousel swipes. |
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: W3C WAI. Last checked: .