Skip to main content

Use ScreenReader on Android in Live

Use the ScreenReader feature on real Android devices in Live.

Introduction

Manual accessibility testing for mobile websites is important to ensure that your websites are fully Web Content Accessibility Guidelines (WCAG) compliant for differently abled users accessing the websites from their phones. The Live ScreenReader feature enables manual accessibility testing of your mobile websites on supported real Android devices and browsers.

Similar to Google TalkBack on an Android device, using the ScreenReader feature on Live enables TalkBack on the device to allow for element-by-element UI navigation of the mobile website and spoken description of the UI being navigated.

In this guide, you learn about:

Supported Android devices

The following Android devices in Live support the ScreenReader feature:

Supported device Android OS version
Samsung Galaxy S22 Plus Android 12
Samsung Galaxy S22 Ultra Android 12
Samsung Galaxy S21 Android 12
Google Pixel 6 Android 12
Google Pixel 6 Pro Android 12

Enable and disable ScreenReader

  1. Log in to the Live dashboard.
  2. On the Live dashboard, select the device-browser combination to start your test session.
  3. In Screen Reader option on the Live toolbar:
    • Click the Enable ScreenReader checkbox to enable the ScreenReader option.
    • Click the Disable ScreenReader checkbox to disable the ScreenReader option.


Note: Ensure that audio is enabled on your system, to hear the spoken description being provided by TalkBack.
Protip: Click on the Android device screen on Live after enabling ScreenReader to ensure focus on it in case your keyboard shortcuts are not working.

Your website’s end-users accessing your mobile website on an Android device with TalkBack enabled would either navigate your website via using touch gestures or keyboard shortcuts on a Bluetooth keyboard. Navigation behavior on TalkBack (such as moving to the next or previous element or auto-reading from the start of the page) that can be undertaken with these two methods will be referred to using the term “TalkBack actions” from here on.

Both ways are essentially similar in that they undertake TalkBack actions on the device UI such as moving to the next or the previous element or activating/selecting the element in focus. It should make no difference to your website’s accessibility rating whether your end-user is using touch gestures or the bluetooth keyboard. Once you ensure your mobile website’s WCAG compliance with one, it should work with the other. Check the next section for further details.

For the ScreenReader feature on Android devices in Live, use the following keyboard shortcuts to trigger TalkBack actions:

TalkBack action MacOS keyboard layout shortcut Windows keyboard layout shortcut
Moving to previous/next item Command + (Left arrow / Right arrow) Ctrl + (Left arrow / right arrow)
Activate / open element Control + Opt + Space Ctrl + Space
Go back Esc Esc

The following is a video demo of the above actions using the shortcuts:


Note: While you do not hear audio in the video demos provided here, you should be able to when using the ScreenReader feature on Android devices in Live.

How to test for end users who use touch gestures on their phones

Any Android device can be seen to have two modes of behavior depending on the kind of action they generate when using touch gestures:

  1. During regular use.
  2. When TalkBack is turned on.

For example, during regular usage, a swipe left or swipe right gesture may trigger the following actions, depending on where you are on the device:

  1. Moves to the previous/next screen on the homepage.
  2. Move to the previous/next picture in a photo gallery.

When TalkBack is turned on however, the same swipe left or swipe right gesture may trigger a TalkBack action which is moving focus to the previous or the next UI element on the screen.

These two modes of UI actions/behaviour are referred to as regular mode and TalkBack mode respectively in this document.

However, even when using TalkBack with the ScreenReader feature in Live, touch gestures trigger regular mode actions and not TalkBack mode actions, as defined in the official TalkBack documentation page.

Regular-mode-like behavior on using left and right swipe gestures when TalkBack is enabled on Live

Then, how should you test your mobile website accessibility for end users who use touch gestures on Android phones with TalkBack enabled?

The answer is, you don’t have to. Simply ensure that your website is accessible via keyboard navigation on real devices in Live.

WCAG compliance and accessibility is for ensuring aspects such as:

  1. UI elements and controls on your website are reachable and in the correct order when traversed in linear order via touch gestures like swipe left/right, or corresponding keyboard shortcuts for moving to previous or next element.
  2. The description of UI elements and controls on your website is such that it makes sense to a user hearing them via the TalkBack audio readout.

Hence, it makes no difference to your website’s accessibility rating, whether the end user navigates the website via the keyboard, or by using touch gestures when TalkBack is enabled. This is because the underlying ordering of UI elements, their reachability, and their description remains the same. Ensuring that your website is accessible by testing with one mode (keyboard or touch gestures) would ensure that it is accessible even if the end user is using another mode.

Modify TalkBack settings

After you have TalkBack enabled on the Live device by enabling the ScreenReader feature, you can access and modify TalkBack settings as follows:

  1. On the Live toolbar, click Show Home Screen.
  2. Click Settings.
  3. On the Settings menu, click Accessibility.
  4. On the Accessibility menu, click Installed Apps.
  5. On the Installed Apps menu, click BSTalkback.
    The BSTalkback option is turned on when TalkBack is enabled.
  6. On the BSTalkback menu, click Settings to view or modify your TalkBack settings.

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Talk to an Expert