The Evinced Mobile SDKs integrate with common mobile testing frameworks to automatically detect accessibility issues. With the addition of a few lines of code to your existing tests, you can begin to analyze your entire application to understand how it can become more accessible. At the conclusion of the test(s), a rich and comprehensive HTML or JSON report is generated to track issues in any reporting tool.

Get Started

To get started, follow the relevant SDK documentation for installation instructions, API explanation, and tutorials. Also, make sure to obtain your APIKey as detailed below.

We are constantly working to expand our platform support. Can’t find an SDK to match your platform? Please contact us at

Supported Platforms

Appium Java SDKAndroid / iOS
Espresso / UIAutomator SDKAndroid
WebdriverIO SDK (Mobile)Android / iOS

Evinced APIKey

In order to use any of the Evinced Mobile SDKs you first need to create an Evinced account. Once your account is created, you will get your apiKey and a matching serviceAccountId. Initialize the SDK with these values it will validate access with Evinced servers when you run your tests. If an outbound internet connection is not available in your running environment - contact us at to get an offline APIKey.


Accessibility Scans

The Evinced Mobile SDKs provide you a helper class called EvincedEngine which acts as an entry point for the API for performing accessibility checks. There are two main use cases that this library aims to facilitate:

Instant scan

The instant scan allows you to immediately take an accessibility snapshot of your current application state and store the results. You control what comes next - you can choose to fail the test immediately or create a detailed report and move on to the next test.

Analyzing over time

For a more comprehensive view of your applications accessibility posture, you can instead consolidate a number of scans in a single report at the conclusion of your tests. Simply add the accessibilityAnalyze method to all of the pertinent points in your test where you want to collect accessibility data. Then, add a single point where you want to have the actual assertion. Complete HTML and JSON reports will then be generated containing all of the accumulated accessibility issues.