Touch and external keyboard
Android
A practical guide to TalkBack on Android for native apps, mobile web, embedded web views, forms, controls, dynamic updates, and recovery.
Course progress: 0 / 20 lessons
LESSON 10 OF 20
TalkBack
TalkBack is Android's built-in screen reader. It supports touch exploration, sequential gestures, reading controls, external keyboards, and web or native app workflows across a varied Android device landscape.
This reference assumes that you have completed the foundation course and understand names, roles, states, focus, and dynamic updates.
Choose an environment
What TalkBack testing depends on
Accessible nodes
TalkBack presents labels, roles, states, actions, text, headings, lists, controls, and other information exposed through Android and browser accessibility APIs.
Accessibility focus
Users move TalkBack focus through available items, hear the current item, and activate it with TalkBack gestures or keyboard commands.
Reading controls
TalkBack reading controls change what up and down gestures adjust, such as navigation granularity or speech settings. Available controls depend on context and device settings.
Device and version variation
Android version, TalkBack version, manufacturer customisations, navigation mode, keyboard keymap, and browser or app technology can all affect testing results.
One reader, several product contexts
| Environment | Primary input | What shapes the experience |
|---|---|---|
| Android | Touch and external keyboard | Android apps, Chrome web content, WebView flows, reading controls, and device variation |
TRY THIS NOW
Match TalkBack to the Android task
Choose one Android product flow and identify which parts need a TalkBack-specific check.
- Native appCheck labels, actions, focus after navigation, system dialogs, and custom components.
- Chrome webCheck headings, controls, form recovery, live updates, and browser-specific behavior.
- WebViewRecord where the task crosses from native UI into embedded web content.
- InputState whether the route used touch gestures, an external keyboard, or both.
What product teams should take from this
- TalkBack with Chrome is the baseline Android web combination, but native apps and embedded web views need their own task checks.
- Gesture navigation, three-button navigation, and manufacturer customisations can change recovery paths and system gestures.
- Record Android version, TalkBack version, device model, app or browser, navigation mode, and whether touch or keyboard input was used.
- User observations will be added after credited research with regular users; they are not inferred from documentation.
Editorial model reviewed 4 August 2026. Command sheets must be rechecked when Google changes TalkBack gestures, keyboard keymaps, or Android accessibility guidance.
Knowledge check
Answer every question, then use the forward lesson button to record this lesson as complete. The check is not scored and can be repeated.