Android 17 Beta 2 restricts non-accessibility apps from using the accessibility services API when Advanced Protection Mode (AAPM) is active.
Verified accessibility apps marked with isAccessibilityTool=”true” are exempt from the restriction.
Change aims to curb malware misuse of the accessibility API (often used for data theft), which is intended for legitimate features like screen readers and voice input.
Apps that previously had accessibility permission will automatically lose it and users cannot grant it while AAPM is enabled.
Android 17 also introduces a new contacts picker for more granular data access (source: The Hacker News).
Read more about how Android 17 Beta 2 restricts non-accessibility apps on SC Media
Mobile accessibility tells half the story
September 8, 2026
I audited five public design systems. The one built for mobile, Material 3, hands designers accessibility as first-class properties. The web still treats the same
Mark SMiller is a digital accessibility consultant who helps organizations build accessible, inclusive digital experiences. He speaks regularly at industry conferences,, CSUN, CVENt and apperes on many webinars and podace. , He trains teams on practical, sustainable accessibility workflows.
Comments