Orientation
With TalkBack on, touching or dragging across the screen explores items by location, while left and right swipes move sequentially through accessible items. Activation uses a TalkBack gesture, so a normal one-finger tap does not operate the app in the usual way.
Android app and web contexts
TalkBack is used with native Android apps, Chrome web pages, and WebView content embedded inside apps. A product can cross those contexts during one task, so testers should record when a flow moves from native UI to web content, authentication, payment, permissions, or a system dialog.
Reading controls and actions
TalkBack reading controls affect what up and down gestures do. Actions expose available operations for the focused item. When a custom component lacks a useful label, role, state, or action, TalkBack may still reach it but cannot communicate the intended operation.
Product-team implications
Check accessible names for icon buttons, logical swipe order, focus after navigation, form labels and errors, live updates, custom gestures, adjustable controls, WebView boundaries, and recovery after system prompts or external flows.
External keyboard
TalkBack supports keyboard shortcuts through configurable keymaps. Recent documentation distinguishes default and enhanced keymaps, so tests should state the keymap and modifier rather than assuming one universal command set.
Practical route
Run a representative task in Chrome or a native Android app. Identify the first view, move through headings or controls where available, operate a form, trigger an error, recover, confirm the result, and repeat any app-to-web or web-to-app transition.