Touch Target Size Checker

Enter a target's width, height and the gap to its nearest neighbour. See whether it passes WCAG 2.5.8 (24×24 CSS px, or the spacing exception), WCAG 2.5.5 (44×44), Apple HIG (44 pt) and Material (48 dp), and convert px, pt, dp and mm.

WCAG 2.2 Success Criterion 2.5.8 Target Size (Minimum), Level AA, requires pointer targets of at least 24 × 24 CSS pixels.

Use the Touch Target Size Checker

Target Dimensions

Unit

Spacing to the nearest target (WCAG 2.5.8 exception)

Device (for physical size)

Quick presets

Compliance Results

Visual Size Preview

Blue dashed = 44 reference · grey circle = 24 px circle · coloured box = your target

px, pt, dp and mm converter

Uses the scale factor and density set above. CSS px, iOS pt and Android dp are treated as one logical unit; device px = unit × scale; inches = device px ÷ ppi.

—
CSS px = pt = dp
—
device pixels
—
millimetres
—
inches

Touch target size requirements

GuidelineSizeNotes
WCAG 2.2 SC 2.5.8 Target Size (Minimum), AA24 × 24 CSS pxSmaller passes if its 24 px circle does not intersect another target or another undersized target's circle; also exempt: equivalent control, inline text, unmodified browser control, essential.
WCAG 2.2 SC 2.5.5 Target Size (Enhanced), AAA44 × 44 CSS pxExceptions: equivalent 44 px control, inline text, unmodified browser control, essential. No spacing exception.
Apple HIG — iOS, iPadOS, watchOS44 × 44 pt (min 28 × 28)Default control size; Apple suggests about 12 pt padding around bezelled controls and 24 pt around unbezelled ones.
Apple HIG — macOS / visionOS / tvOS28 / 60 / 66 ptMinimums 20, 28 and 56 pt.
Android accessibility (Material)48 × 48 dppx = dp × dpi ÷ 160 (1 dp = 1 px at 160 dpi).

Sources: W3C Understanding 2.5.8 and 2.5.5; Apple HIG Accessibility; Android Make apps more accessible and screen densities. In CSS, 1in = 96px and 1pt = 1/72in as absolute units; the physical size of a CSS px on a phone depends on the device.

Quick answer

WCAG 2.2 Success Criterion 2.5.8 Target Size (Minimum), Level AA, requires pointer targets of at least 24 × 24 CSS pixels. A smaller target still passes if a 24 px diameter circle centred on it does not overlap any other target or the circle of another undersized target, which means about 24 px centre to centre between small targets. The AAA criterion 2.5.5 asks for 44 × 44 CSS pixels. Apple's HIG uses 44 × 44 pt as the default control size on iOS (28 × 28 pt minimum), and Android recommends at least 48 × 48 dp. Inline links in text and browser-default controls are exempt.

Examples

TargetWCAG 2.5.8 (AA)WCAG 2.5.5 (AAA)Apple 44 pt / Android 48 dp
24 × 24 pxPass (size)FailFail / Fail
20 × 20 px, 4 px gap, small neighboursPass (24 px centre to centre)FailFail / Fail
20 × 20 px, 2 px gap, small neighboursFail (needs 4 px gap)FailFail / Fail
44 × 44 pxPassPassPass / Fail
48 × 48 pxPassPassPass / Pass

Enter your target size and spacing to check every standard at once.

Summary

Enter a target's width, height and the gap to its nearest neighbour. See whether it passes WCAG 2.5.8 (24×24 CSS px, or the spacing exception), WCAG 2.5.5 (44×44), Apple HIG (44 pt) and Material (48 dp), and convert px, pt, dp and mm.

How it works

  1. Enter the width and height of the clickable area (include padding that is part of the button) and pick px, dp or pt.
  2. Enter the edge-to-edge gap to the nearest other target, whether it sits beside or above/below, and whether that neighbour is also smaller than 24 px.
  3. Read pass or fail for WCAG 2.5.8 (AA), WCAG 2.5.5 (AAA), Apple HIG and Android/Material, plus the extra width, height or gap needed.
  4. Set the device scale factor and screen density to see the physical size in mm.
  5. Use the unit converter to turn px, pt, dp, device pixels, mm or inches into each other.

Use cases

  • Checking icon buttons, close buttons and pagination links for a WCAG 2.2 AA audit.
  • Working out how much spacing small toolbar icons need to pass the 2.5.8 spacing exception.
  • Comparing a web design against Apple HIG and Android touch target guidance.
  • Converting a 48 dp or 44 pt target into millimetres for a given phone density.
  • Writing evidence for an accessibility conformance report.

Frequently Asked Questions

Last updated: 2026-10-10 · Reviewed by Nham Vu