About gesture-alternatives
A design skill that calls for a simpler alternative to every gesture, so people with motor limitations can complete the same tasks. It covers gesture types, alternative controls, discoverability, and customization.
Key features
- 01Adds button alternatives to path gestures
- 02Offers single-point options for multi-point gestures
- 03Provides on-screen controls for device motion
- 04Replaces timed gestures with untimed actions
- 05Supports gesture hints and customization
Use cases
- 01Check for a button alternative to swipe-to-delete
- 02Ensure zoom does not require pinching
- 03Add a visible button for shake-to-undo
- 04Review whether gestures can be disabled or remapped
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/gesture-alternativesin Claude Code to confirm it loaded.
Details
From the project READMEGesture Alternatives
Every gesture-based interaction must have a simpler alternative. Gestures that require specific physical movements exclude people with motor disabilities, limb differences, tremors, or limited range of motion.
Core Principle
Gestures are shortcuts, not gatekeepers. The feature they activate must always be reachable another way.
Gesture Types and Required Alternatives
Path-Based Gestures (swipe, draw, drag)
These require tracing a specific path. Many users cannot perform them.
- Swipe to delete → visible delete button
- Swipe to navigate → previous/next buttons
- Draw a shape → select from a menu of shapes
- Drag to reorder → move up/down buttons or numbered input
Multi-Point Gestures (pinch, rotate, two-finger scroll)
These require multiple simultaneous contact points.
- Pinch to zoom → zoom buttons (+/−) and text input for zoom level
- Two-finger rotate → rotation buttons or degree input
- Two-finger scroll → single-finger scroll or visible scrollbar
- Three-finger swipe → visible button or menu option
Device Motion (shake, tilt, rotation)
These require moving the entire device.
- Shake to undo → visible undo button (always)
- Tilt to steer → on-screen directional controls
- Device rotation for content → manual rotation toggle
Timed Gestures (long press, double tap)
These require precise timing.
- Long press for context menu → visible menu trigger (⋮ or ⋯)
- Double tap to zoom → zoom button
- Press and hold to record → toggle start/stop buttons
Design Patterns
Progressive Enhancement
- Build the button-based version first
- Add gesture support as an enhancement on top
- This guarantees the alternative always exists
Discoverability
- Gesture shortcuts should be documented but not required
- Show a hint on first use ("You can also swipe to delete")
- Provide a gesture guide in settings or help
- Never assume users know a gesture exists
Customisation
- Allow users to disable gesture controls entirely
- Allow remapping of gestures where possible
- Respect system-level gesture settings
Assessment Questions
- Does every gesture have a visible, single-action alternative?
- Can users who cannot perform multi-point gestures complete every task?
- Are device-motion interactions optional with on-screen alternatives?
- Can timed gestures be replaced with untimed actions?