Skip to main content
Accessibility.com, LLC
Category: Mobile Accessibility

Target Size (Minimum)

Also known as: WCAG 2.5.8, Success Criterion 2.5.8, SC 2.5.8
Simply put

Target Size (Minimum) is a WCAG guideline that asks the clickable or tappable areas of a web page, such as buttons and links, to be large enough for people to activate without accidentally hitting the wrong thing. Under this criterion, these targets should generally be at least 24 by 24 CSS pixels, though several exceptions apply, including when adequate spacing is provided around smaller targets. Meeting this guideline helps users who have difficulty with precise pointer movements, such as those using touchscreens or with limited motor control.

Formal definition

Target Size (Minimum) is WCAG Success Criterion 2.5.8, a Level AA criterion introduced in WCAG 2.2. It requires that the size of the target for pointer inputs be at least 24 by 24 CSS pixels, subject to five documented exceptions, including a spacing exception (undersized targets that have sufficient surrounding spacing), an equivalent-control exception, an inline exception, a user-agent-controlled exception, and an essential exception. This criterion should be distinguished from SC 2.5.5 Target Size (Enhanced), a Level AAA criterion (present in WCAG 2.1 as SC 2.5.5 Target Size and carried into WCAG 2.2 as Target Size (Enhanced)) that specifies a larger minimum of 44 by 44 CSS pixels. As with all WCAG criteria, conformance does not by itself guarantee an accessible experience or legal compliance; manual and assistive-technology testing remain necessary, and this entry is not legal advice.

Why it matters

Small, tightly packed interactive targets are a common source of frustration and error for people who cannot make precise pointer movements. Users with tremors, limited fine motor control, or conditions affecting hand steadiness may repeatedly miss a small button or accidentally activate an adjacent link. Touchscreen users, operating with a fingertip rather than a precise cursor, face similar difficulties, as do people using a head pointer, eye-tracking, or other alternative input methods. When targets are too small or crowded, these users may be unable to complete essential tasks like submitting a form, navigating a menu, or confirming a purchase.

Target Size (Minimum), added as a Level AA success criterion in WCAG 2.2, addresses this by asking that pointer targets generally measure at least 24 by 24 CSS pixels, or be surrounded by adequate spacing where they are smaller. Because AA is the level most commonly cited as a conformance target in accessibility work and in settlements referencing WCAG, this criterion is frequently relevant to organizations aiming to align with widely used benchmarks. Meeting it reduces accidental activation and lowers the physical and cognitive effort required to interact with a page.

As with any WCAG success criterion, meeting 2.5.8 does not by itself guarantee an accessible experience or immunity from legal claims, and automated tools detect only a portion of relevant issues. Manual review and testing with assistive technologies remain necessary to confirm that targets are genuinely usable in practice. This entry is informational and is not legal advice; requirements evolve through regulation and case law, and readers with legal questions should consult qualified counsel.

Who it's relevant to

UX and UI Designers
Designers make the layout decisions that determine whether targets meet the 24-by-24 CSS pixel guideline or qualify under the spacing and other exceptions. Accounting for target size and spacing early, especially for icon buttons, closely packed controls, and dense navigation, helps avoid rework and improves usability for people using touchscreens or alternative pointing methods.
Front-End Developers
Developers translate designs into the actual interactive regions users click or tap, so the measurable clickable area, not just the visible graphic, must satisfy the criterion or a documented exception. They also need to understand which situations fall under the inline, equivalent-control, user-agent-controlled, or essential exceptions when implementing components.
Accessibility Engineers and QA Testers
Because automated tooling detects only a portion of target-size issues, testers should verify sizing and spacing manually and confirm that controls can be reliably activated with different pointer inputs. Understanding the distinction between SC 2.5.8 (Level AA, 24 pixels) and SC 2.5.5 Target Size (Enhanced) (Level AAA, 44 pixels) is important for reporting conformance accurately against a stated target level.
Compliance Officers and Business Leaders
Since AA conformance is the level most commonly cited as a target in accessibility programs and in settlements that reference WCAG, teams pursuing WCAG 2.2 AA alignment will encounter this newer criterion. Leaders should treat conformance as one input among several, recognizing that meeting a criterion does not by itself guarantee legal compliance and that qualified legal counsel should advise on obligations, which evolve through regulation and case law.

Inside Target Size (Minimum)

Success Criterion 2.5.8 (Target Size (Minimum))
A WCAG 2.2 Level AA success criterion added in the WCAG 2.2 release. It addresses the minimum size of pointer targets so that they can be activated more reliably, particularly by users with limited dexterity or motor impairments.
Minimum target dimension
The criterion generally establishes a minimum size for interactive targets, commonly cited as 24 by 24 CSS pixels, unless one of the defined exceptions applies.
Spacing exception
Targets smaller than the minimum may still conform when sufficient spacing separates them from adjacent targets, so that an undersized offset circle of the specified diameter would not overlap neighboring targets or their spacing.
Inline exception
Targets within a sentence or block of text, where the target sizing is constrained by the flow of the text, are generally exempted.
User-agent and essential exceptions
Targets whose size is determined by the user agent and not modified by the author, or where a particular presentation of the target is essential or legally required, are typically excluded from the requirement.
Relationship to 2.5.5 (Target Size (Enhanced))
Distinct from the Level AAA criterion 2.5.5, which is often cited at a larger 44 by 44 CSS pixel threshold. 2.5.8 sets a lower, Level AA baseline and should not be conflated with the AAA criterion.

Common questions

Answers to the questions practitioners most commonly ask about Target Size (Minimum).

Does meeting the Target Size (Minimum) criterion require every interactive element to be at least 24 by 24 CSS pixels with no exceptions?
No. The Success Criterion 2.5.8 Target Size (Minimum), added in WCAG 2.2 at Level AA, sets 24 by 24 CSS pixels as a baseline, but it includes several exceptions. These commonly include targets that have sufficient spacing from adjacent targets, targets where an equivalent alternative control meeting the size is available on the same page, targets whose position is determined by the user agent and not modified by the author, targets that are part of a sentence or block of text (inline targets), and cases where the presentation is essential or legally required. Because of these exceptions, a small target may still conform when spacing or an alternative is provided, so evaluating conformance requires checking the specific exception conditions rather than applying a flat 24-pixel rule to every element.
Is Target Size (Minimum) the same as the larger 44 by 44 pixel requirement people sometimes reference?
No. Those are distinct criteria at different conformance levels. Target Size (Minimum), Success Criterion 2.5.8, is a Level AA criterion added in WCAG 2.2 and uses a 24 by 24 CSS pixel baseline. The larger 44 by 44 CSS pixel figure corresponds to Target Size (Enhanced), Success Criterion 2.5.5, which is a Level AAA criterion introduced in WCAG 2.1. Because AA is the level most commonly cited as a conformance target, teams often work to the 24-pixel minimum, while the 44-pixel figure applies to the more stringent AAA level and is generally treated as an enhanced goal rather than a common baseline.
How is the 24 by 24 CSS pixel target size measured for an interactive element?
The measurement generally refers to the size of the target area a user can activate, expressed in CSS pixels, which are a reference unit rather than physical device pixels. The relevant area includes the actionable region of the control, which may extend beyond the visible graphic if the clickable or tappable area is larger. When evaluating conformance, assess whether the effective target area meets or exceeds 24 by 24 CSS pixels, or whether one of the criterion's exceptions applies, such as adequate spacing between adjacent targets.
What can we do when a design constraint prevents a target from reaching 24 by 24 CSS pixels?
The criterion's exceptions provide practical paths to conformance. Options commonly used include increasing the spacing around the small target so that a 24-pixel-diameter circle centered on it does not intersect neighboring targets, providing an equivalent control that meets the size elsewhere on the page, or relying on user-agent-determined positioning that the author does not modify. Inline targets within a sentence or block of text are also excepted. Which approach fits depends on the specific interface, so the appropriate exception should be identified and documented during evaluation.
Does spacing between small targets help satisfy Target Size (Minimum)?
Yes, spacing is one of the recognized exceptions. Where individual targets are smaller than 24 by 24 CSS pixels, the criterion can still be met if the targets are separated enough that surrounding spacing effectively provides the required area, generally described in terms of whether a 24-pixel region centered on each target overlaps with adjacent targets. This makes spacing a useful strategy for dense controls such as toolbars or closely grouped links, provided the spacing conditions in the criterion are met.
Can automated testing confirm that an interface passes Target Size (Minimum)?
Automated tools may help flag some potential target size issues, such as elements with small dimensions, but they detect only a portion of what the criterion requires. Assessing the exceptions, the effective activation area, spacing relationships, and whether an alternative control is genuinely equivalent generally requires manual review and testing with assistive technologies and real interaction. Automated results should therefore be treated as a starting point rather than a complete determination of conformance, and this guidance is not legal advice.

Common misconceptions

Target Size (Minimum) has always been part of WCAG at Level AA.
Success Criterion 2.5.8 was introduced in WCAG 2.2 and is not present in WCAG 2.0 or 2.1. Organizations targeting earlier versions would not have this specific Level AA requirement, though the related 2.5.5 (Enhanced) at Level AAA existed in WCAG 2.1.
Every interactive element must physically measure at least 24 by 24 pixels to conform.
The criterion includes defined exceptions, including adequate spacing around smaller targets, inline targets within text, user-agent-controlled sizing, and cases where a specific size is essential. A target can conform without meeting the minimum dimension if a documented exception applies.
Meeting 2.5.8 makes controls fully usable for everyone.
Conformance with a success criterion is not the same as guaranteed usability. Meeting the minimum threshold may still leave targets difficult to use for some individuals, and manual evaluation with real users and assistive technologies remains important.

Best practices

Confirm which WCAG version applies to your project, since 2.5.8 is specific to WCAG 2.2; if you are conforming to 2.0 or 2.1 this Level AA criterion does not apply.
Aim for the commonly cited 24 by 24 CSS pixel minimum for pointer targets, and treat the larger 44 by 44 pixel figure from 2.5.5 as an enhanced goal where feasible.
Where targets must remain small, provide adequate spacing so that neighboring targets are not accidentally activated, applying the spacing exception intentionally rather than by accident.
Document which exception you are relying on (spacing, inline, user-agent, or essential) so that conformance decisions are defensible and reviewable.
Validate target sizing through manual testing and testing with people who have motor impairments, since automated tools detect only a portion of relevant issues.
Because requirements evolve through regulation and case law and vary by jurisdiction, treat conformance as one input and consult qualified legal counsel for compliance decisions rather than relying on a single criterion.