Android accessibility services make phones usable for people with vision, hearing, mobility, and interaction needs. They also support legitimate features such as screen reading, voice control, automation, and—in some designs—password autofill. Because a service may observe screen content or perform actions, the enabled list deserves the same care as device administrator or VPN access.
Where to find the enabled services
Open Settings and tap Accessibility. On some phones, choose Installed apps, Downloaded apps, Installed services, or Advanced settings. The exact label varies by manufacturer and Android version. Settings search for “accessibility” or “installed services” is often faster. Separate built-in features such as TalkBack from downloaded apps, and note which entries say On.
Do not assume every item in the menu is currently active. Android may list available services even when their switch is off. Open each unfamiliar entry and check its status, package name, and description.
What accessibility access can allow
Depending on the service and permissions, an app may read interface text, observe which window is open, follow notifications, tap buttons, scroll, type, or place an accessibility shortcut on screen. Those abilities are necessary for many assistive tools. They are also attractive to fraud apps trying to capture credentials or approve actions. Android therefore shows a strong warning before activation.
Decide whether an enabled entry belongs there
Ask who enabled it, what feature depends on it, and whether that feature is still used. A screen reader selected by the owner has an obvious purpose. A reputable password manager may document accessibility as a fallback on older apps. A remote-support tool may need temporary control during a session. A QR scanner, wallpaper app, loan app, or unknown APK has a much harder case.
Check the app’s store page, developer site, privacy policy, and update history. Search for an official explanation of the accessibility feature rather than relying on a pop-up inside the app. If the app says the service must stay on to “improve speed” without explaining how, turn it off and test.
Disable access safely
- Open the app’s accessibility entry.
- Turn off “Use service,” “Allow,” or the corresponding switch.
- Confirm the warning.
- Return to the list and verify that it says Off.
- Open the app and test the feature you care about.
If you do not need the app, uninstall it after disabling the service. Turning off accessibility does not delete data the app previously collected. Use its account deletion controls when relevant.
If the switch will not stay off
Check whether the phone is managed by work, school, parental controls, or device policy. Review Device admin apps and installed management profiles. Restart and try again. If an unfamiliar app repeatedly re-enables control, disconnect from sensitive accounts, document the package and warnings, and use the manufacturer’s Safe Mode instructions to determine whether a third-party app is interfering.
Restricted settings and sideloaded apps
Recent Android versions may restrict sensitive settings for apps installed outside a trusted store. An app may instruct you to open its App info page and allow restricted settings. Do not bypass that protection merely to make a downloaded APK work. Confirm the publisher and source independently, understand why accessibility is essential, and prefer a verified distribution channel.
Check related powers at the same time
An accessibility audit is more useful when paired with Display over other apps, Notification access, Device admin, VPN, Usage access, and Install unknown apps. A combination of accessibility, overlays, and notification reading can create much greater exposure than any one setting. Record unfamiliar combinations before removing them.
Do not disable accessibility blindly
On a shared phone, an enabled service may be essential to another person. Disabling TalkBack, Switch Access, Live Transcribe, or a hearing tool without asking can make the device difficult or impossible for them to use. Confirm ownership and need first. Security work should not remove accessibility from the person it protects.
A short quarterly review
- List every service that is On.
- Explain the current purpose of each in one sentence.
- Remove temporary remote-support and automation access after use.
- Check whether the app is still installed, supported, and updated.
- Review related special access for the same package.
- Revisit after installing an APK or responding to a fraud warning.
The goal is not “zero accessibility services.” It is an enabled list that reflects deliberate needs. A legitimate service should have a clear benefit, a known developer, a narrow duration where possible, and an owner who understands why it is active.
A realistic example: temporary support that never got removed
Suppose a relative installed a remote-support app months ago and enabled its accessibility service during a troubleshooting call. The session ended, but the service stayed active. The app may be legitimate, yet the continuing access is no longer proportionate. Confirm that remote help is not scheduled, turn off the service, remove any overlay or notification access, and uninstall the support tool if it has no ongoing role. This is why an audit should focus on current need rather than trying to label every powerful app as malicious.
Questions to record before changing a shared phone
Ask whether anyone relies on the service for reading, hearing, switch control, automation, or work. Note how the feature is launched and how it can be restored. If disabling it changes navigation, do not leave the user stranded; re-enable the known service and seek help from the app developer or accessibility support. A short record makes the security decision reversible and respectful.
Official references
Google’s Android accessibility overview explains where accessibility features are managed. Pair it with Google’s permission guidance for the broader audit.