Android Touch Targets and Contrast: Fix Interaction Barriers, Not Just Scores

Size the interaction area deliberately

Android accessibility guidance recommends touch targets of at least 48 × 48 dp for interactive elements. Padding or an appropriately implemented touch region can enlarge the target without making the icon itself oversized.

Check adjacent controls. Enlarged targets should not overlap in a way that makes the activated action unpredictable. Test list rows, small close buttons, overflow menus and inline icon actions on a physical device.

Measure contrast by content type

For text, WCAG's common AA contrast thresholds are 4.5:1 for normal text and 3:1 for qualifying large text. Relevant non-text controls and visual indicators have their own contrast requirements and exceptions. Do not apply a single ratio indiscriminately to every decorative pixel.

Test scale and semantics together

Use large font and display settings, then check wrapping and control reachability. A label that technically meets contrast but is clipped to two unreadable characters does not solve the task.

Verify that the screen reader announces the action and state. Increasing the visual target cannot repair an unnamed button.

Keep platform units separate

Android dp and CSS pixels are not interchangeable units for blindly transferring numeric requirements. WCAG 2.2's web target-size criteria also have specific thresholds and exceptions distinct from Android's design recommendation.

APKLint's Accessibility Checker can support a review, but measurements and task testing still need the actual UI. Use Android's accessible-app guidance, testing tools and WCAG 2.2 to document the standard and method used. Fix the source components so the improvement survives the next screen redesign.