Choose tools by the question
| Tool or method | Useful for |
|---|---|
| TalkBack | Spoken labels, focus order and nonvisual task completion |
| Switch Access or keyboard | Reachability without precise touch gestures |
| Accessibility Scanner | On-screen suggestions about labels, targets and contrast |
| Compose UI Check | Design-time checks across preview configurations |
| Automated UI tests | Repeatable assertions about semantics and interaction |
| Testing with disabled users | Barriers that implementation assumptions miss |
Android's current accessibility documentation is increasingly Compose-oriented, with separate Views references where needed. Use the branch matching the UI technology rather than applying a Views attribute mechanically to a composable.
Test a full task with TalkBack
Enable TalkBack through the device's Accessibility settings; OEM navigation can differ. Move through the app in sequence, activate controls and complete the main task without relying on visual position.
Listen for unnamed icons, duplicate labels, unexplained state changes and focus moving behind a dialog. A button described only as “button” needs a meaningful accessible name, not another decorative icon.
Use scans as investigation leads
Run a scanner on representative screens and states, including errors, expanded menus and dialogs. Fix the underlying layout or semantics rather than hiding elements from accessibility to silence a warning.
A tool can flag contrast or target size but cannot decide whether instructions make sense to a first-time user.
Record reproducible findings
Include app version, device, OS, assistive technology, starting state, actions and expected outcome. Prioritize barriers that prevent task completion before cosmetic improvements.
APKLint's Accessibility Checker is a review aid for selected inputs and checklist signals. It is not Google's on-device Accessibility Scanner and does not operate TalkBack inside your app.
Use Android's testing guide and accessible-app guidance to choose complementary tests. Name the methods actually performed instead of declaring complete compliance after a single automated report.
Sources and further reading
Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
