gesture-alternatives
Design alternatives to gesture-based and motion-based interactions. Use when designing swipe actions, pinch-to-zoom, shake-to-undo, tilt controls, multi-finger gestures, or any interaction that requires specific physical movements. Triggers on: gesture, swipe, pinch, shake, tilt, multi-touch, two-finger, rotation gesture, device motion, accelerometer, gyroscope.
- Installs
- 74
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill gesture-alternatives- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads gesture-alternatives automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Gesture 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?
FAQ
What does the gesture-alternatives skill do?
Design alternatives to gesture-based and motion-based interactions. Use when designing swipe actions, pinch-to-zoom, shake-to-undo, tilt controls, multi-finger gestures, or any interaction that requires specific physical movements. Triggers on: gesture, swipe, pinch, shake, tilt, multi-touch, two-finger, rotation gesture, device motion, accelerometer, gyroscope.
How do I install gesture-alternatives?
Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill gesture-alternatives in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/gesture-alternatives/ (personal) or .claude/skills/gesture-alternatives/ (project).
Which AI agents can use gesture-alternatives?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is gesture-alternatives safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains gesture-alternatives?
It is published by owl-listener in owl-listener/inclusive-design-skills. It has 74 recorded installs.
More from owl-listener/inclusive-design-skills
plain-language-design
owl-listener/inclusive-design-skills
Write and review content for plain language accessibility. Use when writing interface copy, error messages, instructions, onboarding text, help content, legal or medical information, forms, or any user-facing text. Triggers on: plain language, reading level, simplify text, jargon, hard to understand, nobody reads this, unclear copy, rewrite, too complicated, ESL, literacy, readability.
keyboard-navigation
owl-listener/inclusive-design-skills
Design keyboard navigation and focus management for users who cannot or prefer not to use a mouse or touch screen. Use when designing any interactive interface — forms, menus, modals, tabs, carousels, drag-and-drop, data tables, or custom components. Triggers on: keyboard, focus, tab order, focus trap, skip link, arrow keys, keyboard shortcut, can't use mouse, motor disability, switch access, focus indicator, focus ring.
cognitive-load-assessment
owl-listener/inclusive-design-skills
Assess and reduce cognitive load in interfaces, flows, and content. Use when designing or reviewing any multi-step process, complex form, dashboard, decision flow, or information-dense screen. Triggers on: cognitive load, too complex, overwhelmed, too many steps, decision fatigue, confusing, information overload, simplify this flow. Applies to any interface where users must think, decide, or remember.
responsive-review
owl-listener/inclusive-design-skills
Review responsive and flexible layout for accessibility across devices, zoom levels, and orientations. Chains: responsive-accessibility, flexible-typography, information-density. Use when testing an existing interface across screen sizes and zoom levels for accessibility.
user-preference-respect
owl-listener/inclusive-design-skills
Design interfaces that detect and respond to system-level user preferences. Use when implementing dark mode, reduced motion, high contrast, text scaling, or any user preference that affects how the interface renders. Triggers on: user preference, system preference, prefers-reduced-motion, prefers-contrast, prefers-color-scheme, forced-colors, media query, user settings, system settings, accessibility settings, OS settings.
error-prevention-recovery
owl-listener/inclusive-design-skills
Design error prevention, error messages, and recovery flows for cognitive accessibility. Use when designing forms, checkout flows, account creation, settings, data entry, or any flow where users can make mistakes. Triggers on: error handling, error messages, form errors, validation, users make mistakes, users abandon, error recovery, undo, forgiving design.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.