The accessibility permission: the most powerful thing you can grant an app

Android deliberately makes this permission awkward to grant — a full-screen warning, buried in Settings, with no way for an app to request it inline. That friction is not a design oversight. It is the single most consequential switch on the device.

Why it exists

The Accessibility Service API was built so that screen readers, switch-access devices and voice control could operate a phone on behalf of someone who cannot touch it. To do that, a service must be able to read what is on screen and act on it. There is no way to build a screen reader without those two abilities.

Android has never added a narrower API for "let this app tap for me". So any app that needs to perform touches on your behalf — a remote control tool, an automation app, a macro recorder — has to go through the same door that was built for assistive technology, and inherits the same very broad powers.

What a service with this permission can actually do

• Read the content of every screen, as structured text. Not a picture — the actual text of buttons, labels, messages and fields, in every app.
• See what you type, because text fields are part of that structure.
• Perform taps, long presses, swipes and gestures anywhere on the device.
• Enter text into fields.
• Press system navigation — back, home, recents — and open the notification shade.
• Observe which app is in the foreground and react to it changing.
• Keep doing all of the above after a restart, until you explicitly revoke it.

There is no per-app scoping. A service granted accessibility for one purpose has it for the whole device. The system does not distinguish between the app it was granted for and your banking app.

The scam angle, in one paragraph

Every phone-based remote access scam is, functionally, an attempt to get this permission granted. The story varies — a bank, a courier, a support line, an investment app — and the destination never does: a real app, installed from a real store, with accessibility enabled. Once it is on, the caller does not need to ask you for a code, because they can read it on your screen. The full anatomy is in the call that asks you to install something.

Auditing your own phone

1. Open Settings → Accessibility. Depending on the manufacturer it may be under Additional settings or Advanced.
2. Find Installed services — sometimes called Downloaded apps or Downloaded services.
3. Read the list. Anything you do not recognise, or no longer use, should be off.
4. Turn off what you do not need. Nothing breaks except that app's ability to control the phone, which is the point.
5. Do this after any support call, without exception — including one you initiated.

Most people who look find at least one service left on from an app they stopped using months ago. That is not a compromise, but it is a standing capability with no current purpose, and it costs nothing to close.

When granting it is reasonable

It is a legitimate permission for legitimate tools, and refusing it categorically is not the lesson. Grant it when all of these are true:

• You initiated the installation, with nobody on the phone telling you to.
• Control is the app's actual purpose — a remote control tool, an automation app, an assistive tool. If an app wants it for something unrelated to acting on your behalf, that is a mismatch.
• You know how to turn it off, and you have looked at where the setting is before you needed it.
• The device is yours, or the person whose device it is understands what they agreed to.

More guides