Hmm. I see a lot of people here responding that disabling this would break the Accessibility Services, and I completely agree. However, it does seem to me like

Hmm. I see a lot of people here responding that disabling this would break the Accessibility Services, and I completely agree. However, it does seem to me like there is a genuine problem here. Perhaps the solution is to have a two-layer accessibility permission system? One permission for reading the screen of non-inherently-sensitive applications, like web browsers and email clients, and another permission for reading high-sensitivity applications like Google Authenticator. Enabling the second permission would come with very strong warnings about security, and the admonition that you should really really trust this application provider a lot more than your average screen reader app.