Google Play accessibility API policy: fixes and checks

By The Draftbit team · Updated
Sources checked

This guide is for Google Play apps using AccessibilityService or related accessibility capabilities.

Accessibility access is powerful enough that Google restricts both its purpose and behavior. It can’t bypass platform privacy/security controls, make deceptive interface changes, or change settings without permission. The policy also prohibits remote call-audio recording and apps that autonomously initiate, plan, and execute actions or decisions through this API.

Inspect what the service can do

List events read and actions performed, including automation and account-sensitive screens. We’d compare the implementation with the narrower APIs available for the same task. Document permitted accessibility use in the store listing.

Correct the capability and declaration

Remove prohibited behavior and unnecessary access. Preventing uninstall or disabling has narrow parent/guardian and authorized enterprise-management exceptions. Check IsAccessibilityTool eligibility separately; setting that flag doesn’t authorize every use.

Test enablement, disclosure, refusal, and disabling the service. Give Google the actual user-facing task, declaration, and review demonstration. A broad statement that the feature helps users isn’t enough to establish compliance.

Messages this guide can help with

Accessibility API; Accessibility API policy violation; Accessibility API rejection; Accessibility API denied

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit a Google Play release with working review access