Web content access guidelines (WCAG 2.1 Level AA) is internationally recognized standard for digital access. Completing these guidelines helps you to ensure that your website is usable by visual, motor, hearing and academic disorders.
Google Risk scanner There is a free app on Google Play that offers developers, designers, and product leaders’ ability to audit their app their app to findable issues. The app is designed to highlight leakage issues that may not meet the WCAG 2.1 level AA standards.
Once installed, the leak scanner allows you to take your app’s screenshots or video recording, then highlights areas that cannot meet the accessories, such as small contact goals, unlike low color, or content label labels.
Here’s what we will cover is:
How to download and qualify the Access Scanner
In five quick steps, you can download the accessable app and enable it on your Android device.
Find and download “Access Scanner” on the Google Play Store.
Find and open it downloaded app on your device.
On the bottom of the page, click on the “Turn On” button and turn on the leak scanner. It will take you to your access settings.
In the Leisure Setting page, click on the Leak Scanner button. It will take you to the accessible scanner settings.
Find and turn it on the Risk Scanner. (This will open a mood that asks if you allow the “Risk Scanner” to get full control over your device, click on the permission.
After the fifth step, you will have a blue checkmark icon that will appear on the right side of your screen (see the picture below). This floating icon provides you with quick access to QUICK to start scanning any screen for access issues.
How to use the Risk Scanner
To scan or record your app, tap the blue checkmark icon, to find access, access issues. After clicking the blue checkmark you will see some options:
Record: A short video of the user’s interactions captures and produces a report on leakage issues.
Snapshot: A steady screenshot and flags found on this screen take problems.
Turn off: Closes the access scanner.
Falling: Eliminates the options to display the initial blue checkmark.
You can choose between taking a single Snapshot Or recording the user’s flow using Record To evaluate multiple screens.
How to use Snap Shot feature
The Snap Shot button will take a snapshot of the page that you are currently present and will give you the result of leisure problems that can be on the page. Eligible leakage will be highlighted in red boxes.
The icon below is the result of taking a snapshot in the Facebook login page. The access scanner states that there are 10 capable leakage suggestions on this page only.
You can click on the main area to get more details of the potential access problem. For example, you can click on the Red Box highlighting the “mobile number or email” form in the above photo. Once you click on the feature area, you will get additional information.
The image below is the result of clicking on the “mobile number or email” form element. A capable access scanner is highlighting the mistakes found on this email form.
The first suggestion is that the item is to be fixed, as this item may not have the label to read by the screen readers. The second problem that is highlighted is the touch target and suggests that the target should be larger. Final advice unexpected text, potential text detected: mobile number or email.
Snap shots allow us to take screenshots of our pages and highlight access issues.
How to use the record feature
If you choose to record, you will take snap shots at the accessible scanner intervals while passing through the pages of your app. To remove the recording, tap the blue pause button (which replaces the original checkmark during recording).
Once you turn off the recording, the Risk Scanner will give you several snap shots and significant errors. The picture below is the result of recording Facebook login in Facebook log in less than a minute.
During the recording, I visited the other pages inside the app. The recording gave 5 snap shots of the pages that I was passing through. You can see snap shots on the page. In the picture below, I’m on one of the five screen. I can click on other snapshots under the words “Screen 1 of the 5” and see the problems of various snapshots taken during my recording. Like a Snapshot -accessible audit, you can click on red boxes and find more information about errors.
Why use access scanner?
A capable access scanner app is a valuable tool for teams in the development life cycle. Engineers can use this process locally at the early to scan, identify access issues, and resolve this process before release. During the QA phase, designers and product managers can use a scanner to audit the user interface and flag potential access concerns. Even after the preparation of an app, all teams can continue to use scanners to monitor and improve accessible.
But it is important to note that the leak scanner is just a part of the leisure strategy – this is not a complete alternative to manual testing or audit. And it will not find all kinds of access barriers – especially those who need keyboard navigation, screen reader testing, or scientific use reviews. But this is an easy and effective point to improve access to Android apps.
You should use other tools as well, such as Talkback of Android for Screen Reader Testing. Most importantly, the real -world feedback of people who uses auxiliary technologies is essential to identify obstacles that may lose automatic tools.
With just some taps, the leak scanner helps with surface problems that can otherwise lose. It is a free, lightweight and essential tool to build comprehensive mobile experiences.
Thank you for reading!
Now you should know how to start using Access access scanner to test your apps access and make sure they are worth the use of everyone.