Touch target size for a child learning app

Your child taps a button in a learning app, but the wrong activity opens, or nothing happens. The button may be too small or too close to another one. A screen problem can cause similar misses, so check the tablet as well as the app before changing the layout.

The Touch Screen Test checks how the screen registers touches and can reveal dead zones. It does not measure the buttons in another app, but it can help you tell whether missed taps come from the screen or the app design.

Check the screen and the app

1. Open the Touch Screen Test on the same phone or tablet your child uses. Testing that device matters because a different screen may respond differently.
2. Follow the test and tap across the screen, including near the edges and the spots where the child often misses. Watch where touch points appear, and note any areas that do not register.
3. If the test supports multiple contact points on the device, try two fingers at once. This can help identify a screen issue when an app expects a child to use a two-finger gesture.
4. Open the learning app and watch a few normal tasks. Notice whether the child misses one particular button, taps a nearby button by mistake, or has trouble across the whole screen.
5. If you can change the app design, try a larger interactive area and more space between neighboring buttons. Repeat the same task and compare how often taps land correctly.

Do not judge a button by the size of its picture alone. The touch target is the full area that accepts a tap. A small icon can sit inside a larger invisible hit area, while a large-looking picture may have a smaller active area than it appears to.

What the result means

Touches register across the screen

If the test registers taps where you make them, the screen is probably responding in those areas. If your child still misses one app button, look at its active touch area, nearby buttons, and the app's layout before assuming the tablet is faulty.

The same screen area misses taps in the test and the app

A repeatable unresponsive patch suggests a screen or digitizer problem. A digitizer is the layer that detects touch. Remove anything that may interfere, such as a damaged screen protector, then test again. If the same patch remains, the app may not be the cause.

Touches work in the test, but neighboring app buttons get tapped

This often points to targets that are too small or packed too closely together. The child may be touching the edge of one target and landing inside another. Make the active areas larger and add space between them, then try the task again.

Misses happen across several apps or in different places each time

Check for a screen that is dirty, wet, cracked, or covered by a poorly fitted protector. Restart the device and retest. If touch input also fails in the Touch Screen Test, treat this as a possible device issue rather than only changing one app's buttons.

Large buttons still feel difficult to use

Size is only one part of a usable target. A child may need more space between choices, clearer feedback after a tap, or fewer buttons on the screen at once. Age, motor control, posture, and the type of activity all affect what feels easy to hit.

Make learning app targets easier to tap

1. Enlarge the active area, not just the artwork. For a child-facing interface, 48 to 64 CSS pixels square is a practical starting range for frequently used buttons. CSS pixels are the browser's logical sizing units, not necessarily the same as physical screen pixels. Use a larger target when a child still misses it.
2. Leave a gap between choices. Start with about 8 to 12 CSS pixels of clear space between neighboring targets, then increase it if taps still land on the wrong choice. Avoid placing a small close, back, or delete control right beside a large activity button.
3. Check common accessibility guidance. WCAG 2.2 includes a 24 by 24 CSS pixel minimum target criterion, with exceptions, and a 44 by 44 CSS pixel enhanced criterion. These are general accessibility benchmarks, not a guarantee that a target will work for every child. Platform guidance also commonly uses larger logical units, such as 44 points on Apple interfaces and 48 density-independent pixels on Android.
4. Keep the layout clear as well as large. Use familiar shapes and labels, make important actions easy to distinguish, and show a clear response when a button is tapped. If two choices are close in meaning or appearance, extra size alone may not prevent mistakes.
5. Retest after changing display size. On Windows 11, check Settings › System › Display › Scale. On macOS, open System Settings › Displays. On Android, look under Settings › Display › Display size and text. On iPhone or iPad, check Settings › Display & Brightness › Display Zoom. These settings can change the overall layout, so check the app again after changing them.

When the screen may need repair

If the same area fails repeatedly in the Touch Screen Test and in more than one app, remove the case or screen protector if it is safe to do so, clean and dry the screen, and restart the device. Do not press hard or rub a damaged screen. If the unresponsive area remains, document where it occurs and contact the device maker or a repair shop. A screen with a persistent dead zone may need repair or replacement.

Test with the child, not only with a ruler

Guideline sizes help you choose a starting point, but they cannot show whether a particular child can use a particular screen comfortably. Try the app in its normal orientation and at the distance the child usually holds it. Give the child a few chances to tap the same controls without rushing. Watch for repeated misses, accidental choices, and taps that need several attempts.

For an app redesign, compare one change at a time, such as enlarging a button while keeping its position the same. This makes it easier to tell whether size, spacing, or the overall layout helped. The screen test can rule out some touch problems, but only using the learning app shows whether its targets work for the child.