Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
owl-listener avatar

Gesture Alternatives

  • 33 installs
  • 87 repo stars
  • Updated June 9, 2026
  • owl-listener/inclusive-design-skills

Helps with ai & agent building tasks during AI-assisted development.

About

gesture-alternatives is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

  • gesture-alternatives
  • AI & Agent Building
  • AI-coding skill

Gesture Alternatives by the numbers

  • 33 all-time installs (skills.sh)
  • Ranked #8,975 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/owl-listener/inclusive-design-skills --skill gesture-alternatives

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs33
repo stars87
Last updatedJune 9, 2026
Repositoryowl-listener/inclusive-design-skills

What it does

Helps with ai & agent building tasks during AI-assisted development.

Files

SKILL.mdMarkdownGitHub ↗

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

1. Does every gesture have a visible, single-action alternative? 2. Can users who cannot perform multi-point gestures complete every task? 3. Are device-motion interactions optional with on-screen alternatives? 4. Can timed gestures be replaced with untimed actions?

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.