Home: Mohammad Abu-aishehOpen to work Open to work العربية

Accessibility // Guide

Touch target size

Small buttons are hard to hit. Learn the WCAG 2.2 minimum of 24 by 24 CSS pixels, the larger 44 px guidance and how spacing helps.

Touch target size

Why size matters

A target is anything a user can tap or click. Small or crowded targets cause mis-taps, especially for people with tremors, limited dexterity or large fingers, and for anyone using a phone with one hand.

Fitts’s law explains the effect: the time to reach a target grows with distance and shrinks as the target gets larger.

The numbers

  • 24 × 24 CSS px

    WCAG 2.2 SC 2.5.8 Target Size (Minimum), level AA.

  • 44 × 44 CSS px

    WCAG SC 2.5.5 Target Size (Enhanced), level AAA.

  • 44 pt

    Apple’s Human Interface Guidelines recommend a minimum control size of 44 by 44 points.

  • 48 dp

    Material Design recommends touch targets of at least 48 by 48 dp.

Spacing and exceptions

WCAG 2.5.8 has a spacing exception: a target smaller than 24 px passes if a 24 px circle centred on it does not overlap another target or the circle of a neighbour. So tiny icons can pass when they are well separated.

  • Inline links inside a sentence are exempt, because their size is set by the text.
  • Targets whose size is controlled by the browser, such as default checkboxes, are exempt.
  • An equivalent larger control on the same page can also satisfy the rule.

Applying it

  1. Design the hit area, not only the visible shape. A 16 px icon can sit inside a 44 px button.
  2. In CSS, add padding to icon buttons, for example <code>padding: 12px</code> around a 20 px icon.
  3. Leave gaps between neighbouring controls, such as rows of action icons.
  4. Place frequent actions within easy thumb reach, usually the lower part of a phone screen.

Treat 24 px as the floor and 44 to 48 px as the comfortable target for primary controls.

Most target-size failures come from icons and compact controls, not from main buttons.

  • Close buttons, menu dots and pagination links drawn at the size of their icon.
  • Rows of small icon actions in tables with no gap between them.
  • Tiny checkboxes and radio buttons where only the box, not the label, is clickable.
  • Dense toolbars copied from desktop layouts onto touch screens.

Make the label part of the click area so a larger target comes for free.

Sources

  • W3C. Understanding SC 2.5.8 Target Size (Minimum). https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html
  • W3C. Understanding SC 2.5.5 Target Size (Enhanced). https://www.w3.org/WAI/WCAG22/Understanding/target-size-enhanced.html

This guide was drafted with AI assistance from public standards and references. For the exact wording of a standard, use the sources listed above.

More on this topic

  • Accessibility2 min read

    Designing for reduced motion

    Animation can cause discomfort or nausea for some users. Learn to respect prefers-reduced-motion and to give people control over moving content.

  • Accessibility2 min read

    Headings and landmarks

    Screen reader users navigate by headings and landmarks. Structure pages with one h1, ordered headings and clear regions.

  • Accessibility2 min read

    Not by colour alone

    Colour should never be the only way to convey meaning. Learn WCAG 1.4.1 and how to pair colour with text, icons and patterns.

Keyboard shortcuts
Single-key shortcuts

Turn off if you use speech input or find them getting in the way.