December 5, 2023 · reala11y team

WCAG 2.2 Target Size (Minimum): the 24px rule for WordPress

WCAG 2.2's new Target Size (Minimum) criterion asks for 24x24 CSS pixel tap targets. Here's what 2.5.8 means for WordPress sites, with its spacing exception.

When WCAG 2.2 became a W3C Recommendation on 5 October 2023, it added nine new success criteria to the 2.1 set published back in 2018. One of them quietly affects nearly every WordPress theme on the web: Success Criterion 2.5.8, Target Size (Minimum). It is a Level AA criterion, which means it sits inside the conformance bar most legal and procurement frameworks point at.

If you have small social icons in your footer, a dense pagination row, or “edit” and “delete” links jammed together in a table, this one is worth ten minutes of your attention.

What 2.5.8 actually requires

The rule is short: the target for a pointer interaction must be at least 24 by 24 CSS pixels — unless an exception applies. A “target” is the clickable or tappable region of a control: a button, a link, a checkbox, a menu item.

Note the unit. CSS pixels, not device pixels. A 24px target stays 24px whether the visitor is on a 4K monitor or a phone with a 3x display. You are sizing the interactive region, not the icon glyph inside it — padding counts.

Why 24 and not something larger? The criterion is a floor, not a goal. People with hand tremors, limited dexterity, or who are tapping on a moving train all benefit from larger targets. The related Level AAA criterion (2.5.5) asks for 44px. 2.5.8 picks 24px as the minimum that meaningfully reduces mis-taps without forcing a redesign of every dense interface.

The exceptions (this is where it gets practical)

You do not have to inflate every link on the page. 2.5.8 has five exceptions, and the first is the one you will lean on most.

• Spacing. A target under 24px passes if a 24px-diameter circle centered on it does not overlap the circle of any adjacent target. In plain terms: small icons are fine if they have enough breathing room around them. This is the practical escape hatch for icon rows.
• Equivalent control. Another control on the same page does the same thing and does meet 24px.
• Inline. Links inside a sentence or block of text are exempt — you are not expected to break your prose to space out an inline link.
• User-agent default. If the browser sets the size and you have not changed it, it is not your failure.
• Essential. The exact size is legally required or genuinely essential to the function (think a precise map pin).

So the common footer row of 16px social icons is not automatically a failure. Tighten the spacing test and you often pass with either more padding or more gap. Either lever works.

Where WordPress sites trip up

A few recurring offenders, in order of how often we see them:

• Footer social icons rendered at their natural glyph size with no padding and 4px between them.
• Pagination — “1 2 3 Next” with tap targets the height of the text line only.
• Table action links — Edit | Delete separated by a thin pipe, each well under 24px tall.
• Tag clouds and inline meta — though many of these qualify for the inline exception.
• Custom icon buttons styled with <a> wrapping an SVG and zero padding.

The fix is almost always CSS, not markup. For a button-like link:

.icon-link {
  display: inline-flex;
  min-width: 24px;
  min-height: 24px;
  align-items: center;
  justify-content: center;
}

For a row of small targets that you would rather keep small, add gap so the spacing exception applies:

.social-row { display: flex; gap: 12px; }

Because the fix lives in the stylesheet, it is exactly the kind of thing a code-level tool can help with — and exactly the kind of thing an overlay widget cannot, because an overlay paints on top of the page without changing the CSS your visitors actually receive. reala11y works at the source: it flags small targets against 2.5.8 and can apply minimum-size padding to theme output, so the rendered HTML and CSS — what screen readers, crawlers, and your real visitors see — is the thing that changed.

Why it matters beyond the spec

The regulatory backdrop has tightened. The US DOJ’s April 2024 ADA Title II rule named WCAG 2.1 AA for state and local government sites, and the European Accessibility Act became enforceable on 28 June 2025. None of that turns 2.5.8 into a checkbox you can buy your way past — and the FTC’s $1,000,000 final order against accessiBe on 21 April 2025 is a reminder of what happens when a vendor pretends otherwise.

The honest takeaway

Target Size is one of the more automatable criteria in WCAG 2.2: a scanner can measure rendered dimensions and a stylesheet can correct them. But “automatable” is not “solved for you.” Automated tooling, ours included, surfaces a portion of WCAG issues — and the spacing exception in particular often needs a human to confirm that a layout still reads the way you intended. Fix the obvious 24px gaps with confidence, then put the edge cases in front of a person. That pairing is the point.