Loading the page...
Preparing tools and content for you. This usually takes a second.
Preparing tools and content for you. This usually takes a second.
Fetching calculator categories and tools for this section.
Free tap target size calculator. Get physical size (mm), WCAG 24px baseline Pass/Fail, and 44 / 52 / 58px context targets. Pair with contrast ratio for button labels.
Last updated: May 24, 2026
Sizing text inside buttons? Font size accessibility calculator
Smallest Side (Physical Size)
3.43 mm
Recommended Minimum
44px
WCAG Baseline Status
Pass
Target size is strong for the selected context and supports reliable touch interaction.
Pair target size checks with spacing and gesture testing on real devices.
We can build and embed a custom version of Touchscreen Tap Target Size Calculator for your brand and workflow.
Answers: minimum button size for mobile, 44px vs 24px WCAG, and tap target size in mm on your PPI.
Default 44 px — drives WCAG baseline and context comparison.
Same 44 px is 3.43 mm at 326 PPI vs 4.23 mm at 264 PPI (iPad).
Pass WCAG 24px yet still need larger targets for senior or a11y-priority UIs.
Default: 44×44 px · 326 PPI · general → min side 44 px · 3.43 mm · WCAG 24px baseline Pass · context target 44 px · meets recommendation.
Min Side
44 px
Physical
3.43 mm
WCAG ≥24px
Pass
Context Min
44 px
| Context | Min px | Reference |
|---|---|---|
| General audience | 44 px | Apple HIG / common UX baseline; aligns with WCAG 2.5.8 Enhanced (44px) intent |
| Senior-friendly UI | 52 px | Reduced precision and tremor — larger than default mobile chrome |
| Accessibility-priority UI | 58 px | Kiosks, health apps, motor impairment focus |
| Rule | Size | Note |
|---|---|---|
| WCAG 2.5.8 Target Size (Minimum) — AA | 24 × 24 CSS px | Exceptions for inline text, user agent controls, essential presentation |
| WCAG 2.5.8 Target Size (Enhanced) — AAA | 44 × 44 CSS px | Stricter spacing/size — matches general 44px planning target |
| This calculator baseline flag | Pass if min(width,height) ≥ 24 px | Does not evaluate spacing exceptions or overlapping targets |
| Device | PPI | 44 px physical |
|---|---|---|
| iPhone (typical) | ~326 | 3.43 mm at 44 px min side |
| High-density Android | ~420 | 2.66 mm at 44 px (same px, smaller physical) |
| iPad | ~264 | 4.23 mm at 44 px (larger physical touch area) |
Pixel thresholds for WCAG and UX planning; millimeters help compare across devices with different pixel density.
targetMinPx = min(widthPx, heightPx)physicalMm = (targetMinPx ÷ PPI) × 25.4wcagBaseline = targetMinPx ≥ 24contextOK = targetMinPx ≥ 44 | 52 | 58 (by profile)3.43 mm · WCAG Pass · meets 44px target.
min 36 px · 2.18 mm · WCAG Pass · needs 58px — increase size or hit area.
1.56 mm · Fail (<24px) — below all context targets.
1.87 mm · WCAG Pass · below 44px general — increase for production UI.
min 48 px · 3.74 mm · WCAG Pass · need 52px — add 4px on smaller side.
Same 44 px as iPhone → 4.23 mm (vs 3.43 mm at 326 PPI).
min 32 px · WCAG Pass · fails 44px — expand height or touch padding.
4.52 mm · meets 58px context target.
Share with mobile designers, design systems teams, and accessibility auditors checking WCAG 2.5.8.
Suggested hashtags: #Accessibility #MobileUX #TouchTargets #WCAG #InclusiveDesign