3 ms·
But there's a lot more that goes into accessibility services. Redirecting all output to a single mono headphone is really important, and most users who use tal
by Klathmon 7y ago
But there's a lot more that goes into accessibility services.
Redirecting all output to a single mono headphone is really important, and most users who use talkback adjust the speed and how things are spoken to better suit them.
And it still doesn't solve the problem, as accessibility services can still tap into the audio output and run speech-to-text to get the codes back still accomplishing the same exact thing.
- tzs 7y agoOK, so the idea of having the authenticator app entirely handle its own accessibility might not solve the problem in the case of users that are actually using accessibility features. Or at least it would require some serious system level support [1]. But how about the first part of my suggestion, which was to have whether or not accessibility features are used in the authenticator app controlled by a setting in the app separate from the system wide settings? For people not needing accessibility, at least, and so have it off both system wide and in the authenticator app they would be protected. A rogue app getting system wide accessibility access would still not get access to the authenticator. [1] The system might have to support two independent sets of accessibility privileges and settings, one for most apps and one for security apps, with severe restrictions on what regular apps can do when a security app is running.