Skip to main content :::
:::

What Is Target Size?

Target size concerns whether buttons, links, and interactive controls have enough operable area so people can activate them without missed taps or accidental activation. WCAG 2.2 adds a success criterion for minimum target size.


Key Takeaways

  • Target size is not only the visible icon size; it is the actual clickable or touchable area.
  • Small or crowded targets increase accidental activation for people with motor needs, zoom users, and mobile users.
  • Design and engineering should check operable areas for buttons, links, form controls, and icon buttons together.

Why target size affects accessibility

Small controls are not merely inconvenient. For people with tremors, limited fine motor control, touch-screen use, zoom, or on-the-go contexts, small targets can cause task failure.

Common issues include icon buttons with tiny hit areas, adjacent links placed too close together, hard-to-select form controls, and mobile lists with insufficient interactive area.

Do not check only the icon

An icon in the design may be 16 or 20px, but the real button can provide a larger operable area through padding. Conversely, something that looks like a large button may only make the text itself clickable.

Check DOM, CSS, hit area, spacing, and focus appearance, not just the visible size.

How UI Kit and DevCheck relate

UI Kit helps standardize basic sizing, state, and keyboard behavior for common controls, reducing repeated defects across projects.

DevCheck helps page reviewers inspect the current page and decide whether target size, focus, and interaction states need manual review.

Frequently Asked Questions

Is visual size enough?

Not necessarily. Check the actual operable area, spacing from nearby controls, and behavior across input methods.

Does target size matter only on mobile?

No. Mouse, trackpad, touch, zoom, and motor use can all be affected by target size.

Related Pages

References