Category: Mobile Accessibility

Touch Target

Also known as: Target Size, Tap Target, Touch Target Size

Simply put

A touch target is the area on a screen that responds when a user taps or touches it, such as a button, link, or icon. When touch targets are too small or too close together, people can find them difficult to activate accurately, particularly those with limited dexterity or motor control. Providing adequately sized and spaced targets makes controls easier to select on touchscreens and other pointer-based devices.

Formal definition

A touch target is the interactive region of a control or link that receives pointer or touch input. WCAG addresses this through two success criteria: Success Criterion 2.5.5 Target Size (Level AAA), introduced in WCAG 2.1, which references a target size of at least 44 by 44 CSS pixels; and Success Criterion 2.5.8 Target Size (Minimum) (Level AA), introduced in WCAG 2.2, which sets a smaller minimum of 24 by 24 CSS pixels or requires sufficient spacing between smaller targets. Under these criteria, certain targets are exempted, for example links positioned within a sentence or block of running text. Target size is generally computed from the largest unobscured area of the target. Platform guidance may differ from WCAG values; for instance, Android accessibility guidance recommends a minimum touch target of 48 by 48 density-independent pixels (dp), corresponding to roughly 7-10mm physical size. In implementation terms, the element that receives a given touch is exposed programmatically (for example, via the Touch.target property in the DOM), and user agents commonly apply heuristics to associate a touch point with the nearest eligible control.

Why it matters

Touch targets determine whether people can reliably activate the controls that make up an interface. When buttons, links, or icons are too small or crowded together, users with limited dexterity, tremors, or reduced fine motor control may repeatedly miss the intended control or trigger the wrong one. These difficulties are not limited to permanent disabilities; situational factors such as using a device one-handed, in motion, or on a small screen can compound the problem for anyone.

Because of this, target size and spacing are addressed directly in WCAG. Success Criterion 2.5.5 Target Size (Level AAA) was introduced in WCAG 2.1 and references a size of at least 44 by 44 CSS pixels, while Success Criterion 2.5.8 Target Size (Minimum) (Level AA) was added in WCAG 2.2 and sets a smaller minimum of 24 by 24 CSS pixels or sufficient spacing between smaller targets. The AA-level criterion is commonly cited as a practical target for teams working toward broadly recognized conformance, though meeting a success criterion does not by itself guarantee an accessible experience for every user or immunity from legal claims.

Platform guidance may set different expectations than WCAG. Android accessibility guidance, for example, recommends a minimum touch target of 48 by 48 density-independent pixels, which corresponds to a physical size of roughly 7 to 10 millimeters. Designers and engineers generally need to reconcile WCAG success criteria with the platform conventions of the environments they ship to, and should verify behavior through manual and assistive technology testing rather than relying on automated checks alone. This entry is general guidance and not legal advice; requirements evolve through regulation and case law, and specific obligations may warrant consultation with qualified counsel.

Who it's relevant to

UX and Visual Designers

Designers make the layout decisions that determine target size and spacing. Understanding that WCAG 2.2 Success Criterion 2.5.8 sets a minimum of 24 by 24 CSS pixels (or sufficient spacing), that the AAA-level 2.5.5 references 44 by 44 CSS pixels, and that platform guidance such as Android's 48 by 48 dp recommendation may differ, helps them design controls that are easier to activate across devices.

Front-End and Mobile Developers

Engineers implement the actual hit areas, which may extend beyond the visible label or icon. Because size is computed from the largest unobscured area of the target and the element receiving a touch is exposed programmatically (for example via the Touch.target property), developers control whether the interactive region matches design intent and behaves consistently across user agents.

Accessibility and QA Testers

Automated tools can flag some target size issues, but they detect only a portion of problems. Testers generally need manual review and assistive technology testing to confirm that targets are usable in practice, including for people with limited dexterity, and to account for exemptions such as links within running text.

Compliance Officers and Legal Counsel

Those assessing conformance should note which criterion applies to their target level: 2.5.8 (Level AA, WCAG 2.2) versus 2.5.5 (Level AAA, WCAG 2.1). Meeting a success criterion supports conformance goals but does not guarantee legal safety, and specific obligations may depend on jurisdiction, regulation, and case law. This is not legal advice; consult qualified counsel where appropriate.

Inside Touch Target

Target Size (Minimum), WCAG 2.2 Success Criterion 2.5.8 (Level AA)

A success criterion added in WCAG 2.2 that generally requires the size of a pointer target to be at least 24 by 24 CSS pixels, unless an exception applies (such as spacing between targets, an equivalent control elsewhere, inline targets within a sentence, targets whose presentation is determined by the user agent, or where a particular presentation is essential). This is distinct from the enhanced criterion below and did not exist in WCAG 2.0 or 2.1.

Target Size (Enhanced), WCAG 2.1 Success Criterion 2.5.5 (Level AAA)

A Level AAA criterion introduced in WCAG 2.1 that generally calls for a target size of at least 44 by 44 CSS pixels, subject to exceptions. Because it is Level AAA, it is less commonly cited as a compliance target than the AA criterion, though it is often referenced as a usability best practice.

Target spacing and exceptions

Both criteria include exceptions where undersized targets may still conform, for example when sufficient spacing separates adjacent targets so they are not easily activated by mistake, when an equivalent accessible control of adequate size is available, or when the size is legally required or essential to the information being conveyed.

CSS pixels as the unit of measure

Target size is expressed in CSS pixels rather than physical device pixels, so measurements are consistent across displays of differing pixel density. Practitioners should evaluate against CSS pixel dimensions rather than assuming a fixed physical size.

Relationship to motor and dexterity needs

Adequately sized and spaced targets support users with limited fine motor control, hand tremors, or those operating devices in motion, as well as touchscreen users generally. The concept centers on reducing accidental activation and the effort required to acquire a control.

Common questions

Answers to the questions practitioners most commonly ask about Touch Target.

Does the ADA legally require a specific minimum touch target size?

No US statute, including the ADA, sets a codified pixel-based minimum for touch targets in web or mobile interfaces. Touch target size is addressed through WCAG success criteria published by the W3C, and courts or settlements have at times referenced WCAG as a benchmark rather than a fixed legal rule. Whether a particular target size is treated as an accessibility obligation depends on applicable regulation, agency guidance, and case law, so you should consult qualified legal counsel for your specific context. This entry is not legal advice.

If a touch target meets the minimum size in an automated check, is it fully accessible?

Not necessarily. Meeting a size threshold in an automated scan addresses only one measurable aspect. Automated testing detects only a portion of potential issues and cannot fully evaluate spacing, overlapping targets, real-world reachability, or how the control behaves with assistive technology. Manual testing and testing with assistive technologies and actual touch interaction are generally needed to confirm a usable experience.

How do WCAG 2.1 and WCAG 2.2 differ in how they address touch target size?

WCAG 2.1 introduced a target size success criterion at the AAA level. WCAG 2.2 added a related target size criterion at the AA level with its own thresholds and exceptions. Because the applicable version and conformance level affect which criterion applies, you should confirm which WCAG version you are targeting and review the specific success criterion text and its exceptions in that version.

What conformance level is commonly cited as a target for touch target sizing?

AA is the level most commonly cited as a conformance target in policies and settlements. Under WCAG 2.1 the more stringent target size criterion sits at AAA, while WCAG 2.2 introduced a target size criterion at AA. Which level you must meet depends on your governing policy, contract, or regulatory context rather than a single universal rule.

How should spacing between adjacent touch targets be handled?

Adequate spacing between adjacent interactive controls generally reduces accidental activation and can help satisfy the relevant WCAG target size criterion, which commonly accounts for spacing as well as raw dimensions. Review the exact wording and exceptions of the success criterion in the WCAG version you are targeting, and verify behavior through manual testing on actual touch devices.

Do the touch target criteria include exceptions?

Yes. The WCAG target size success criteria generally include defined exceptions, which may cover situations such as inline controls within text, targets whose size is determined by the user agent, or cases where an equivalent control meeting the size requirement is available. Consult the specific criterion text in the WCAG version you are applying to confirm which exceptions apply.

Common misconceptions

The 44 by 44 pixel figure is the WCAG AA requirement all sites must meet.

The 44 by 44 CSS pixel value corresponds to Success Criterion 2.5.5, which is Level AAA and was introduced in WCAG 2.1. The Level AA minimum is Success Criterion 2.5.8, added in WCAG 2.2, which generally calls for 24 by 24 CSS pixels with exceptions. Confusing the two misstates both the required dimension and the conformance level.

Any target smaller than the stated dimension automatically fails.

Both target size criteria include defined exceptions, such as adequate spacing between targets, an equivalent control available elsewhere, inline targets, user-agent-determined presentation, or where the presentation is essential. A smaller target may still conform if a relevant exception applies.

Meeting the target size criterion guarantees the interface is accessible and legally compliant.

Conformance with a single success criterion does not ensure an accessible experience for all users, nor does it guarantee immunity from legal claims. Target size is one factor among many, and automated tools detect only a portion of issues; manual and assistive technology testing remain necessary. This entry is not legal advice.

Best practices

Design interactive controls to meet at least the WCAG 2.2 Level AA minimum of roughly 24 by 24 CSS pixels, and treat the 44 by 44 CSS pixel value from the Level AAA criterion as an aspirational target for touch-first interfaces.

Where controls must remain small, apply one of the recognized exceptions deliberately, provide adequate spacing between adjacent targets or offer an equivalent larger control elsewhere, rather than relying on chance.

Measure targets in CSS pixels and verify sizing across responsive breakpoints and varying pixel densities so controls remain adequately sized on the smallest supported viewport.

Ensure sufficient spacing between neighboring targets to reduce accidental activation, particularly in dense navigation, toolbars, and form controls.

Validate target size and activation with manual testing on real touchscreen devices and with users who have motor or dexterity limitations, since automated checks alone will not confirm real-world usability.

Confirm which WCAG version and conformance level your project is targeting, and consult qualified legal counsel and current agency guidance to understand how these criteria relate to your specific obligations, which evolve through regulation and case law.