Google Play IsAccessibilityTool eligibility policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Google Play apps declaring themselves accessibility tools or using accessibility APIs for another purpose.
The IsAccessibilityTool flag is for apps whose core functionality directly supports people with disabilities. It isn’t a shortcut around disclosure requirements for ordinary automation.
Check the primary purpose
Compare the feature, target audience, listing, and service configuration. We’d explain the concrete assistance the app provides and test it with the relevant access settings.
Use the correct declaration
Remove the flag when the app isn’t eligible. Non-tool uses still need the required prominent disclosure and consent, and all uses must follow the Accessibility API restrictions. Prefer narrower APIs when they can perform the task.
Test the corrected configuration and consent flow in the submitted build. Give Google the app’s actual purpose and the steps to use the service. A change to the category label won’t turn an unrelated feature into an accessibility tool.
Messages this guide can help with
IsAccessibilityTool eligibility; IsAccessibilityTool eligibility policy violation; IsAccessibilityTool eligibility rejection; IsAccessibilityTool eligibility 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.
- Google Play: IsAccessibilityTool eligibility Checked 22 September 2026