<aside> 💡 A cross-cutting layer covering WCAG 2.5.x (Input Modalities) and mobile-specific concerns. Touch interaction is fundamentally different from keyboard/mouse — swipe, pinch, shake, and tilt have no keyboard equivalent unless you provide one.

</aside>

Why this matters

Screen reader users on mobile (VoiceOver on iOS, TalkBack on Android) interact via a completely different model: swipe to navigate between elements, double-tap to activate. Gestures that require multi-finger actions (pinch, two-finger swipe) are impossible when one finger is used for exploration.

WCAG 2.5.1 — Pointer Gestures (Level A)

Any action available via a path-based gesture (swipe, drag, pinch, multi-point) MUST have a single-pointer alternative.

Designer checklist

• Every swipe action has a button alternative (e.g. Next/Previous buttons alongside a swipeable carousel)
• Pinch-to-zoom has +/− buttons or a slider
• Drag-to-reorder has move up/down buttons or a position input
• Map pan/zoom has keyboard and button controls

Developer checklist

• Implement button alternatives for all gesture-only interactions
• Test with touch + screen reader (VoiceOver explore mode disables custom gestures)
• Don't require simultaneous multi-finger gestures for essential functionality

WCAG 2.5.4 — Motion Actuation (Level A)

Any action triggered by device motion (shake to undo, tilt to scroll, bump to share) MUST have a UI alternative AND the ability to disable the motion trigger.

Checklist

• Shake-to-undo → provide an Undo button