FAQ for Accessibility Insights for Android

If you don't see an answer to your question here, check out Help and Release notes.

Can all Android apps be tested using Accessibility Insights for Android?

All native Android apps can (and should!) be tested using Accessibility Insights for Android. You can even test apps created with cross-platform frameworks such as React Native or Xamarin.

Can I test an Android web application using Accessibility Insights for Android?

Accessibility Insights for Android can be used to test Android web applications; however, using web standards and rules will provide more actionable results. For that reason, we recommend using Accessibility Insights for Web to test web applications.

To run automated checks on an Android web application:

  1. Install Accessibility Insights for Web on your desktop browser.
  2. Open your web application in the browser.
  3. Use the browser's device emulation to simulate a mobile viewport.
  4. Open Accessibility Insights for Web and select FastPass.

Because web attributes sometimes work differently in Android applications, we also recommend testing with a screen reader.

What kinds of issues can be detected by automated checks?

Automated checks can detect some common accessibility issues, such as low contrast, missing names, or inadequate touch target sizes. The rules are based on axe-android, an open source accessibility rules library developed by Deque Systems.

Can automated checks detect issues in content that's currently hidden?

The automated checks run only on visible content; content with android:visibility="gone" or "invisible" is ignored.

To test content that's hidden by default – such as combo box options, dialog boxes, and menu options – you'll need to reveal the content before running automated checks:

  1. Use touch, mouse, or keyboard commands to reveal the hidden content.
  2. Run the automated checks.

Can automated checks detect issues in content that’s currently offscreen

Automated checks run on whatever elements are currently in the AccessibilityNodeInfo hierarchy. Because Android minimizes the number of objects in memory, elements that are currently scrolled offscreen might not be in the AccessibilityNodeInfo hierarchy. To test offscreen elements, you’ll need to scroll them into view and run automated checks again.

Can I aggregate automated check results from multiple screens?

Test results can't be aggregated across multiple screens.

Can I save or share automated check results?

At this time, results can't be shared or saved. We hope to support saving and sharing soon.

Can I run automated checks through scripting?

At this time, automated checks must be run manually through the Accessibility Insights for Android app.

Can I use appimaged or AppImageLauncher?

Both appimaged and AppImageLauncher can be used with Accessibility Insights for Android. However, if you use AppImageLauncher, an issue in Electron will prevent automatic updates.

What are the Android APIs supported by the Accessibility Insights for Android Service?

Currently, the Accessibility Insights for Android Service supports Android 7 (API 24) and greater.