How to implement Android Accessibility Part 2 — How to install Android Accessibility Suite in the emulator
Hi, this is the second part of Android Accessibility. If you haven’t read the first article, you can find the links at the end of that article.
Today I will talk a bit about how to install Android Accessibility Suite on the emulator (https://play.google.com/store/apps/details?id=com.google.android.marvin.talkback&hl=pt_PT&gl=US)
We will focus on Talkback, which doesn’t come by default on the emulator.
There are three ways to do it:
1 — you can download the version on your computer and drag it into the emulator
2 — install directly through the play store
3 — You can download the base code from Google’s Github and do it yourself. (I won’t demonstrate. Mainly used when you need to modify something in the Android Accessibility Suite)
Initially, we need to create an emulator with Google Play.
Drag & Drop
First, we need to download the APK. There are a few ways to do it. But find below a direct link to the Android Accessibility Suite version 8.2 (version when I wrote this article). I always suggest downloading the most recent version.
Play Store
Follows the steps when you click on Play Store App. You need to register a new device (in this case, our emulator).
When you turn on Talkback for the first time, it will start a very intuitive “How to Use.”
Something nice is “Display Speech Output,” which appears as a text with everything the Talkback speech. This is practically an indispensable resource for testing. However, sometimes Talkback doesn’t speak in the emulator, which solves the problem.
Basic Commands
There are three basic commands:
• Move your finger from left to right -> will go to the next item on the screen,
• Move your finger from right to left -> will go back to the previous item,
• Double tap on any part of the screen -> select or click a button
That’s it, guys.
We’ll have more cool stuff in the following article.
0 — Introduction to mobile accessibility
1 —This article — H̴o̴w̴ ̴t̴o̴ ̴i̴n̴s̴t̴a̴l̴l̴ ̴t̴h̴e̴ ̴a̴c̴c̴e̴s̴s̴i̴b̴i̴l̴i̴t̴y̴ ̴f̴e̴a̴t̴u̴r̴e̴ ̴i̴n̴ ̴t̴h̴e̴ ̴e̴m̴u̴l̴a̴t̴o̴r̴ ̴(̴w̴h̴i̴c̴h̴ ̴d̴o̴e̴s̴n̴’̴t̴ ̴c̴o̴m̴e̴ ̴b̴y̴ ̴d̴e̴f̴a̴u̴l̴t̴)̴
2 — What is the correct way to build buttons. (It seems to be a silly and straightforward theme, but there are some details that we don’t take care of in the construction of our screens)
3 — Lists and why not use the build manual with Viewgroups (This can become a nightmare for those who need accessibility if not built correctly)
4 — Automated tests for accessibility (I have no idea how to do it, but I will study)
5 — Jetpack Compose with accessibility (same as item 4)
