Provide sufficient touch target size
SkillDev toolsTouch-targets is a skill for AI agents that reviews touchscreen interfaces for tap usability. It checks that buttons, links, checkboxes, radio buttons, form inputs, icon buttons, and menu items are big enough to press easily, by inspecting CSS for min-width, min-height, width, height, and padding on interactive elements.
Use Provide sufficient touch target size in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Provide sufficient touch target size and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Provide sufficient touch target size skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
No other account needed.
Have an AI agent that can load skills.
What your AI can do with it
- Checks CSS sizing properties (min-width, min-height, width, height, padding)
- Applies to buttons, links, checkboxes, radio buttons, form inputs, and menu items
- Flags undersized icon-only buttons such as close controls
- Reviews all interactive elements on touchscreen interfaces
Getting started
- Have an AI agent that can load skills.
- Add the touch-targets skill to the agent's available skills.
- Ask the agent to review a page or component for touch target sizes.
- Apply the agent's findings to the CSS of the interactive elements it flags.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/touch-targets/SKILL.md and read by ahel’s review.
Motor disabilities such as essential tremor, Parkinson's disease, hemiplegia, and spasticity make it difficult to tap small targets with precision. A 24×24px icon button with no padding requires a fine-motor action that many users simply cannot perform. Insufficient tap target size is one of the most common barriers for users with mobility impairments on mobile and tablet devices. Even users without disabilities benefit from larger targets, reducing accidental activations.
Quick Reference
- WCAG 2.2 SC 2.5.5 (AAA): touch targets must be at least 44×44 CSS pixels
- WCAG 2.2 SC 2.5.8 (AA, new in WCAG 2.2): targets must be at least 24×24 CSS pixels OR have 24px of spacing from other targets
- Apple HIG recommends 44×44 pt minimum; Google Material Design recommends 48×48 dp minimum
- Use
paddingto enlarge the interactive area without changing the visual size - Inline text links are exempt from SC 2.5.8
Check
Find all interactive elements: <button>, <a>, <input>, <select>, <textarea>, and elements with click/touch event handlers or role='button'. For each, compute the rendered bounding box size (including padding). Flag elements whose width or height is less than 24px (WCAG 2.2 AA threshold) or less than 44px (AAA / platform guidelines). Also check spacing: elements smaller than 44px should have at least 24px of clear space from adjacent interactive elements.
Fix
To increase touch target size without changing visual appearance: (1) Add padding to the element — e.g., padding: 12px on a button adds 12px to each side of the visual content. (2) Use min-width and min-height to enforce a floor: min-width: 44px; min-height: 44px. (3) For icon-only buttons, use a transparent pseudo-element to extend the hit area: .icon-btn::before { content: ''; position: absolute; inset: -12px; } with position: relative on the button. (4) Ensure adequate spacing between small targets so users do not accidentally activate the wrong element.
Explain
WCAG 2.2 introduced SC 2.5.8 (Target Size, Minimum) at Level AA, requiring touch targets to be at least 24×24 CSS pixels or have 24px of offset spacing from neighboring targets. The older SC 2.5.5 (Target Size) at Level AAA recommends 44×44px. These thresholds are based on average human fingertip size (approximately 10mm) and the precision required for touchscreen interaction. Users with tremors or limited dexterity need larger targets because their touch point can deviate by 20–30px from where they intend. The 44px recommendation aligns with Apple's Human Interface Guidelines and Google's Material Design system.
Code Review
Review the rendered markup and interactive states that affect Provide sufficient touch target size. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/touch-targets
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Oct 2026
Questions
- What elements does it check?
- All interactive elements on touchscreen interfaces: buttons, links, checkboxes, radio buttons, form inputs, icon buttons, and menu items.
- What does it look at in the code?
- It checks CSS for min-width, min-height, width, height, and padding on interactive elements.
- Why does it call out icon-only buttons?
- Icon-only buttons, such as close controls, are particularly important to check because they have no text label to enlarge their tappable area.
Advanced
- Item type
- skill
- Key
touch-targets- Source
- github.com/thedaviddias/front-end-checklist
github.com/thedaviddias/front-end-checklist
Related picks
Skill · alecs5am
The pick for Cssreset-css
Skill · thedaviddias
The pick for Cssapple-hig-expert
Skill · alirezarezvani
The pick for iOS (HIG)Audit Apple-platform UI work against Human Interface Guidelines with HIG Doctor
Skill · agentskillexchange
The pick for iOS (HIG)material
Skill · bergside
The pick for Materialmaterial-design-3-ui
Skill · skydashnet
The pick for Material