Collective Appeal from the Blind Community: Google TTS Needs Action, Not Just Acknowledgment. This is a comprehensive public report on "Speech Services by Google" (Google TTS). We are posting this publicly because these issues are not new. They have been reported by multiple users over a long period, and many have already been accepted by your teams through standard feedback channels. We do not need to "DM for details" or "provide audio recordings." We need these long-standing issues and accepted feature requests to be fixed and implemented. The post is clear to avoid any confusion: PART 1: ACKNOWLEDGED FEATURE REQUESTS (NOT IMPLEMENTED) 1. User Dictionary: We still have no ability to create a user dictionary to fix custom pronunciations (e.g., for names or technical words). 2. Uninstall Default Voices: We still cannot uninstall the default English (US) voice pack, which wastes storage and clutters the menu. 3. Number Processing: We still have no feature to choose how numbers are read. The default "millions, billions" format is annoying, and we need options (like digit-by-digit). 4. Date Processing: We still have no feature to customize date formats. We need to be able to set regional standards (e.g., DD/MM/YYYY for India). PART 2: LONG-STANDING BUGS (NOT FIXED) 1. "Zero" Pronunciation Bug: The digit "0" is still incorrectly read as the letter "O" (e.g., "one O five" instead of "one zero five"). This affects all English variants (US, UK, IN, AU, NG). 2. Poor Audio Quality: The voices are not "clear, crisp, and crystal." They are muffled and sound nasally, "like somebody is speaking in the nose." 3. High Latency (Accessibility Failure): The TTS has "huge latency" and is "sluggish." This makes accessibility services like Explore by Touch (TalkBack) "pathetic" and unusable. The "quick responsive" feedback needed for scrolling and swiping is completely absent. 4. No Expressiveness: The engine ignores punctuation. A sentence ending in a question mark (?) is read with the same flat, declarative tone as a period, failing to convey intent. 5. Broken Auto-Language Switching: The auto-language detection "is not working properly." When it does try to switch, it introduces a "huge delay" that disrupts the flow of reading. 6. Incorrect Voice Switching: The system ignores the user's selected "desire voice." For example, a user sets Voice A for English and Voice B for a regional language. When reading, the system will suddenly use a random Voice C for the regional language, creating inconsistency and confusion. 7. Unsolicited Voice Downloads: Google TTS is still automatically downloading unnecessary voices that the user never requested. Even after being manually uninstalled, the system forcibly re-downloads them, wasting data and storage against the user's explicit wishes. These are not new reports requiring investigation. They are well-documented failures requiring action. We request escalation and a timeline for these fixes. @Google @GoogleAccess @Android @sundarpichai @MissionAccess_ @dequesystems @accessibility00 @LevelAccessA11y @IAAPOrg @A11yNews @MSFTEnable @acbnational @NFB_voice @BlindUnion @IDA_CRPD_Forum @socialpwds @GoI_MeitY @_DigitalIndia @ncpedp_india @Ncpwds @BeMyEyes @DisabRights_Ind @FreedomSci @APHfortheBlind @fbaccess @NVAccess @DisabilityRepor @BlindDroidUsers @AndroidDev @AndroidAuth @androidcentral @AndroidPolice @_ShivamBhatt @Sindhuvasini @VGTtweets @ppranava68 @NirendraNagar @amarjain2006 @mtonykurian @Rahul400 @istemtech @yatinpanchal143 @PrakashWKamatPK @drvj70 @GyanTherapy @iamasagar @friendsofeyeway @ScoFoIndia @MishaalRahman #GoogleTTS #SpeechServicesByGoogle #TalkBack #AndroidAccessibility #Accessibility #BlindCommunity #ScreenReaderUsers #UserDictionary #CustomPronunciation #NumberProcessing #LowLatency #FixGoogleTTS #AccessibilityMatters #DisabilityRights #InclusionMatters #AccessibilityForAll #DigitalInclusion #TechForAll #EqualAccess #FixAccessibility #AccessibleTech

Collective Appeal from the Blind Community: Google TTS Needs Action, Not Just Acknowledgment. This is a comprehensive public report on "Speech Services by Google" (Google TTS). We are posting this publicly because these issues are not new. They have been reported by multiple users over a long period, and many have already been accepted by your teams through standard feedback channels. We do not need to "DM for details" or "provide audio recordings." We need these long-standing issues and accepted feature requests to be fixed and implemented. The post is clear to avoid any confusion: PART 1: ACKNOWLEDGED FEATURE REQUESTS (NOT IMPLEMENTED) 1. User Dictionary: We still have no ability to create a user dictionary to fix custom pronunciations (e.g., for names or technical words). 2. Uninstall Default Voices: We still cannot uninstall the default English (US) voice pack, which wastes storage and clutters the menu. 3. Number Processing: We still have no feature to choose how numbers are read. The default "millions, billions" format is annoying, and we need options (like digit-by-digit). 4. Date Processing: We still have no feature to customize date formats. We need to be able to set regional standards (e.g., DD/MM/YYYY for India). PART 2: LONG-STANDING BUGS (NOT FIXED) 1. "Zero" Pronunciation Bug: The digit "0" is still incorrectly read as the letter "O" (e.g., "one O five" instead of "one zero five"). This affects all English variants (US, UK, IN, AU, NG). 2. Poor Audio Quality: The voices are not "clear, crisp, and crystal." They are muffled and sound nasally, "like somebody is speaking in the nose." 3. High Latency (Accessibility Failure): The TTS has "huge latency" and is "sluggish." This makes accessibility services like Explore by Touch (TalkBack) "pathetic" and unusable. The "quick responsive" feedback needed for scrolling and swiping is completely absent. 4. No Expressiveness: The engine ignores punctuation. A sentence ending in a question mark (?) is read with the same flat, declarative tone as a period, failing to convey intent. 5. Broken Auto-Language Switching: The auto-language detection "is not working properly." When it does try to switch, it introduces a "huge delay" that disrupts the flow of reading. 6. Incorrect Voice Switching: The system ignores the user's selected "desire voice." For example, a user sets Voice A for English and Voice B for a regional language. When reading, the system will suddenly use a random Voice C for the regional language, creating inconsistency and confusion. 7. Unsolicited Voice Downloads: Google TTS is still automatically downloading unnecessary voices that the user never requested. Even after being manually uninstalled, the system forcibly re-downloads them, wasting data and storage against the user's explicit wishes. These are not new reports requiring investigation. They are well-documented failures requiring action. We request escalation and a timeline for these fixes. @Google @GoogleAccess @Android @sundarpichai @MissionAccess_ @dequesystems @accessibility00 @LevelAccessA11y @IAAPOrg @A11yNews @MSFTEnable @acbnational @NFB_voice @BlindUnion @IDA_CRPD_Forum @socialpwds @GoI_MeitY @_DigitalIndia @ncpedp_india @Ncpwds @BeMyEyes @DisabRightsFund @accessible_apps @FreedomSci @APHfortheBlind @fbaccess @NVAccess @DisabilityRepor @BlindDroidUsers @AndroidDev @AndroidAuth @androidcentral @AndroidPolice @_ShivamBhatt @Sindhuvasini @VGTtweets @ppranava68 @NirendraNagar @amarjain2006 @mtonykurian @Rahul400 @istemtech @yatinpanchal143 @PrakashWKamatPK @drvj70 @GyanTherapy @iamasagar @friendsofeyeway @ScoFoIndia @MishaalRahman #GoogleTTS #SpeechServicesByGoogle #TalkBack #AndroidAccessibility #Accessibility #BlindCommunity #ScreenReaderUsers #UserDictionary #CustomPronunciation #NumberProcessing #LowLatency #FixGoogleTTS #AccessibilityMatters #DisabilityRights #InclusionMatters #AccessibilityForAll #DigitalInclusion #TechForAll #EqualAccess #FixAccessibility #AccessibleTech

👤🟢 Welcome Maxim Malişciuc to Droidcon Italy 2025! Senior Android Developer 🇮🇹🎙️ 🔎 “Navigating the Roadblocks to EAA Compliance” Dc25 Agenda: it.droidcon.com/2025/agenda/ The EU Accessibility Act (EAA) is no longer just on the horizon, it's a deadline. Starting June 28, 2025, apps must meet accessibility standards, but getting there isn’t as simple as adding contentDescription = "arrow button". In this talk, Maxim shares his deep-dive journey into making his company’s app EAA-compliant. From WCAG 2.2 guidelines to the legal and practical nuances of disability-aware design, this session is packed with actionable advice, honest lessons learned, and real examples that go beyond theory. 👉🏻 Curious who else is speaking at #DroidconItaly25? Explore the lineup → it.droidcon.com/2025/speaker… 📅 November 19–20, 2025 📍 Turin, Italy #DroidconItaly #EAACompliance #AndroidAccessibility #EUAccessibilityAct #InclusiveApps #WCAG #MobileDev #AndroidDev #Droidcon2025 #AccessibilityMatters #DevTalks

Cool stuf on #AndroidAccessibility. You can record a sound and be notified about it, and on #Pixel7 you can transcribe audio messages. #CSUNATC23

Today is the day for me 😅 Hope I will show you some good stuff and will inspire you to check your apps on accessibility! #AndroidAccessibility #gdesummit @GoogleDevEurope

If you are like me and you make apps to change people's lives, you can make the difference when you put accessibility in your app. You can make people independent. #AndroidAccessibility #androiddev Image description in the next tweets.

#Didyouknow that your #Android phone has an amazing feature that allows you to improve your overall experience just by changing your phone’s settings? Read our blog by Nikhil Attili to make your Android apps more accessible with #AndroidAccessibility lnkd.in/gJBB_PA

Make android easier to use with the BIG Launcher App for Low Vision, Seniors, and kids! Check out the full video all about the app: youtu.be/sC18uC0KqbU #LowVisionApps #AppsForLowVision #BigLauncher #AndroidAccessibility #appsforseniors #Blind #VisuallyImpaired

Latest video goes over how to use and the less used features of @BeMyEyes - app for the blind, visually impaired, and low vision! youtu.be/plA35-oci3Q #iosaccessibilitiy #androidaccessibility #blind #appsfortheblind,#blindapps, #bemyeyes #visuallyimpaired #lowvision

Here are my top 10 voice commands for both Google Assistant and Siri that can help so much in accessibility! youtu.be/Ey1hHXgeczU #visualimpairmeent #blind #assisticetechnology #assistivetech #iosaccessibilitiy #androidaccessibility #accessibility #a11y

If you like white text on a dark background, android now has a dark theme! Here's how to enable it and how you can toggle it on and off! youtu.be/-fQAJEyqcBI #android #androidaccessibility #assistivetechnology #assisstivetech

I wrote an article for @SpinalCordCom on touch-free mobile solutions: spinalcord.com/blog/using-a-… #assistivetechnology #accessibility #disability #inclusion #a11y #androidaccessibility

Exciting new #facetracking app allows you to control your phone #handsfree . Seems to work well with #Voicedictation on #Android . Nice work and thanks for developing it ! #adaptibility #androidaccessibility #spinalcordinjury #assistivetech

Your @WhatsApp messages aren't safe! @kaspersky #Skygofree #AndroidAccessibility #WhatsApp bit.ly/2Dr8Na3

#Android devs, here’s what happens to Talkback when you use contentDescription for hints, e.g. “Take a picture, double-tap to analyze, double-tap to activate”. Lesson? Do not! http:/g.co/androidaccessibility #a11y

Check out our latest #blog regarding @keepersecurity with #AndroidAccessibility and #Autofill blog.keepersecurity.com/2017…

All Android Phones Vulnerable to Extremely Dangerous Full Device… thehackernews.com/2017/05/an… #Android #Androidaccessibility #androiddeveloper

preparing a lecture about accessibility on Android platform. This subject makes me happy to talk about #androidaccessibility #androiddev

vem gente aprender sobre acessibilidade!!!! #noExcuses #android #accessibility #androidAccessibility x.com/concretes/status/75914…