Restrict abuse: Google Android 17 Beta 2 supports strict restrictions on accessibility API calls

Tech News 3/13: Android Authority today (March 13) published a blog post reporting that in the Android 17 Beta 2 update, Google has enabled a stricter Advanced Protection Mode, which directly blocks non-official accessibility tool applications from calling the AccessibilityService API.

Note from IT Home: The AccessibilityService API is an accessibility service interface in the Android system, supporting applications to read screen content and simulate user operations. It is often used by third-party tools to implement automation or customized functions.

The original intention of the AccessibilityService API is to help people with disabilities interact better with devices, such as reading out current screen content or assisting with related tasks.

However, these powerful features can also be easily abused. Applications with accessibility access can not only view screen content and monitor user interactions but also automatically perform gesture operations.

Many automation tools, customization software, monitoring applications, and even some third-party desktops utilize this API to bypass the native restrictions of the Android system. To close this security loophole, Google has decided to tighten permissions under Advanced Protection Mode.

Under the new mechanism in Android 17 Beta 2, once users enable Advanced Protection Mode, the system will completely prohibit applications that are not officially classified as accessibility tools from obtaining accessibility permissions.

If a non-accessibility application has previously been granted this permission, the system will automatically revoke it; during this mode, users cannot manually grant permissions to these applications.

For example, on a Pixel 9a running Android 17 Beta 2 with Advanced Protection Mode enabled, the dynamicSpot application used to simulate the “Dynamic Island” feature will be unable to obtain the accessibility permission required to display floating windows.

According to Google’s official support page, applications that correctly declare themselves as accessibility tools (such as screen readers or voice assistance services) will not be affected by this adjustment.