If you’re designing for people tapping one-handed on a bus, the mobile app ui design principles that matter most start with the thumb. Make every control big enough to hit and spaced so a slip doesn’t trigger its neighbour.
This guide is part of the wider topic of mobile app development, where design choices meet build and release decisions.
| Item | Value |
|---|---|
| WCAG 2.2 AA minimum target size (2.5.8) | 24 by 24 CSS pixels |
| WCAG AAA enhanced target size (2.5.5) | 44 by 44 CSS pixels |
| Google’s recommended minimum for Android controls | 48 by 48 dp |
| Apple’s recommended minimum for iOS controls | 44 by 44 pt |
| Spacing between adjacent targets | 8 dp/pt |
These figures come from Deque University’s target-size rule and the NZ Government touch and pointer target sizing guidance. Standards and platform advice can change, so check the source before you rely on them.
Start with the thumb, not the screen
A phone is rarely used under ideal conditions, so good interface design assumes imperfect taps. Deque University lists the people who benefit from well-sized touch targets, and the list reads like an everyday audience rather than a niche one (Deque University).
- People who use a mobile device where the touch screen is the primary mode of interaction.
- People who access a device using one hand.
- People using a device in environments where they are exposed to shaking, such as public transportation.
The same page adds people with hand tremors and people who tap with only part of a finger. Designing for these cases tends to make an app easier for everyone.
The NZ Government guidance gives a simple habit to build in: test designs with thumbs, not just index fingers. It also suggests thinking through one-handed use from the first sketch (NZ Government).
What size should touch targets be?
There is no single number, because the web standard and the two mobile platforms each set their own bar. Here is how they line up, using the figures in the sources below.
- WCAG 2.2 Level AA (criterion 2.5.8) asks for targets of at least 24 by 24 CSS pixels (Deque University).
- WCAG Level AAA (criterion 2.5.5) is met at 44 by 44 CSS pixels (NZ Government).
- Google recommends 48 by 48 dp for Android controls, and Apple recommends 44 by 44 pt for iOS (NZ Government).
In practice, treat the smaller figure as a floor. The NZ guidance says to use a minimum of 24 for all interactive elements and ideally 44 for primary controls such as the main action on a screen (NZ Government).
Note that the Level AAA criterion is not a legal or formal requirement in the NZ guidance, which says its standard does not require conformance to that level. Following the platform figure is still a sensible default for tap comfort.

Spacing and padding matter as much as size
A small icon can still work if it has room around it. Deque’s rule says that if a target is too small, it must be at least 24 CSS pixels away from any other touch target (Deque University).
For mobile layouts, the NZ guidance recommends 8dp/8pt of spacing between adjacent targets and says to avoid clustering small targets together (NZ Government).
If the visual design calls for a small icon, add invisible padding. BrowserStack’s app accessibility documentation describes it as surrounding the touch target with enough padding to increase the touchable area without altering the visual design (BrowserStack).
One unit note helps when you move between design tools and code. On a standard display 1pt equals 1 pixel, but on Retina displays 1pt is either 2 by 2px or 3 by 3px, so always think in points or dp rather than device pixels (NZ Government).
Which elements need to meet the size rule
The NZ guidance lists the interactive elements that need proper sizing (NZ Government).
- Buttons and controls, including icon buttons.
- Form elements: input fields, checkboxes, radio buttons and toggles.
- Interactive images, such as clickable photos, thumbnails and image buttons.
Inline links or other interactive components within a sentence or a block of text are the listed exception. The guidance also says to make the entire tappable area clear to users, so a large hit area behind a tiny icon should still look tappable.
Let people adjust the interface
Sizing rules set a baseline, but people differ. BrowserStack suggests considering a setting that lets users enlarge touch targets throughout the app to accommodate their individual needs (BrowserStack).
The cost of ignoring this is real. In one example from that documentation, a button measured 57dp x 17dp and was flagged as below the 44dp x 44dp requirement, and the rule’s severity is listed as serious (BrowserStack).
The NZ guidance names the same underlying issue: small targets are difficult to use for people with motor impairments, tremors, dexterity challenges or large fingers (NZ Government).
Check the design before and after build
Size and spacing are easy to verify, so settle them early in the mobile app development process, before code is written. Then repeat the checks on a real device.
The NZ guidance suggests a short hands-on routine (NZ Government):
- Use the app with just your thumb and see whether you can reach every target, especially on larger devices.
- Check tap accuracy: can you hit each target without multiple attempts?
- Try your non-dominant hand and see whether you can still navigate.
- Ask people with motor difficulties to move through the app and note where they get frustrated.
Automated scanners can flag undersized controls too, but they do not replace the hands-on pass. Fold both into your wider mobile app testing plan.
Frequently asked questions
What is the minimum touch target size for a mobile app?
Show answer
It depends on the standard. WCAG 2.2 Level AA asks for at least 24 by 24 CSS pixels (Deque University), while Apple recommends 44 by 44 pt and Google recommends 48 by 48 dp (NZ Government).
Do links inside a paragraph need to be 44 points tall?
Show answer
No. The NZ Government guidance lists links or other interactive components within a sentence or a block of text as not needing proper sizing (NZ Government).
What if a control cannot look bigger?
Show answer
Add padding around it. BrowserStack says that if increasing the element size is not possible, padding can raise the touch target area to 44dp x 44dp (BrowserStack).
How much space should sit between buttons?
Show answer
The NZ guidance recommends 8dp/8pt between adjacent targets (NZ Government). Deque’s WCAG rule uses 24 CSS pixels of distance when a target is under the minimum size (Deque University).



