Article

Tap Targets: How Big Buttons and Links Should Be on Mobile

,

A tap target is any element someone taps to do something on a touchscreen: a button, a link, a menu icon, a checkbox or a form field. The WCAG 2.2 accessibility standard sets a minimum of 24 by 24 CSS pixels at Level AA, or enough space around a smaller target to make up the difference. For the targets that matter most, aim higher: Apple recommends at least 44 by 44 points and Google’s Material Design 48 by 48 density-independent pixels. Targets that are too small, or too close together, lead to mis-taps, frustration and lost enquiries.

Here’s what each standard says, and how to fix the warnings that testing tools report.

What is the minimum tap target size?

The accessibility baseline is WCAG 2.2 success criterion 2.5.8, Target Size (Minimum), at Level AA: each target should be at least 24 by 24 CSS pixels. A smaller target passes if there’s enough space around it that a 24 pixel circle centred on it doesn’t overlap any neighbouring target or its circle.

There are sensible exceptions: links inside a sentence, controls whose action is also available through a larger target on the same page, browser controls you haven’t styled, and cases where the size is essential, such as pins on a map.

WCAG also has a stricter Level AAA criterion, 2.5.5 Target Size (Enhanced), which asks for 44 by 44 CSS pixels.

What is the recommended touch target size on mobile?

For buttons, menu icons and anything people tap often, aim for 44 to 48 pixels in both directions. The platform guidelines agree on roughly that range:

  • Apple’s Human Interface Guidelines: at least 44 by 44 points.
  • Google’s Material Design: at least 48 by 48 dp, with about 8 dp between targets.
  • WCAG 2.5.5 (AAA): 44 by 44 CSS pixels.

The 24 pixel figure keeps you within WCAG 2.2 AA. The 44 to 48 pixel range is what makes it comfortable for someone using their thumb on a bus.

Size your most important buttons for a thumb on a moving bus, and treat the 24 pixel rule as the floor.

A worked example

Say you run a dental practice in Richmond and most of your bookings come from phones. Your header has three icons, for phone, email and the menu, each drawn at 20 pixels and sitting 4 pixels apart. On a phone, people trying to open the menu call the practice by mistake, or tap nothing at all.

The fix needs no visual redesign. Keep the icons at 20 pixels, give each one padding so its tappable area is 44 by 44 pixels, and let the padding provide the spacing. The header looks the same. It just stops fighting people.

The same logic applies to the booking form: make the checkbox label tappable too, so people can tap the words as well as the box.

What does “touch targets do not have sufficient size or spacing” mean?

This is the warning Google’s Lighthouse tool shows in its Accessibility section, and in PageSpeed Insights, when targets on the page fail the WCAG 2.5.8 check. It lists the offending elements, so you can see exactly which links or buttons are too small or too crowded.

Older versions of Lighthouse showed a similar warning in the SEO section, worded “Tap targets are not sized appropriately”, based on Google’s 48 pixel guidance. If you still see that wording in an older report or tool, the fix is the same.

The usual causes are icon buttons with no padding, lists of footer or menu links packed tightly together, and small text links side by side, such as “Privacy | Terms | Cookies”. In CSS, `min-height: 44px` and `min-width: 44px` on buttons and icon links, plus padding on inline-block links, resolves most cases.

How to test your own site

Run your key pages through PageSpeed Insights and check the Accessibility section. Then do the human test: open the site on a phone, use one thumb, and try to tap every menu item, button and form field without zooming. Anything you have to aim at carefully is too small.

How we build for touch

On every site we design, buttons, menus and form controls are sized and spaced for touch from the first wireframe, and we test against WCAG 2.2 AA before launch. If your site is producing tap target warnings, it’s usually a quick fix as part of a wider review. You can read more about our web design in London, or how mobile-first design shapes the rest of the page.

FAQs

What is the minimum target size for WCAG 2.5.8 Level AA?

WCAG 2.2 success criterion 2.5.8 requires interactive targets to be at least 24 by 24 CSS pixels. A smaller target passes if it has enough clear space around it that a 24 pixel circle centred on it doesn’t overlap any other target. Inline text links and a few other cases are exempt.

Do tap targets affect SEO?

Not directly as a ranking factor. Tap target problems make a site harder to use on phones, which can mean fewer enquiries and shorter visits, and they count against your Lighthouse accessibility score. Fixing them is worth doing for usability and accessibility in their own right.

What is the difference between a tap target and a touch target?

They’re the same thing. Google’s older tools said “tap targets”, while WCAG and Lighthouse’s accessibility audit use “target size” or “touch targets”. All of them mean the area of a button, link or control that responds when someone taps it.