Android 17 Advanced Protection locks down accessibility apps
Android 17 Advanced Protection limits accessibility services to verified Accessibility Tools. Who it protects, which apps lose access and what developers do.
Source-based. Written from the documents, reporting and reviews linked in the text. Nothing here was tested hands-on by The Ruling Desk. How we work
In Android 17, turning on Advanced Protection now cuts off accessibility services for every app that isn't a verified Accessibility Tool. Google announced the change on October 1, 2026, as one of six additions to Android 17 Advanced Protection, its opt-in security mode for people at higher risk of attack. Screen readers and other assistive apps keep working; automation tools, launchers, some security apps and other apps that borrow accessibility powers lose them while the mode is on.
Key takeaways
- Opt-in only: nothing changes unless you turn on Advanced Protection. It's one switch in Settings, and it needs a screen lock.
- What changes: in Android 17, Google says Advanced Protection restricts AccessibilityService access "exclusively to verified applications categorized as Accessibility Tools".
- Why: Google calls apps abusing that API "a primary vector" for fraud and scams. Banking trojans use it to read screens, fake login pages and tap through transfers.
- Who loses access: Google hasn't published a list. Its Play policy says automation tools, launchers, password managers, antivirus and cleaner apps can't claim to be accessibility tools. A customization app lost access in an Android 17 beta, and Bitdefender says some of its features stop.
- Developers: genuine assistive apps set the
isAccessibilityToolflag and meet Google Play's policy; everyone else should detect the mode and tell users what stops working.
What changed in Android 17 Advanced Protection
Advanced Protection arrived with Android 16 in 2025 as a single toggle that switches on Google's strictest settings at once. According to Google's help page, it keeps Google Play Protect on, blocks installs from unknown sources and blocks 2G networks on supported phones, among other things. The same page now lists a new line: it "restricts accessibility services to verified accessibility tools."
In its October 1 announcement, Google group product manager Il-Sung Lee explains that because accessibility services "are designed to interact directly with the screen", attackers can use them to read sensitive data, install malware or block you from uninstalling an app. In Android 17, turning on Advanced Protection limits that access to verified Accessibility Tools automatically. Google says all six new features reach Android 17 devices, except USB Protection and Failed Authentication Lock, which come to select Android 17 devices. If you already use the mode, Google says you'll get a notification when the new capabilities land on your phone.
The other five additions are Intrusion Logging (encrypted forensic logs kept for 12 months, a separate opt-in), USB Protection, WebGPU switched off in Chrome, Failed Authentication Lock and a page listing which apps check whether Advanced Protection is on.
What you see when an app is blocked
Android Authority first spotted the restriction in a February Canary build, with apps marked "Restricted by Advanced Protection". When it tested Android 17 Beta 2 on a Pixel 9a in March, the customization app dynamicSpot lost its accessibility permission as soon as the mode was on: Android revoked the existing grant and wouldn't let it be granted again. Google's announcement doesn't describe the message itself, so treat that wording as what testers saw in pre-release builds.
Why banking trojans abuse accessibility services
An accessibility service can read what's on the screen and act for you, which is exactly what a screen reader or a switch control needs. It's also what fraud malware wants. The Hacker News, reporting the change, notes that banking trojans and spyware have used the API to pull data, start fraudulent transfers, log keystrokes and show fake login screens.
A recent example: Cyble's researchers described OverlayPhantom in May 2026, a banking trojan that targets more than 180 banking, finance and crypto apps in 10 countries. Cyble says it uses the Accessibility Service to watch which app is open, intercept input, simulate taps and swipes, and draw overlays that collect your PIN, password or unlock pattern. It reached phones through a dropper posing as trusted apps such as ID Austria and TikTok.
The same idea, software driving apps through the accessibility layer, also powers legitimate automation, like GitHub Copilot's computer use on desktop. That dual use is the whole problem: the system can't tell a helper from a thief by behavior alone, so Google is gating it by who the app says it is and whether that claim is verified.
Which apps keep working and which may stop
Google's AccessibilityService policy for Google Play sets the line. Only services "designed to help people with disabilities" can declare themselves accessibility tools, and supporting people with disabilities has to be their primary purpose.
| Likely keeps access | Likely loses access with Advanced Protection on |
|---|---|
| Screen readers | Automation tools and assistants |
| Switch-based input for motor impairments | Launchers and customization apps |
| Voice-based input for motor impairments | Password managers that use accessibility |
| Braille-based access | Antivirus, cleaners and monitoring apps |
The right-hand column comes from the categories Google's policy says can't use the flag, not from a list of blocked apps, which Google hasn't published. One security vendor has already confirmed the effect: Bitdefender's support page says Web Protection, Chat Protection and App Anomaly Detection stop working under Android 17's Advanced Protection, with the accessibility setting greyed out. Bitdefender says users have to choose between the mode and those features while it looks for a fix.
What developers need to do
The flag already exists. The AccessibilityServiceInfo reference documents android:isAccessibilityTool, added in API level 31 (Android 12), declared in the service's metadata XML and false by default. Google notes the criteria "might be defined by the installer", which on Google Play means the policy above.
- If your app is a genuine assistive tool, set
android:isAccessibilityTool="true"and make sure your Play listing and purpose meet the policy. - If it isn't, don't set the flag to dodge the restriction; Play's policy forbids it. Instead, check the mode with
AdvancedProtectionManager, as Google's Advanced Protection Mode guide shows, and explain to users which features pause while it's on.
Bottom line
If you're a journalist, activist, public figure or anyone who wants the strictest Android settings, Android 17 Advanced Protection now closes one of the most abused doors on the platform, and your screen reader still works. The cost is that apps which lean on accessibility for convenience, from launchers to some security suites, stop doing that part of their job while it's on. Check your apps before you flip the switch, and for more on threats like this one, follow our cybersecurity coverage and the software section.
FAQ
How do I turn on Advanced Protection on Android?
Open Settings, tap Security & privacy, then Advanced Protection (on some phones it's under Google, then All services). Turn on Device protection and confirm. Google's help page says you need a screen lock first, and some phones ask you to restart.
Will TalkBack and other screen readers still work?
They should, as long as they're verified Accessibility Tools. Google says the change preserves "vital assistive technology", and screen readers are the first example in its Play policy of apps that qualify.
Can I turn Advanced Protection off if an app I need stops working?
Yes. It's a setting, not a one-way lock: go back to Security & privacy, then Advanced Protection, and turn off Device protection. Bitdefender gives the same steps for users who want its accessibility-based features back.