SkieWhy does Skie block third-party accessibility apps?
Accessibility services can read the screen, tap on a user's behalf and watch what is typed, so a rogue one could automate around the rules. Skie blocks third-party accessibility apps on managed devices, and it is on by default. Built-in system accessibility features keep working.
Android's accessibility framework is designed to help people who need it, such as screen readers and switch control. The same power makes it a popular route for misuse: an app granted an accessibility service can click through settings, dismiss prompts and read what appears on screen.
Skie restricts which accessibility services are permitted on the device, so that only system ones are allowed. A student cannot enable a downloaded app as an accessibility service, and an app that asks for the permission has no way to obtain it. This sits well alongside the install controls, since an unknown app should never get as far as asking.
The protection is on by default and appears as one switch in the hardening section. Its state is read back from Android after each apply and counted in the compliance score. If a student relies on assistive technology, the built-in tools on the device are not affected, and the admin can discuss the right setup for that individual group.
There is a practical side, too. Auto-clickers and macro apps work through accessibility. Blocking the route means they cannot be used to work around timers or to press through prompts.
Practical tip: if a student genuinely needs a third-party assistive app, add it to the allowed list for a specific group after checking it, rather than turning the whole protection off.