2.5.5 Target Size (Enhanced)

1. What is the goal of this criterion?

Imagine trying to hit a tiny “Buy” button on a bumpy train – while your thumb is shaking. Frustrating? For people with motor disabilities, tremors or simply larger fingers, that’s everyday life.

The goal of WCAG Success Criterion 2.5.5 is clear: controls should be large enough to be activated safely and accurately. Specifically, buttons, links and other pointer targets need a minimum size of 44 by 44 CSS pixels.

2. What exactly does it require?

This criterion covers all targets activated with a pointer (mouse, finger, stylus):

The basic rule: every target is at least 44 by 44 CSS pixels.

Exceptions only apply to:

• Equivalent targets: the same function is available on the same page through another link or control that is at least 44 by 44 CSS pixels.
• Inline targets: links within a sentence or block of text are exempt.
• User agent control: the size is determined by the browser and not modified by you.
• Essential presentation: a particular presentation of the target is essential to the information being conveyed.

Key difference from Target Size (Minimum): the AA version only requires 24 by 24 CSS pixels and allows smaller targets if there’s enough spacing. 2.5.5 has no such spacing rule – the target itself must be 44 by 44 pixels.

3. Why does it matter for accessibility?

Imagine shopping online while your hands shake slightly – or using your phone with gloves in winter. Tiny buttons quickly become a real obstacle.

Large targets improve accessibility because they:

• let people with motor disabilities hit elements reliably
• help people with tremors or limited fine motor control avoid mis-clicks
• support people who tap with large fingers, a knuckle or a stylus
• give people with low vision bigger, easier-to-see targets
• help everyone in unsteady environments, like on a bus or train, or while walking
• make one-handed use easier

And finally: large targets make interfaces more comfortable for everyone – especially on touch devices, where a finger is far less precise than a mouse pointer.

4. How to meet the criterion

The good news: 44 by 44 pixels is usually easy to implement. Here are some proven tips:

Ground rules for large enough targets:

• Use min-width: 44px and min-height: 44px on interactive elements.
• Enlarge the clickable area with padding – it counts toward the target, while margin does not.
• For icons, make the surrounding button bigger, not just the icon.
• Test on real devices, especially phones and tablets.

Especially important for:

• frequently used elements like navigation and primary actions
• consequential actions such as delete or buy
• elements at the edge of the screen or in hard-to-reach areas
• multi-step flows like forms

A typical implementation:

.button {
  min-width: 44px;
  min-height: 44px;
  padding: 12px 16px;
}

.icon-button {
  width: 44px;
  height: 44px;
  /* the icon is centered, the button has the right size */
}

Using the exceptions correctly:

• Links in running text are exempt – a list of links below the text or a menu is not.
• If the same function is also available as a large element on the page, that’s enough.
• Unmodified browser default controls, such as native checkboxes without custom styling, are exempt.
• Map markers whose exact position is the information may fall under the essential exception.

5. Why this criterion matters for businesses

2.5.5 is a Level AAA criterion and not legally required under the European Accessibility Act or its German implementation, the BFSG – the underlying standard EN 301 549 requires WCAG 2.1 Level AA. Still, 44 by 44 pixels is a widely used guideline for touch targets and a good default for your design system.

1. Fewer mis-clicks, more completed tasks

Buttons that are too small lead to mis-clicks and drop-offs. Larger controls mean less frustration and more successfully completed tasks – especially in mobile e-commerce.

2. Comfortable on mobile

A large share of use happens on phones. Generous touch targets make your website comfortable to use there.

3. A safety margin for required criteria

If you make 44 by 44 pixels your default, you meet the AA requirement of 24 by 24 pixels from WCAG 2.2 with room to spare – even if an element turns out a little smaller in practice.

This section is general information, not legal advice.

6. The success criterion in the W3C’s words

Success Criterion 2.5.5 Target Size (Enhanced) (Level AAA)

The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when:

• Equivalent: The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;
• Inline: The target is in a sentence or block of text;
• User Agent Control: The size of the target is determined by the user agent and is not modified by the author;
• Essential: A particular presentation of the target is essential to the information being conveyed.

In short: pointer targets must be at least 44 by 44 CSS pixels – unless there’s a large equivalent, the target is inline in text, the browser controls its size or the presentation is essential.