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

Touch Target Design

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

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

About

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

  • touch-target-design
  • AI & Agent Building
  • AI-coding skill

Touch Target Design by the numbers

  • 34 all-time installs (skills.sh)
  • +5 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #8,855 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 touch-target-design

Add your badge

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

Listed on Skillselion
Installs34
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 ↗

Touch Target Design

Design interactive elements that are large enough, spaced enough, and forgiving enough for people with limited precision — whether from disability, age, environment, or device.

Minimum Sizes

Touch (mobile, tablet)

  • Minimum: 44×44 CSS pixels (WCAG 2.2 Level AA)
  • Recommended: 48×48 CSS pixels (Google Material guidelines)
  • For high-stakes or frequent-use targets: 56×56 or larger

Pointer (desktop)

  • Minimum: 24×24 CSS pixels (WCAG 2.2 Level AA)
  • Recommended: 32×32 for common actions
  • For destructive or irreversible actions: larger targets reduce errors

Spacing Between Targets

  • Minimum: 8px gap between adjacent interactive elements
  • Recommended: 12–16px for frequently used elements side by side
  • Never place destructive actions (delete) adjacent to common actions

(save) without spacing or visual separation

Design Patterns

Generous Hit Areas

  • The tappable area can be larger than the visible element
  • Use padding, not just the visual size of the icon or text
  • Entire row should be tappable in list items, not just the text
  • Link text should be descriptive enough to form a reasonable

tap target ("Read the full report" not "here")

Forgiving Interactions

  • Don't trigger actions on touch-down — trigger on touch-up

(this lets users slide away to cancel)

  • For destructive actions: require a deliberate second tap or

confirmation, not a single tap

  • Avoid double-tap requirements — they're unreliable for users

with tremors

  • Avoid long-press as the only way to access functionality

Spacing for Safety

  • Separate "confirm" and "cancel" actions with distance or visual weight
  • Place destructive actions away from common actions
  • Group related actions together, separate unrelated actions
  • On mobile: keep primary actions in the thumb zone (bottom half

of screen)

Alternatives to Precision

  • Provide zoom capability for complex interfaces
  • Allow pinch-to-zoom on mobile (never disable it)
  • For precise tasks (colour pickers, sliders): provide a text

input alternative

  • Dropdown menus with many items: add search/filter

Assessment Questions

1. Are all interactive elements at least 44×44px on touch devices? 2. Is there adequate spacing between adjacent targets? 3. Are destructive actions separated from common actions? 4. Can every interaction be completed without precision timing or precise pointing? 5. Is there always an alternative to precision-dependent interactions like sliders or drag-and-drop?

Related skills

This week in AI coding

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

unsubscribe anytime.