WebInclusiveby Giuseppe Stumbo

Android and TalkBack testing

With TalkBack, try to find an element, understand what it does and activate it. This guide takes you through Android checks, from gestures to text settings, to document what happens on a real device.

Essential Android checks with TalkBack

Follow a journey and observe how content, controls and states are reached and announced. Start with these checks to gather initial evidence.

  • Android

    Testing Android with TalkBack

    On Android, try reaching a control, understanding what it does and activating it with TalkBack. Observe exploration order, names, roles and states on a real device, then repeat the journeys with the intended user settings.

    • Turn on TalkBack in accessibility settings, explore by dragging one finger, then repeat the same flow with forward/backward swipes to identify differences between visual order and focus order.
    • Double-tap to activate, swipe with two fingers to scroll, and use reading controls to change granularity between headings, controls, links or text.
    • Check that buttons, tabs, switches, checkboxes, menus, dialogs and temporary messages have sufficient names, roles, states and instructions without relying solely on visual position.
    • Repeat tasks with larger text, increased display size, high contrast, portrait/landscape orientation and an external keyboard if the product supports one.
    • Document each issue with the device, Android version, app/browser, steps, expected result, TalkBack announcement and impact on the task.

TalkBack modes of use to cover in practice

Explore the same journey using direct touch, linear reading and available navigation levels. Differences between these modes help identify where the difficulty arises.

  • Touch exploration and double-tap activation

    A useful first test on Android is to touch the screen as someone exploring the layout would: ambiguous naming, unstable order and targets that are hard to activate soon become apparent.

    • Drag one finger across the screen to explore the elements under it and hear their name, role and state.
    • When focus is on the right element, double-tap to activate it and check that the expected action starts.
    • Observe whether cards, clickable rows, chips and custom controls have a clear, consistent active area.

  • Swipe

    Forward and backward linear navigation

    TalkBack swipes reveal the actual order of a flow: if focus skips, goes backwards or enters unexpected areas, the problem is often structural.

    • Swipe right to move to the next element and left to return to the previous one.
    • Check that hidden, duplicate or decorative elements do not interrupt linear reading.
    • Check focus return after closing modals and menus, and its destination after screen changes; status toasts must not move focus unnecessarily.

  • Granularity

    Headings, controls and other reading levels

    Test TalkBack by changing granularity or reading level as well, to see whether headings, controls and important blocks are genuinely reachable through useful shortcuts.

    • Open the TalkBack menu or change reading controls to move between headings, controls, links and other available elements.
    • Check whether long pages, WebViews or dense lists remain explorable without relying solely on linear swipes.
    • Record cases where content can be read visually but provides no useful shortcuts for assistive navigation.

  • Input

    Fields, keyboard and contextual actions

    In forms and interactive widgets, pay close attention to how TalkBack enters a field, announces instructions and errors, and supports the user through available actions.

    • With the field focused, double-tap to enter it, type with the on-screen keyboard and listen to instructions, value, error and confirmation.
    • Check whether sliders, pickers, drag actions, custom swipes or context menus have an accessible alternative.
    • Check consistency between the visible label, announced name and updated state after interaction.

TalkBack: navigation and activation

Perform compound one-finger gestures without lifting your finger between the two directions. Before testing, record the Android and TalkBack versions and assignments in Customise gestures. Multi-finger commands require a compatible device; system combinations also depend on the selected Android navigation method. Selection, activation and scrolling are separate operations. Check focus after each action.

1 finger: drag
Explore touched elements.
1 finger: tap
Select an element.
1 finger: swipe right / left
Next / previous element.
1 finger: double-tap
Activate the selected element.
1 finger: double-tap and hold
Long-press the selected element.
2 fingers: vertical swipe
Scroll content.
2 fingers: horizontal swipe
Scroll sideways.
Selected slider: swipe up / down
Increase / decrease the value.
Slider: double-tap, hold and drag
Adjust the slider directly.

TalkBack: reading, menu and search

Choose the reading control first: characters, words, lines, paragraphs, headings, links or controls. Available options depend on the content and configured menu. Google documents horizontal and vertical variants of three-finger gestures: check the mapping on the device.

1 finger: up then down / down then up
Next / previous reading control.
3 fingers: swipe right / left
Change the reading control according to its assignment.
3 fingers: swipe down / up
Alternative gesture for changing reading control.
1 finger: swipe down / up
Move forwards / backwards at the chosen granularity; adjust speed or other values when selected.
3 fingers: tap; or 1 finger: down then right
TalkBack menu.
2 fingers: triple-tap
Read from the next element.
2 fingers: tap
Pause / resume speech.
3 fingers: touch and hold; or 1 finger: left then down
Search the screen.
1 finger: right then up
Voice commands; wait for the signal before speaking.
TalkBack menu → Actions
Actions for the selected control, if available.

TalkBack: typing and editing text

Editing requires an editable field or selectable text. With Gboard, explore the keys and release the chosen key; some keys require a double-tap. Selection, copying and cutting depend on the active text.

2 fingers: double-tap and hold
Turn selection on / off.
3 fingers: double-tap
Copy the selection; outside selection mode, this may copy the focused text.
3 fingers: double-tap and hold
Cut the selected text.
3 fingers: triple-tap
Paste into the field.
Characters or Words control + swipe up / down
Move the cursor through the text.
Back gesture with the keyboard open
Close the keyboard.

TalkBack: system, audio and tools

The two-finger edge gestures shown here require Android gesture navigation. With the three system buttons, select and activate the corresponding buttons. Media and call actions depend on context.

1 finger: up then left
Home.
1 finger: down then left
Back.
1 finger: left then up
Recent apps.
2 fingers: swipe up from the bottom edge
Home with gesture navigation.
2 fingers: swipe up from the bottom edge and hold
Recent apps with gesture navigation.
2 fingers: swipe inward from a side edge
Back with gesture navigation.
1 finger: right then down
Notifications.
2 fingers: swipe down from the top
Notifications; repeat for Quick Settings.
2 fingers: double-tap
Play / pause; manage a call when present.
4 fingers: tap
Gesture practice.
4 fingers: double-tap
TalkBack help.
4 fingers: double-tap and hold
Pass the next gesture to the system without TalkBack interpreting it.

Google sources and configuration

Compare the guide with the device's assignments. You can customise almost all gestures; two-finger scrolling cannot be reassigned.

Gestures, real devices and evidence collection

Note the device, settings and gestures while testing the journey. This information allows your team to repeat the assessment under the same conditions.

  • Matrix

    State the devices, operating systems and assistive technologies tested

    For native apps, the Notes field and methodology section must state the devices, system versions and assistive technologies used in testing.

    • Real iPhone and Android devices provide stronger evidence than emulators.
    • Identify VoiceOver and TalkBack by name.
    • Also record large text, orientation and reduced motion.

  • Gestures

    Document gestures and alternatives in the remarks

    For criteria such as Pointer Gestures or Target Size, remarks must explain when an accessible alternative exists and when interaction remains unreliable.

    • Describe double taps, linear swipes, the rotor or reading controls when relevant.
    • Highlight cases involving dragging, multiple gestures or targets that are too small.
    • Connect the criterion to journeys, rather than only an isolated control.

  • Evidence

    Keep evidence useful for remediation and release

    On mobile, collect screenshots, recordings, focus notes and platform details to preserve context between the audit, fix and retest.

    • Makes comparison between iOS and Android easier.
    • Helps native teams understand the root of the issue.
    • Provides a stronger basis for the statement and history.

Comparing reports

Illustrative example, not an actual report. It shows the difference between a generic note and one that enables an issue to be reproduced and fixed.

  • Device and OS

    Weak note
    Android, recent version.
    Verifiable note
    Samsung Galaxy S21 with Android 14, TalkBack enabled, demo build 1.4.0. In an actual report, also record the TalkBack version, exact system versions and second device, if used.

  • System state

    Weak note
    Default settings.
    Verifiable note
    Text size at 130%, screen magnification disabled, landscape orientation. In an actual report, also document display size and customised TalkBack gestures.

  • Observed behaviour

    Weak note
    Swiping does not read the list properly.
    Verifiable note
    Open the six-product list and swipe right: TalkBack moves from the second to the fourth product and from the fifth to the final button, without reading the third and sixth. View recycling is a hypothesis to investigate, not a cause demonstrated by the test.