GratisAI

Accessibility · official-source review · reviewed 2026-10-10

Check Button and Link Target Sizes for Touch Accessibility

Most mobile buttons are too small for fingers to tap accurately, causing errors and frustration.

What this guide helps you do

Check whether your interactive targets meet WCAG 2.2 minimum target size (24 CSS pixels).

Who this guide is for

Web and app builders checking tap target sizes for mobile accessibility.

Use the source document or official route that applies to your situation. This guide does not contact another person or verify external information.

Steps

  1. Measure target size

    Measure the clickable/tappable width and height of your button or link in CSS pixels.

  2. Check spacing

    Targets must also have at least 8px spacing to adjacent targets if they are smaller than 44px.

  3. Size up

    Increase tap target area to at least 24×24 CSS pixels, ideally 44×44 for critical controls.

  4. Test with your thumb

    Test on a real phone, not just on desktop.

Worked example

A 20×20 pixel button fails the 24px minimum; size it to at least 24×24 and keep 8px spacing to other targets.

Use your own source and details. The example is not a record about a real person or organization.

What the sources say

Understanding Target Size (Minimum)

W3C Web Accessibility Initiative · reviewed 2026-10-10

What this source supports: WCAG 2.2 requires a minimum 24×24 CSS pixel target size for pointer inputs, with spacing exceptions when targets are at least 8 pixels apart.

Source limit: Target size is one of many pointer-accessibility requirements; test on real touch devices.

These sources support the statements above. They do not show that every person needs this guide. They do not show a specific result.

Limits

This compares target sizes you measure to WCAG 2.2 minimum size. It does not inspect your page.

Target size is one of many pointer-accessibility requirements; test on real touch devices.

Use current instructions from the responsible organization. This guide is a planning aid, not an official decision or a substitute for qualified advice.

Common questions

What does the App compute?

Compare tap target dimensions against WCAG 2.2 minimum size.

What does the App not do?

This compares measured sizes. It does not inspect your page or code.

Where do the numbers come from?

You enter every number yourself. The sources support the method and the limits. They do not produce a result for your specific case. Keep the original documents next to the sheet you build.

Before you start

Free Companion App

The App computes the worked example with your own numbers, in your browser.

The App runs in this browser. It does not send or save entries. Copy, download, or print only when you choose.

This guide uses short, direct instructions as an ASD-STE100-style writing target. It is not a formal certification.

About this guide

Category
Accessibility
Reading time
About 3 minutes
Last reviewed
Cost
Free to read. No account is required.

Companion App: Touch Target Size Accessibility Check. It runs in this browser and does not upload your entries.

This guide is edited for clarity and checked against the sources it links. It is not a substitute for official instructions or qualified advice. A linked source does not show that every person needs this guide.