# Google Play: AccessibilityService API use not allowed or not declared
> Google Play rejected the app over the AccessibilityService API. Add the disclosure and declaration, or remove the service if the app is not a true tool.
Canonical: https://app369.com/fix/google-play-accessibility-service-api/
Last updated: 2026-11-09
The AccessibilityService API is a restricted Google Play API that needs a declaration in Play Console. Only apps built to help people with disabilities may set isAccessibilityTool; every other app needs a separate in-app disclosure and consent.
**Short answer**
Decide whether the app is an accessibility tool for people with disabilities. If it is, set isAccessibilityTool and complete the declaration with a video. If it isn’t, show a prominent disclosure and get consent before turning the service on, complete the declaration, and keep any automation narrow and rule-based. If the feature isn’t core, remove the service.
Rather not fix it yourself? [**App Fix Ticket**](https://app369.com/fixed-price/flutter-firebase-bug-fix/) starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
## **Why Play refuses the API, and the fix**
1. 01 ### **The app claims to be an accessibility tool**
> “The tools must support people with disabilities as their primary purpose.” [**Google Play Console Help, Use of the AccessibilityService API**](https://support.google.com/googleplay/android-developer/answer/10964491) General assistants and apps that serve a wide audience don’t qualify, even when some users with disabilities find them useful. Remove isAccessibilityTool and follow the disclosure route instead.
2. 02 ### **No prominent disclosure before consent**
> “Must require affirmative user action for consent (for example, tap to accept, or tick a check box);” [**Google Play Console Help, Use of the AccessibilityService API (prominent disclosure)**](https://support.google.com/googleplay/android-developer/answer/10964491) The disclosure must sit in the app, in normal use, stand apart from other disclosures, say why the app needs the service and how it is used, and need a tap to accept. Text in the privacy policy or terms alone is not enough.
3. 03 ### **The service acts on its own**
> “Any use of the Accessibility API that enables an app to autonomously initiate, plan, and execute actions or decisions is strictly prohibited.” [**Google Play Console Help, Use of the AccessibilityService API (automation)**](https://support.google.com/googleplay/android-developer/answer/10964491) Apps that are not verified accessibility tools can’t use this API for AI agents that plan and tap through other apps. Keep automation to fixed rules the user set, such as one trigger and one action.
4. 04 ### **The declaration is missing or out of date**
> “If you change how your app uses this API, you must submit the form again with updated and accurate information.” [**Google Play Console Help, Use of the AccessibilityService API**](https://support.google.com/googleplay/android-developer/answer/10964491) Also check: the declaration in Play Console must match what the current build does. Submit it again after any change to how the service is used.
Checked against the vendor’s docs on November 9, 2026: [Play Console Help: Use of the AccessibilityService API](https://support.google.com/googleplay/android-developer/answer/10964491).
## **Rather hand it over?**
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- [from $450**App Fix Ticket**One reproducible bug in an existing mobile or web app, diagnosed and fixed.**See scope and start**](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
[**All 127 Fiverr reviews**](https://app369.com/reviews/)
Related: [**Google Play prominent disclosure**](https://app369.com/fix/google-play-prominent-disclosure-consent/) · [**Google Play SMS and Call Log permissions**](https://app369.com/fix/google-play-sms-call-log-permissions/) · [**Google Play QUERY_ALL_PACKAGES permission**](https://app369.com/fix/google-play-query-all-packages-permission/) · [**Google Play target API level**](https://app369.com/fix/google-play-target-api-level-35/)
Questions
## **More on this launch**
**Does an accessibility tool need a disclosure? **+
No. Apps that correctly declare isAccessibilityTool are exempt from the prominent disclosure and consent requirement, but still need the declaration.
**What goes in the video? **+
For an accessibility tool: the app being opened, the service being turned on and the service in use, with captions or a voice-over if the use isn’t obvious. For any other app, show the prominent disclosure and the consent step in the recording too.
**Can you fix it for me? **+
If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.
Something else?
## **Describe it and get a written quote**
Describe the app and where it is in the launch. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.
[**Describe your problem **→](https://app369.com/contact/) [**All fixes**](https://app369.com/fix/)