Fortunately, Google is now temporarily suspending the ban and taking a step back to re-evaluate its requirements for apps that can make “responsible and innovative” use of accessibility features. Android Police reports that the company has started reaching out to affected developers who contacted Google when the ban was imposed last month. Here’s an excerpt from an email sent out to one such developer:
In the case of LastPass, the password manager used Accessibility Services not only to automatically fill passwords with App Fill, but to also conveniently manage links that the user has copied via Clipboard Actions. And although the repercussions for LastPass users were not immediate, the long-term solution for the popular password manager would likely be to make use of the new autofill API that’s built into Android 8.0 Oreo, rather than relying on Accessibility Services. On the other hand, since no API counterpart exists to Clipboard Actions, the developer could make the case that LastPass needs Acessibility access in order to be able to deliver its full functionality to users.
Google’s decision to more closely regulate apps that tap into Android’s Accessibility Services is a good one, as it aims to prevent possible security breaches, but seeing as how there are many apps out there that use the Accessibility API to enrich user experience, albeit not necessarily by utilizing the API in the intended way, a complete crack down on such apps would not have been beneficial for anyone – Google, developers, or end users. We don’t know when Google will be ready with re-evaluating its guidelines and impose a revised ban.
News credit : Phonearena