In this guide
TalkBack is Android's screen reader. It speaks what is on screen and changes how touch works. A pass takes about 15 minutes and finds problems that no visual check will. For a short, general version, read the 10-minute screen reader test first. This page is the Android-specific script.
Turn it on
Go to Settings > Accessibility > TalkBack and press On/Off (the path in Android's testing guide; names vary by phone). Many phones also offer an accessibility shortcut; set it up in the accessibility settings before you start, because the first activation can be confusing. A tutorial launches the first time you enable TalkBack; you can reopen it under Settings > Accessibility > TalkBack > Settings > Launch TalkBack tutorial. If you get stuck, use the same shortcut to turn it off.
Core gestures
With TalkBack on, swiping right or left moves through elements and a double-tap selects the current one, as in Android's testing guide. Other gestures differ by version and phone, so check the tutorial in the TalkBack settings:
| Action | Gesture |
|---|---|
| Hear what is under your finger | Touch and explore with one finger |
| Next / previous item | Swipe right / left |
| Activate the selected item | Double-tap |
| Scroll | See the gesture list in your TalkBack tutorial |
| Go back, home, recents | Use the system navigation as set on your phone |
Practice in the TalkBack tutorial for five minutes before testing your own app.
The script
- Swipe through the first screen from the top. Expect: a sensible reading order, left to right and top to bottom. No item is skipped.
- Every button and icon has a spoken label. Expect: "Search, button", not "unlabelled" and not a file name.
- State is spoken. Toggles, checkboxes, tabs. Expect: "on/off", "selected", "checked".
- Images that matter have a description; decorative ones are skipped.
- Headings are announced so a user can jump between sections, where your screen has sections.
- Fill in a form. Expect: each field's label is spoken when focused, hints and errors are spoken, and the keyboard does not trap focus.
- Trigger an error. Expect: the error is announced, not just shown in red.
- Dialogs and sheets. Expect: focus moves into the dialog, stays in it and returns to the right place after closing.
- Loading and success messages. Expect: the user hears that something happened (a toast or snackbar is read, a spinner has a label).
- Custom views and gestures. Sliders, carousels, swipe actions, drag handles. Expect: each has an alternative a screen reader user can operate.
- Touch targets. Tap small items by double-tap. Expect: they activate reliably.
- Finish the main task with the screen off the visual path. Try to complete sign-in and one core action using only TalkBack. If you can't, neither can a user who depends on it.
Also check
- Large font and display size (see the input checklist).
- Colour contrast and not relying on colour alone.
- Reduced motion, if you animate heavily.
Reporting
For each finding note the screen, the element, what TalkBack said, what it should have said, device, Android and TalkBack version.
Part of the Android app testing guide. Related: entry-level phones and tablets and foldables.
Want more people to run this script on their own phones? See how AppReviewX works for private, structured feedback, and ask your testers to report with the details above.