Block Passively Accessibility Readers

Last updated September 15, 2024 by Appdome

Learn to Block Passively Accessibility Readers in Android apps, in mobile CI/CD with a Data-Driven DevSecOps™ build system.

What are Accessibility Readers?

Accessibility readers are tools designed to help users with disabilities by reading out screen content aloud. However, these tools can potentially be exploited to access sensitive information displayed on the screen without user consent.

How Does Blocking Passively Accessibility Readers Protect Mobile Apps?

Appdome blocks accessibility services from passively reading or extracting content from the app’s components. This enhancement ensures that sensitive information within the app remains protected from unauthorized access by accessibility services. By restricting this capability, the feature strengthens the app’s overall security posture, particularly in scenarios where accessibility services might be misused to harvest user data.

Prerequisites for Using Block Passively Accessibility Readers:

To use Appdome’s mobile app security build system to Block Passively Accessibility Readers , you’ll need:

Block Passively Accessibility Readers on Android apps using Appdome

On Appdome, follow these 3 simple steps to create self-defending Android Apps that Block Passively Accessibility Readers 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. Block Passively Accessibility Readers Compatible With: Java, JS, C++, C#, Kotlin, Flutter, React Native, Unity, Xamarin, Cordova and other Android apps
  2. Build the feature: Block Passively Accessibility Readers.

    1. Building Block Passively Accessibility Readers by using Appdome’s DEV-API:

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

        Figure 1: Fusion Set that will contain the Block Passively Accessibility Readers 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 Block Passively Accessibility Readers feature via Appdome Console, to add the Block Passively Accessibility Readers 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 Block Passively Accessibility Readers feature via Appdome Console

      To build the Block Passively Accessibility Readers 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. When you enable Accessibility Service Abuse you'll notice that your Fusion Set you created in step 2.1.1 now bears the icon of the protection category that contains Block Passively Accessibility Readers

        Fusion Set applied Block Passively Accessibility Readers

        Figure 4: Fusion Set that displays the newly added Block Passively Accessibility Readers protection

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

    After building Block Passively Accessibility Readers, Appdome generates a Certified Secure™ certificate to guarantee that the Block Passively Accessibility Readers protection has been added and is protecting the app. To verify that the Block Passively Accessibility Readers protection has been added to the mobile app, locate the protection in the Certified Secure™ certificate as shown below: Block Passively Accessibility Readers 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 Block Passively Accessibility Readers has been added to each Android app. Certified Secure provides instant and in-line DevSecOps compliance certification that Block Passively Accessibility Readers and other mobile app security features are in each build of the mobile app

Using Threat-Events™ for Passively Accessibility Readers Intelligence and Control in Android Apps

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

The specifications and options for Threat-Events™ for Passively Accessibility Readers are:

Threat-Event™ Elements Block Passively Accessibility Readers Method Detail
Appdome Feature Name Block Passively Accessibility Readers
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 Blocking Passively Accessibility Readers 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 Passively Accessibility Readers is detected.

The following is a code sample for native Android apps, which uses all values in the specification above for Block Passively Accessibility Readers:


Using Appdome, there are no development or coding prerequisites to build secured Android Apps by using Block Passively Accessibility Readers. 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 Block Passively Accessibility Readers

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 to Set Trusted Accessibility Services

How to Detect Accessibility Service Abuse in Android Apps

How to Detect Unlocked Bootloader in Android Apps

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

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