How accessible is your website?Start free check
WCAG 2.5.8Level AAOperable

Target Size: 24 × 24 px for Every Click Target

Also called: Target Size (Minimum), Touch target size, Tap target, Click target size

Definition

Target Size (Minimum) is WCAG success criterion 2.5.8. The size of the target for pointer inputs is at least 24 by 24 CSS pixels, unless spacing, an equivalent control, inline text, the user agent or an essential presentation makes an exception.

Target size is the area someone has to hit with a mouse, finger or stylus to activate a link or button. WCAG 2.2 sets a minimum of 24 by 24 CSS pixels so that people do not trigger the wrong control by accident. Tiny close icons, crowded social buttons and pagination numbers squeezed together are the usual problems.

What it means

WCAG 2.5.8 Target Size (Minimum) is a Level AA criterion, new in WCAG 2.2. The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except when:

Exception Meaning
Spacing An undersized target passes if a 24 CSS pixel diameter circle centered on it does not intersect another target or the circle of another undersized target
Equivalent The same function is available through another control on the page that meets the size
Inline The target sits in a sentence, or its size is limited by the line height of the text around it
User agent control The browser sets the size and the author did not change it (e.g. a default checkbox)
Essential A particular presentation is essential or legally required

Sliders and color pickers that set a value by position count as one target. W3C names who benefits: people with hand tremors or limited fine motor control, people using a mouse, stylus or touch on the move (for example on public transit), one-handed users and people with large fingers. Even when spacing lets a small target pass, W3C recommends meeting the minimum size as a best practice; Level AAA criterion 2.5.5 Target Size (Enhanced) is stricter still.

Small targets often come with other problems: an icon button without a name, or a link so small that its focus visible outline is hard to spot.

Examples

Example
<!-- Bad: 16 px icon, the clickable area is only the icon -->
<button class="close"><svg width="16" height="16" aria-hidden="true">…</svg></button>

<style>
  /* Good: keep the icon small, make the target bigger (W3C technique C42) */
  .close {
    min-width: 24px;
    min-height: 24px;
    display: inline-grid;
    place-items: center;
    padding: 4px;
  }
  /* Good: spacing between small pagination links */
  .pagination a { display: inline-block; min-width: 24px; min-height: 24px; }
  .pagination li + li { margin-left: 8px; }
</style>
Do

Use min-width and min-height on buttons and links, give icon buttons padding, leave space between neighboring controls, and make whole cards or rows clickable where it makes sense.

Don't

Shrink close, cart or social icons to 12–16 px without padding, cram page numbers side by side, or place tiny checkboxes you have restyled right next to each other.

How to check target size

    Questions

    What is the minimum target size in WCAG 2.2?

    24 by 24 CSS pixels for Level AA (2.5.8). A smaller target can still pass if a 24 pixel circle around it does not intersect another target or another small target's circle, or if another exception applies.

    Do links in text need to be 24 × 24 pixels?

    No. Targets in a sentence, or whose size is limited by the line height of the surrounding text, fall under the inline exception.

    What is the difference between target size 2.5.8 and 2.5.5?

    2.5.8 Target Size (Minimum) is Level AA and sets the 24 pixel minimum with five exceptions. 2.5.5 Target Size (Enhanced) is Level AAA and asks for larger targets; W3C suggests aiming for it on important links and controls.

    Does the icon have to be 24 pixels?

    No, the target does. A 16 px icon inside a button with padding is fine as long as the clickable area is at least 24 × 24 CSS pixels or the spacing exception applies.

    • Dragging Movements: Offer a Click Alternative

      Dragging Movements is WCAG success criterion 2.5.7. All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the browser provides it.

      Read definition: Dragging Movements: Offer a Click Alternative
    • Icon Button: How to Give It an Accessible Name

      An icon button is a button that shows only a symbol – a magnifier, a cross, three lines – and no visible text. To be accessible it needs an accessible name in code that tells assistive technology what the button does.

      Read definition: Icon Button: How to Give It an Accessible Name
    • Focus Visible: WCAG 2.4.7 and Visible Focus Styles

      Focus visible means that a website shows a visible indicator – usually an outline – on the link, button or field that currently has keyboard focus. WCAG 2.4.7 requires it at Level AA.

      Read definition: Focus Visible: WCAG 2.4.7 and Visible Focus Styles
    • Reflow: Content That Fits at 400% Zoom

      Reflow is WCAG success criterion 1.4.10. Content must work without loss of information or functionality and without scrolling in two directions at a width equal to 320 CSS pixels – or a height of 256 CSS pixels for horizontally scrolling content.

      Read definition: Reflow: Content That Fits at 400% Zoom

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done