Use Accessibility Service Consent

Last updated October 6, 2024 by Appdome

Learn to Initialize User Accessibility Service Consent in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

Why is Accessibility Service Consent Necessary?

Accessibility Services run in the background and receive callbacks from the system when accessibility events, such as clicking a button or changing focus, are triggered. In response to a callback, an accessibility service can request the capability needed to query the contents of the active window. As allowing an app to take full control of a user’s device can result in considerable damage, if that app is malware, Appdome enables displaying a message (dialog box) that prompts the user to consent to allow the relevant accessibility services to track, use, modify, and perform gestures for you in this app.

Why Should I Enable the Use Accessibility Service Consent Dialog Box?

You are advised to enable this dialog box to minimize the impact that the prevention of Accessibility Service Malware has on app usage.

When only trusted accessibility services are running no enforcements will be triggered, and therefore end users will not experience any impact on app usage. Threat data will still be collected and visible on ThreatScope. When enabling User Accessibility Service Consent in addition to this protection, the end user will not be prompted to provide consent for trusted services.

Prerequisites for Using User Accessibility Service Consent:

To use Appdome’s mobile app security build system to Initialize User Accessibility Service Consent , you’ll need:

Initialize User Accessibility Service Consent on Android apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Android Apps that Initialize User Accessibility Service Consent without an SDK or gateway:

  1. Upload the Mobile App to Appdome.

    1. Upload an app to Appdome’s Mobile App Security Build System

    2. Upload Method: Appdome Console or DEV-API
    3. Android Formats: .apk or .aab
    4. User Accessibility Service Consent Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
  2. Build the feature: User Accessibility Service Consent.

    1. Building User Accessibility Service Consent by using Appdome’s DEV-API:

      1. Create and name the Fusion Set (security template) that will contain the User Accessibility Service Consent feature as shown below:
      2. fusion set that contains User Accessibility Service Consent

        Figure 1: Fusion Set that will contain the User Accessibility Service Consent feature
        Note: Naming the Fusion Set to correspond to the protection(s) selected is for illustration purposes only (not required).

      3. Follow the steps in Sections 2.2.1-2.2.2 of this article, Building the User Accessibility Service Consent feature via Appdome Console, to add the User Accessibility Service Consent feature to this Fusion Set.

      4. Open the Fusion Set Detail Summary by clicking the “...” symbol on the far-right corner of the Fusion Set. Copy the Fusion Set ID from the Fusion Set Detail Summary (as shown below): fusion Set Detail Summary image

        Figure 2: Fusion Set Detail Summary
        Note: Annotating the Fusion Set to identify the protection(s) selected is optional only (not mandatory).

      5. Follow the instructions below to use the Fusion Set ID inside any standard mobile DevOps or CI/CD toolkit like Bitrise, App Center, Jenkins, Travis, Team City, Circle CI or other system:
        1. Build an API for the app – for instructions, see the tasks under Appdome API Reference Guide
        2. Look for sample APIs in Appdome’s GitHub Repository
    2. Building the User Accessibility Service Consent feature via Appdome Console

      To build the User Accessibility Service Consent protection by using Appdome Console, follow the instructions below.

      1. Where: Inside the Appdome Console, go to Build > Anti Fraud Tab > Mobile Malware Prevention section.
      2. How: Check whether is toggled On (enabled), otherwise enable it . The feature User Accessibility Service Consent is enabled by default, as shown below. Toggle (turn ON) User Accessibility Service Consent, as shown below. User Accessibility Service Consent option

        Figure 3: Initialize User Accessibility Service Consent option

      3. When you select the User Accessibility Service Consent you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains User Accessibility Service Consent

        Fusion Set applied User Accessibility Service Consent

        Figure 4: Fusion Set that displays the newly added User Accessibility Service Consent protection

      4. Click Build My App at the bottom of the Build Workflow (shown in Figure 3).
    Congratulations!  The User Accessibility Service Consent protection is now added to the mobile app
  3. Certify the User Accessibility Service Consent feature in Android Apps

    After building User Accessibility Service Consent, Appdome generates a Certified Secure™ certificate to guarantee that the User Accessibility Service Consent protection has been added and is protecting the app. To verify that the User Accessibility Service Consent protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below: User Accessibility Service Consent shown in Certificate secure

    Figure 5: Certified Secure™ certificate

    Each Certified Secure™ certificate provides DevOps and DevSecOps organizations the entire workflow summary, audit trail of each build, and proof of protection that User Accessibility Service Consent has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that User Accessibility Service Consent and other mobile app security features are in each build of the mobile app

Using Threat-Events™ for User Accessibility Service Consent Intelligence and Control in Android Apps

Appdome Threat-Events™ provides consumable in-app mobile app attack intelligence and defense control when User Accessibility Service Consent is detected. To consume and use Threat-Events™ for User Accessibility Service Consent in Android Apps, use registerReceiver in the Application OnCreate, and the code samples for Threat-Events™ for User Accessibility Service Consent shown below.

The specifications and options for Threat-Events™ for User Accessibility Service Consent are:

Threat-Event™ Elements Initialize User Accessibility Service Consent Method Detail
Appdome Feature Name User Accessibility Service Consent
Threat-Event Mode
OFF, IN-APP DEFENSE Appdome detects, defends and notifies user (standard OS dialog) using customizable messaging.
ON, IN-APP DETECTION Appdome detects the attack or threat and passes the event in a standard format to the app for processing (app chooses how and when to enforce).
ON, IN-APP DEFENSE Uses Appdome Enforce mode for any attack or threat and passes the event in a standard format to the app for processing (gather intel on attacks and threats without losing any protection).
Certified Secure™ Threat Event Check x
Visible in ThreatScope™ x
Developer Parameters for Initializing User Accessibility Service Consent Threat-Event™
Threat-Event NAME
Threat-Event DATA reasonData
Threat-Event CODE reasonCode
Threat-Event REF
Threat-Event SCORE
currentThreatEventScore Current Threat-Event score
threatEventsScore Total Threat-events score
Threat-Event Context Keys
message Message displayed for the user on event
failSafeEnforce Timed enforcement against the identified threat
externalID The external ID of the event which can be listened via Threat Events
osVersion OS version of the current device
deviceModel Current device model
deviceManufacturer The manufacturer of the current device
fusedAppToken The task ID of the Appdome fusion of the currently running app
kernelInfo Info about the kernel: system name, node name, release, version and machine.
carrierPlmn PLMN of the device. Only available for Android devices.
deviceID Current device ID
reasonCode Reason code of the occurred event
buildDate Appdome fusion date of the current application
devicePlatform OS name of the current device
carrierName Carrier name of the current device. Only available for Android.
updatedOSVersion Is the OS version up to date
deviceBrand Brand of the device
deviceBoard Board of the device
buildUser Build user
buildHost Build host
sdkVersion Sdk version
timeZone Time zone
deviceFaceDown Is the device face down
locationLong Location longitude conditioned by location permission
locationLat Location latitude conditioned by location permission
locationState Location state conditioned by location permission
wifiSsid Wifi SSID
wifiSsidPermissionStatus Wifi SSID permission status

With Threat-Events™ enabled (turned ON), Android developers can get detailed attack intelligence and granular defense control in Android applications and create amazing user experiences for all mobile end users when User Accessibility Service Consent is detected.

The following is a code sample for native Android apps, which uses all values in the specification above for User Accessibility Service Consent:


Using Appdome, there are no development or coding prerequisites to build secured Android Apps by using User Accessibility Service Consent. There is no SDK and no library to code or implement in the app and no gateway to deploy in your network. All protections are built into each app and the resulting app is self-defending and self-protecting.

Releasing and Publishing Mobile Apps with User Accessibility Service Consent

After successfully securing your app by using Appdome, there are several available options to complete your project, depending on your app lifecycle or workflow. These include:

Related Articles:

How Do I Learn More?

If you have any questions, please send them our way at support.appdome.com or via the chat window on the Appdome platform.

Thank you!

Thanks for visiting Appdome! Our mission is to secure every app on the planet by making mobile app security easy. We hope we’re living up to the mission with your project.

Want a Demo?

Android Malware Detection

TomWe're here to help
We'll get back to you in 24 hours to schedule your demo.