Accessibility vs Usage Access: Which Permission Does a Screen Time App Need?

What each permission is for

Usage Access is the permission behind Android's app usage statistics. It exposes which app came to the front, which went to the back, and when. That is the data Digital Wellbeing uses to show your daily totals. It carries no screen content at all; here is exactly what it contains.

Accessibility exists so that screen readers, switch controls and voice access can work. To read a screen aloud, a service has to see the text on it. To let someone control the phone with a switch, it has to press buttons in other apps. So by design an Accessibility service can read on-screen text, see what you type into most fields, and perform taps and gestures for you, in any app.

	Usage Access	Accessibility
Which app is open	Yes	Yes
Text on your screen	No	Yes
What you type	No	In most fields
Tap buttons in other apps	No	Yes
Which part of an app you are in, such as Reels	No	Yes
Notice an app opening instantly	Within a second or so	Instantly
Blocked for sideloaded apps on Android 13 and up	No	Yes, behind "Allow restricted settings"
Revoked by Advanced Protection	No	Yes, for apps that are not accessibility tools

Why so many screen time apps use Accessibility anyway

It is not always bad faith. Accessibility solves three real problems for app blockers.

• Speed. Accessibility pushes an event the instant the window changes. An app using Usage Access has to check, so it notices a second or so later. For a blocker that wants to stop the app before you see anything, that gap matters.
• Reaching inside apps. Blocking Reels but keeping Instagram DMs, or hiding YouTube Shorts, requires knowing which screen of the app is showing. Only Accessibility can see that. Every Reels and Shorts blocker on Android relies on it.
• Acting on the app. Pressing Back or Home for you when a limit is reached is an Accessibility action.

Popular apps split along these lines. Opal's Play Store listing says it uses the Accessibility service on Android 14 and up to manage the apps on your block list. Pause-before-opening apps such as one sec intercept launches through Accessibility too. Doom Saver does not use it: it only needs to know which app is open, so Usage Access is enough.

What you give up by granting Accessibility

An Accessibility service can technically read your banking app, your messages and your passwords as you type them, in fields that do not mask input. A well-behaved app ignores all of that. But you are trusting the app, its future updates, and whoever might buy the company later, with that capability.

This is why Google keeps tightening the rules:

• Android 13 blocks Accessibility for apps installed from outside an app store until you explicitly choose Allow restricted settings (XDA).
• Google Play requires apps that use Accessibility for anything other than helping people with disabilities to disclose it prominently and justify it (Play policy).
• Advanced Protection, Google's high-security mode introduced with Android 16, now revokes Accessibility from every app that is not a genuine accessibility tool such as a screen reader, starting with Android 17 (Android Authority). A screen time app built on Accessibility simply stops working in that mode. One built on Usage Access keeps going.

How to choose

Ask what you actually want the app to do.

• See your time and get nudged while you are in an app: Usage Access is enough. Prefer apps that do not ask for more.
• Pause before an app opens, instantly: Accessibility is the practical route. Android 17's Pause Point will do this natively without any third-party permission.
• Block parts of an app, like Reels or Shorts: only Accessibility can do it. Pick one app for this job, from a developer you trust, and do not stack several.

Whatever you choose, read the disclosure screen an app shows before you grant Accessibility. If it cannot explain in a sentence or two what it reads and why, that is your answer.

How to see which apps have Accessibility

Open Settings, then Accessibility. On Pixel and most phones the apps are listed under Downloaded apps; on Samsung, under Installed apps. Anything turned on there can read your screen. Tap it to switch it off. The list should be short, and you should recognise every item on it. For the Usage Access list, see is Usage Access safe.

Common questions

Does a screen time app need Accessibility permission?

Not to track time. Knowing which app is open only needs Usage Access. Accessibility is only required for features that reach inside other apps, such as blocking the Reels tab, or for stopping an app the instant it opens.

Is Accessibility permission dangerous?

It is the most powerful permission a normal app can hold. It can read text on screen, see much of what you type and tap buttons in other apps. It is safe in the hands of a trustworthy app, but it is also the permission Android malware abuses most, which is why Google keeps restricting it.

Why does my screen time app stop working in Advanced Protection mode?

Advanced Protection revokes Accessibility from every app that is not a genuine accessibility tool, such as a screen reader. Screen time apps that depend on Accessibility lose it. Apps that use only Usage Access are not affected.

Why is Accessibility greyed out with a "Restricted setting" message?

Android 13 and later block Accessibility for apps installed from outside an app store. Go to Settings, Apps, the app, open the menu in the corner and choose Allow restricted settings, but only if you trust where the app came from.

Which is more private, Usage Access or Accessibility?

Usage Access, by a wide margin. It exposes which apps you use and when. Accessibility can expose the content of those apps.