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 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
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
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.
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)
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.
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)
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.
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
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 : Play Console Help: Use of the AccessibilityService API.
Rather hand it over?
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
Related: Google Play prominent disclosure · Google Play SMS and Call Log permissions · Google Play QUERY_ALL_PACKAGES permission · Google Play target API level