Skip to main content

Test with a Screen Reader

Why?

In WebAIM's Screen Reader Surveys they've been conducting for the past 15 years, the amount of Android screen reader users has been increasing, and in the latest survey from 2021, the percentage of Android users from screen reader users surveyed was about 25%.

The easiest way to test your app with a screen reader is to use Android's built-in screen reader called TalkBack. You can set it up to a physical device and emulator.

Install TalkBack on Physical Device

Your Android device might already have TalkBack installed. You can check it from Settings > Accessibility Settings > Screen Reader, or Settings > Accessibility Settings > Installed Services > TalkBack, or similar, depending on your phone's model.

If it's not installed, install Google Accessibility Suite as TalkBack is part of it.

Install TalkBack on Emulator

Read instructions for setting up TalkBack on the emulator.

Gestures

You can read about the most common gestures for navigation with TalkBack and how to test with TalkBack from Orange Digital Accessibility's Talkback user guide.

If you prefer a video, there's TalkBack - Accessibility on Android by Android Developers (embedded next), explaining how to set up TalkBack and how to navigate with it.

Testing

Orange Digital Accessibility provides a testing procedure for TalkBack testing. The following list is from their site:

Use the application on the differents use cases and check that all the information is vocalized in a logical and understandable order as well as:

  • Are all the significant elements accessible?
  • Is all the information vocalized in a logical and understandable order?
  • Are the interactive elements vocalized with the associated action? (button, checkbox ... Double tap to activate)
  • Are the states of the elements specified? (disabled, checked)
  • Are temporary messages and alerts vocalized?
  • Are the transitions between activities vocalized?
  • Are error messages and dynamic content vocalized?
  • Are the horizontal scrolls vocalized?
  • Are visible items the only items to be vocalized (no ghost items vocalized)?
  • Are the titles of the activities vocalized?
  • Is the workflow easy?
  • Is the vocalization coherent, succinct, and simple?
  • Are decorative images well ignored? And on the contrary, are the meaningful images vocalized?

Ideally, the test should be done without looking at the screen, or by activating the black screen (Darken the screen).