Skip to content
UX Atlas
AccessibilityCraft conventionFoundational

Target Size

Interactive targets need to be large enough and spaced enough to hit reliably.

Definition

WCAG 2.2 introduced 2.5.8 Target Size (Minimum) at level AA, requiring targets of at least 24 by 24 CSS pixels, with exceptions where sufficient spacing exists. The earlier AAA criterion 2.5.5 sets 44 by 44.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this page
  1. Definition
  2. Practical rules
  3. Sources
  4. Continue from here

Practical rules

  • Design to 44 by 44 for touch, even though AA requires 24. Platform guidance from Apple and Google both sit at or above that.
  • The hit area is what counts, not the visible icon. Expand it with padding or a pseudo-element.
  • Spacing can substitute for size under 2.5.8, so a smaller target with a clear gap can conform.
  • Include the label in the target for checkboxes, radios and list rows.
  • Keep destructive targets away from frequently used ones.
  • Inline links in prose are exempt, since enlarging them would disrupt the text.

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

A CheckoutA Data TableA FormA Mobile AppAn Ecommerce ExperienceAn Enterprise Workflow

Why this works

The reasoning this entry rests on.

  • Fitts's LawLaw

    The WCAG minimum is the accessibility floor under an effect that is really about distance and size together.

Relied on by

Entries that assume this is already in place.

Practical example

A worked decision where this was the deciding factor.

Check your work

Review passes that test whether this was done properly.

Related concept

Connected closely enough to change how you apply this.