liveBook · Manning

Target size (minimum)

As explained in Architecting Accessibility

A WCAG 2.2 Level AA success criterion specifying minimum pointer-target dimensions and permitted exceptions.

A small control can be hard to select when a finger covers several options, a mouse pointer is unsteady, or an eye tracker cannot pinpoint a tiny area. Crowded targets raise the chance of selecting the wrong action. Make controls forgiving rather than requiring pixel-perfect pointing. section 5.5.1 section 5.6

WCAG 2.2 Level AA Success Criterion 2.5.8 requires most pointer targets to be at least 24 × 24 CSS pixels. Measure the area that actually responds to a click, tap, or eye-tracker dwell—not just the visible icon or text. A small icon can sit inside a larger target. Level AAA’s Target Size (Enhanced) criterion sets a 44 × 44 CSS-pixel threshold, with exceptions. section 5.5.1 section 5.5.2

A target smaller than the Level AA minimum may still qualify in limited circumstances:

  • It has sufficient clearance from nearby targets, assessed using a 24 CSS-pixel-diameter circle centered on the target. section 5.5.1
  • An equivalent target elsewhere provides the action with the necessary spacing. section 5.5.1
  • It is inline with text, browser-defined, or essential at that size. Inline links, for example, cannot reliably be enlarged without affecting surrounding text across screens. section 5.5.1

Make pagination easier to select

Imagine trying to choose a page number when a fingertip covers several tightly packed links. Give each link a larger clickable area and separate neighboring links; the visible numeral need not fill the whole target. The illustrated CSS uses a 50-pixel minimum width and height for links and an 8-pixel gap between them. Prioritize this care for frequently used controls and actions that are difficult to undo; keep a consequential action such as “Confirm deletion” away from unrelated controls. section 5.5.2 section 5.5.1

.pagination ul { #A
  gap: 8px; #B
  display: flex;
  flex-wrap: wrap;
  list-style: none;
  margin: 0;
  padding: 0;
  align-items: center;
}

.pagination a { #C
  min-width: 50px; #D
  min-height: 50px; #E
  padding-inline: 1rem; #F
  padding-block: 0.625rem; #G
  font-size: 1rem; #H
  line-height: 1.2;
  border: 1px solid var(--control-border);
  border-radius: 0.375rem;
  text-decoration: none;
  font-weight: 700;
  display: inline-flex;
  align-items: center;
  justify-content: center;
}

The pagination CSS enlarges the clickable links with minimum dimensions and padding, while a flex-container gap separates them. Check the resulting target areas, not merely the appearance of the numbers. section 5.5.2

TIP: Treat 24 × 24 CSS pixels as a minimum, not a design goal. Where space permits, larger, well-separated targets make selection easier and give people more confidence across pointing methods. section 5.5.2

How Architecting Accessibility covers it

How deep it goes
Defines the Level AA threshold and exceptions, then works through target-area measurement, spacing questions, and a pagination CSS refactoring.
Examples
Contrasts crowded pagination links with links enlarged and spaced using CSS, and considers a consequential confirmation action beside an unrelated control.
What you can do after
Apply it via CSS to enlarge clickable areas and separate neighboring controls, while checking whether smaller targets meet a permitted exception.
How it connects
Connects pointer targets with eye tracking, touch interaction, error prevention, pagination, and WCAG 2.2 Level AAA Target Size (Enhanced).

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.