@SupportGrapheneOS_667 That's for the Google account rather than Gmail specifically, and it has an impact on Android for the stock OS when logged into a Google account. Several of the Android Advanced Protection features are existing Google Advanced Protection features impacting Android including blocking installing apps from outside the Play Store.

It's possible to use other mail clients but they must implement the modern authentication support which likely requires using a WebView for this.

@J3317 @evilcookies98 @wmd eSpeak NG has restrictive GPLv3 licensing that's not appropriate for GrapheneOS. It also doesn't really meet the robustness or security requirements.

RHVoice doesn't implement Direct Boot support so it can't work Before First Unlock. A text-to-speech implementation can of course be installed on GrapheneOS.

We have our own fork of the open source TalkBack included but there hasn't been a text-to-speech app we can include yet and they also mostly require setup too.

@evilcookies98 @J3317 @wmd We won't bundle code with more restrictive licensing than GPLv2. It would limit GrapheneOS usage.

We haven't locked anything out. You can use eSpeak NG, RHVoice, Speech Recognition & Synthesis, etc. on GrapheneOS. Only Google's app could provide a good out-of-the-box experience anyway. Neither eSpeak NG or RHVoice is up to the task of providing a robust and usable implementation that's ready to go out-of-the-box for an easy initial setup for someone who depends on it.

@evilcookies98 @wmd @J3317 There are major issues with the open source options both in terms of robustness and usability along with overly restrictive licensing. Google's app is the only one which really meets the requirements but is a closed source implementation.

We've seen some newer apps in development without the same legacy baggage and may be able to include one of them soon. Including one of them does not mean a device will be usable by blind users after flashing/locking though.

@J3317 @evilcookies98 @wmd Direct boot aware apps can run in the time between system boot and first unlock. The app needs to be able to run without an access to (most) of its files, since these are encrypted and need unlocking.

I am not sure what exact implication this has for the usability of screen readers, since I haven't needed one.

@joepie91 @J3317 @evilcookies98 @darkyen There are better options than eSpeak NG with the permissive licensing we neeed. Regardless of the choice of the app to fork, there's work involved in forking it and integrating it to work seamlessly out-of-the-box without requiring any setup. There's further work to add TalkBack integration into Setup Wizard.

We're not to blame for a project choosing licensing which is broadly known to be something many companies want to avoid. That choice limits usage.