How to inspect touch zones used by navigation buttons

You tap Back, Home, or a navigation button in an app, but the screen does not respond every time. The cause might be a touchscreen area that misses input, an operating system gesture taking over, or a button that is difficult to tap.

Start by checking which parts of the screen register touches. The Touch Screen Test can show touch points and help you look for dead zones. It cannot inspect another app's button layout or change the operating system's navigation settings, so use the results to narrow down where to look next.

Check the areas around the navigation buttons

1. Open the Touch Screen Test on the device with the problem. Use the screen in the same orientation as when the navigation button misses your tap.
2. Touch the center of the screen, then tap the areas around the navigation buttons. Include the screen edge and the space just above the buttons. Watch whether each touch appears in the test.
3. Tap each area several times at a steady pace. Then slowly drag a finger across the area. Look for a spot where the touch point disappears, jumps, or stops following your finger.
4. If the test supports multiple touch points, place two fingers on different parts of the display and move them. This can help reveal whether the trouble affects one zone or a larger part of the screen.

Do not judge the result from one missed tap. Lift your finger between taps, keep your finger pad on the glass, and repeat the same path. If the navigation controls are part of an app, also test those controls in that app. A touch test can show that the screen reports input in a location, but it cannot confirm that the app's button receives or acts on that input.

What the result means

The same area misses touches in the test and in other apps

A repeatable patch that fails across several apps points toward a touchscreen or screen-layer problem. Test the area in both portrait and landscape orientation if the device allows it. If the missed area stays in the same physical place on the glass, rather than following a button on screen, the touch layer may have a dead zone.

The test registers touches, but one navigation button does not work

The screen is reporting touches at that location, so check the button itself. It may be too small, placed too close to the edge, covered by an overlay, or affected by the app's layout. If other controls in the same app work, try rotating the device or increasing the app's display size if it offers that option.

The problem is limited to the bottom edge

Phones often reserve the bottom edge for system navigation. A swipe may trigger a Home or Back gesture instead of reaching the page, and the operating system may keep a navigation bar outside the browser's touch area. The test only receives the touches that the browser passes to the page. It cannot inspect touches intercepted by the system.

Touches work in the test but fail in one app

This points more toward the app, its layout, or a setting that changes touch behavior than a general dead zone. Check whether the button is partly covered by a pop-up, toolbar, or screen magnifier. Update or restart the app, then test again.

How to fix missed navigation taps

1. Clean and dry the screen. Wipe away moisture, oil, or dirt with a soft cloth. Water droplets and grime can make taps register in the wrong place or not register at all.
2. Check the case and screen protector. Remove a case that overlaps the display edge. If a protector is cracked, lifting, or covering the button area, remove it if safe and retest. Do not press hard on a cracked screen.
3. Check the phone's navigation mode. On many Android devices, open Settings › System › Gestures › System navigation and check whether gesture navigation or three-button navigation is selected. Menu names vary by device. On Samsung phones, look under Settings › Display › Navigation bar. A navigation-mode change can alter how the bottom edge responds, but it will not repair a physical dead zone.
4. Review touch settings on an iPhone or iPad. Open Settings › Accessibility › Touch and check whether Touch Accommodations is changing how long a touch must last or how repeated touches are handled. iPhones use gestures rather than a standard row of Android-style navigation buttons.
5. Check touch settings on a Windows touchscreen. In Windows 11, open Settings › Bluetooth & devices › Touch, if that page is available, and review the touch and gesture options. A Windows touchscreen test can help check input, but it does not diagnose a phone's system navigation area.
6. Compare with another browser or app. If the problem appears only in one browser, app, or web page, update it and check for overlays or display scaling that may shift the button. A touchscreen test in a browser cannot confirm the app's own clickable regions.
7. Restart the device. A restart can clear a temporary input or app problem. Retest the same places afterward, using the same screen orientation.

Mac computers do not have native touchscreen controls for their displays. If you are testing an external touch display connected to a Mac, its behavior may depend on the display and its software. For the built-in trackpad, use System Settings › Trackpad; trackpad settings do not diagnose touchscreen zones.

When the touchscreen may be damaged

A likely hardware fault is a fixed strip or patch that repeatedly misses touches across different apps, after you clean the glass and remove any case or protector that could interfere. If the fault remains in the same physical location after a restart, take photos or notes showing the affected area and contact the device maker or a repair shop. A screen replacement may be needed. If the device is under warranty, ask the manufacturer about coverage before opening or repairing it.

Why a navigation button can be hard to test in a browser

A browser page sees touch input only when the operating system sends it to the page. System navigation gestures, edge swipes, and on-screen system controls can take priority. The browser test also cannot tell whether a visible button in another app is positioned correctly or whether that app responds to its tap.

Use the test to compare touch response across the display, then repeat the same action in the app or system screen where the navigation problem occurs. That comparison helps separate a touch-sensitive area from a navigation setting or button-layout issue.