App accessibility basics: four practical checks from Google's own guidance
48dp touch targets, content descriptions for screen readers, contrast thresholds and testing with real accessibility settings - from Google's own Android guidance.
Accessibility work is usually framed as a compliance task, which is why it gets deferred. The more useful frame: a significant share of your users cannot complete your signup or checkout if touch targets are tiny, contrast is weak, or screen readers hear "button, button, button". The basics are a short, concrete list - and Google's own Android documentation states the key numbers.
This guide follows the Android "Make apps more accessible" guidance, checked 19 November 2026. The principles transfer to iOS, where the same classes of requirement exist.
The four that catch the most users
- Touch targets of at least 48dp x 48dp. Google's guidance recommends every interactive element have a focusable area of at least 48 by 48 density-independent pixels for touch interfaces (smaller is permitted for precise input like mouse and trackpad). Icon buttons are the usual offender: the visible glyph can stay small, but the tappable area around it must not.
- A description for every UI element. Each element needs a description of its purpose so accessibility services like TalkBack can announce something meaningful. TalkBack automatically announces visible text itself - the gaps are icons, images, and custom controls, where "unlabelled" is what a blind user hears.
- Text contrast that meets the thresholds. Google's guidance: if text is smaller than 18sp, or bold and smaller than 14sp, the contrast ratio between text and background should be at least 4.5:1; for all other text, at least 3:1. They suggest checking with an online contrast checker or the Accessibility Scanner app.
- Large, simple controls. Beyond the 48dp floor, controls that are easy to hit and simply arranged help everyone - motor impairments, one-handed use, moving vehicles.
What "test it" actually means
- Run a scanner. Google's docs point to the Accessibility Scanner app, which walks your screens and flags small targets, low contrast and missing labels. It finds the mechanical issues; it cannot judge flow.
- Do one TalkBack pass of your core flow. Turn on the screen reader, close your eyes, and try to sign up, buy, or book. Every dead end you hit is a user lost.
- Test with system settings, not just defaults. Larger font sizes, display scaling, dark mode and reduced motion all change your layout; overflow at 200% text size is a real-world bug.
Why this pays back beyond compliance
Contrast and target size improvements show up in ordinary usability metrics; content descriptions double as UI-test hooks; and the discipline of describing each element forces the interface to make sense structurally, not just visually. Accessibility debt behaves like other technical debt: cheapest at design time, expensive as retrofit.
Related: ASO basics and our platform choice guide.
Sources
- Android Developers: Make apps more accessible (checked 19 November 2026): https://developer.android.com/guide/topics/ui/accessibility/apps
Drafted with AI assistance from this source. Platform guidance evolves and legal requirements vary by market; check the current Android and iOS accessibility documentation for your target releases.