1. AccessibilityService is one of the most policy-sensitive APIs on Google Play: the platform allows it across a wide range of apps, but every app that uses it falls under the Permissions and APIs that access sensitive information policy, and misuse is one of the fastest routes to rejection or removal.
2. Set isAccessibilityTool=true in the service metadata ONLY if your app genuinely helps people with disabilities use their device or overcome challenges - only such services are eligible to declare themselves accessibility tools, and only they are exempt from the prominent-disclosure and consent requirement.
3. For every other legitimate use (the large majority), you must: (a) complete the accessibility declaration in Play Console under App content > Permissions and APIs and receive Google approval before release, (b) show a clear in-app disclosure explaining what data the service accesses and why, and (c) obtain affirmative user consent - accessibility-related functionality is not obvious to users, so disclosure is mandatory.
4. Strictly prohibited: any implementation that enables the app to autonomously initiate, plan, or execute actions or decisions (auto-clicking, self-driving UI flows, screen scraping used to power unrelated automation), plus using accessibility data for ad targeting or to circumvent user choices - violations lead to suspension or removal.
5. Since November 2021, any app targeting Android 12 or higher that uses the AccessibilityService API must complete the permission declaration form and receive Google Play approval before publishing; review of declared accessibility features has kept tightening through 2026, so declare only what your app actually does.
6. Platform headwind to plan for: Android is restricting accessibility access on high-security accounts (Advanced Protection Mode updates block non-essential apps from AccessibilityService) - genuine disability tools stay functional while automation and customization apps lose the API. If your app relies on accessibility for automation, architect a non-accessibility fallback now.
7. Compliance checklist: keep the declared use case narrow and matching your real code, read only the data the feature needs, never export accessibility data off-device or sell it, and re-test every release - one update that misuses the API can take the whole app down.