Welcome to the Android Ally main page!
The tools are two-fold: The Android Ally and TalkBack for Developers.
Watch the YouTube introduction
The Android Ally is a desktop software companion to enable testers and developers faster access to Android device accessibility features. The core goal is to simplify and encourage Android Accessibility testing. It also works on emulators, which have been problematic because of the nature of the gestures that TalkBack uses.
The way that the software operates is by reading and writing values to the device settings through the Android Debug Bridge (ADB). On some devices, this may result in some unexpected behavior. Use at your own risk. Please read more about these commands from within the help menu. The Android Ally also has an optional Android accessibility service called TalkBack for Developers.
TalkBack is the open source native screen reader for Android. The two most popular versions are the base version from Google and the fork modified by Samsung. TalkBack for developers (TB4D) is a customized version of Google's TalkBack that allows developers to use adb commands for more fine-grained control of TalkBack. The core function is to allow developers to interact with TalkBack without having to learn complicated shortcuts and gestures.
TalkBack for Developers (TB4D) allows for developer and tester oriented features whose goal is to speed up the development process. All TalkBack settings can be adjusted from the Android Debug Bridge (ADB) rather than having to navigate complex preference screens, which become even more difficult when TalkBack is active. Examples of the additional features include using the ADB to control TB4D:
- navigate to the previous heading
adb shell am broadcast -a com.a11y.adb.previous -e mode headings
- navigate to the next heading
adb shell am broadcast -a com.a11y.adb.next -e mode headings
TalkBack for developers comes bundled inside the Android Ally, and can be installed from the UI. If you want to side load it yourself, you may download the phone APK or the wear APK.
- Simple installation on devices and emulators (emulators with Google API's are preferred)
- Complex navigation beyond simple tabbing
- Open the TalkBack menu with a button click
- Allow faster testing of custom actions
- Open TalkBack settings quickly
Android accessibility is difficult for a number of reasons:
- Design and QA communication can sometimes be hard to effectively diagnose
- Accessibility training is difficult find, and finding time can be problematic as well
- Accessibility documentation is always separate from core documentation - and in most example code, not present
- Businesses do not understand usability / accessibility as a priority
- Settings are scattered all over the system, and are modified in different ways
- night mode has a useful
cmdcommand alternative which is immediate, unlike using the (more well known, but not by much) settings API - color inversion is direct and immediate, color correction needs to be enabled and then changed
- animations have 3 different values that users can only toggle with one control, even though they can scale internally
- night mode has a useful
- All assistive tech is user-first, with little to no considerations for the developers who need to implement features for it
- Assistive tech is difficult to use while debugging
- Assistive tech is difficult to learn in the context of getting the whole job done
- Changing settings takes a long time, and even doing it by ADB doesn't always refresh immediately
- The people most negatively impacted by engineers not being able to use accessibility tools are the users
- A Java Runtime Environment
- The Android Debug Bridge (ADB):
- installed on your computer
- set up as a path variable (Mac) or as an environment variable (Windows)
- Enable the Android Debug Bridge (ADB) on your phone
- Google API's are recommended for emulators
Download the relevant package and unzip the installer.
If you intend to control TalkBack with the on screen controls, you will need to install TalkBack for Developers - this can be done from the Android Ally
- Open the DMG file and accept the license terms
- Drag the App into your applications directory
- From Applications, double click the app - it will tell you it's from an unverified developer. Select Cancel.
- From Applications, right click the app and choose open, then select open from the dialog. You should only need to do this once
Issues will be handled at the discretion of the creator. It is highly recommended in the creation of an issue that you include:
- The version of the Android Ally
- Device information
- Manufacturer:
adb shell getprop ro.product.manufacturer - Model:
adb shell getprop ro.product.model - Version:
adb shell getprop ro.build.version.release - SDK level:
adb shell getprop ro.build.version.sdk - User list:
adb shell pm list users - Check if "Disable permission monitoring" is enabled in developer settings (it needs to be on)
- Steps to reproduce
- Expected behavior
- Actual behavior