Back in March 2024, I penned an ambitious “Blueprint for Google” to revolutionize Android accessibility in ten areas that, let’s be honest, were desperately in need of some TLC. It’s been quite a few months since then, and with great anticipation (and perhaps a smidge of wishful thinking), I’ve been keeping an eye on Google’s progress. Spoiler alert: there’s been a lot of… watching and not enough doing. But let’s give credit where it’s due — there have been a few flickers of hope amidst the darkness.
Table of Contents
- 1. Open Up TalkBack’s Beta-Testing Program to the Whole Universe
- 2. Fully Embrace TalkBack and Accessibility Actions
- 3. Prevent TalkBack from Speaking While Recording Voice Messages
- 4. Pull Lookout Out of Its Miserable Oblivion
- 5. Make High-Quality Offline Google TTS Voices Available to TalkBack Users
- 6. Add More Languages to Speech Recognition & Synthesis, Including Persian
- 7. Clear Up the Google TalkBack vs. Samsung TalkBack Mess
- 8. Divide the Controls Item in TalkBack’s Reading Controls
- 9. Improve Braille Support for TalkBack
- 10. Share Some of That AI Prowess with TalkBack for Offline Image Descriptions
- In Conclusion
1. Open Up TalkBack’s Beta-Testing Program to the Whole Universe
Status: Nothing has been done here.
In the last article, I suggested that Google should widen the doors to TalkBack’s beta program. And by widen, I mean blow those doors off their hinges and let the whole world in. Well, as it stands, those doors remain firmly bolted shut, accessible only to a select few regions. It’s especially odd given that most Google Android apps have public betas, so why TalkBack is excluded is a bit of a head-scratcher. It’s like trying to get into an ultra-exclusive VIP lounge… except this one’s for a screen reader. Priorities, right?
2. Fully Embrace TalkBack and Accessibility Actions
Status: Nothing.
Here’s the deal: TalkBack has so much untapped potential. Yet Google’s reluctance to truly embrace its own accessibility tool feels like watching a star athlete benched for no reason. Adding to the irony, Google’s own apps on iOS have more accessibility actions via VoiceOver Rotor options than they do on their native Android platform! For a deeper dive into Accessibility Actions, it’s clear that Android could use some love in this department too. It’s like Google treats iOS as the golden child, while TalkBack on Android just gets the scraps. Come on, Google, your Android users are waiting!
3. Prevent TalkBack from Speaking While Recording Voice Messages
Status: Nothing.
One would think stopping TalkBack from yammering away while recording voice messages in many apps would be a relatively straightforward fix. But alas, here we are, still grappling with TalkBack’s uninvited commentary when all we want to do is record a simple “Hey, I’ll call you later.” Google, please, a little radio silence during voice message recording is all we’re asking for.
4. Pull Lookout Out of Its Miserable Oblivion
Status: Lookout can now provide image descriptions based on AI.
Alright, though not a TalkBack-specific enhancement per se, but I have to give Google a nod here. Lookout has finally started to crawl out from under its rock, now offering AI-powered image descriptions. It’s like seeing an old friend who finally decided to get a haircut — definitely an improvement, though there’s still a lot more that could be done to polish things up. Here’s the catch: those descriptions are pretty short, nowhere near as detailed as what apps like Be My Eyes or Seeing AI offer. It’s like getting a half-hearted answer from a friend who’s too busy to chat. Plus, you can’t ask the AI follow-up questions unless you are a happy resident of a few countries cherished by Google. And let’s not forget that some of Lookout’s modes, like “Text” and “Find and Explore,” still wear the “beta” badge as if they’re lazy students who refuse to graduate. It’s time to hand out those diplomas, Google!
5. Make High-Quality Offline Google TTS Voices Available to TalkBack Users
Status: Again, nothing.
Access to offline high-quality Google voices? Forget it. For a tech giant that has more resources than it knows what to do with,, Google has been surprisingly stingy with its high-quality TTS voices. We’re still stuck using third-party workarounds – like AutoTTS – for what should be a standard feature. Come on, Google, you’ve got the goods — share them!
6. Add More Languages to Speech Recognition & Synthesis, Including Persian
Status: Only support for some Indian languages has been added.
While I was hoping for expanded support to include Persian (and a few others), all we’ve gotten is the addition of a handful of Indian languages. While that’s great for users in those regions, it’s like Google is handing out crumbs when we’re all waiting for the full buffet. Persian speakers are still out here, hoping that one day, we’ll get a seat at the table.
7. Clear Up the Google TalkBack vs. Samsung TalkBack Mess
Status: Nothing, and Samsung keeps updating TalkBack on its own after Google releases.
The Great TalkBack Divide remains alive and well. For more on why this separation is a headache, check out this article. Google and Samsung continue to play an odd game of “Who’s the real TalkBack?” with each releasing their own versions. Users are left in a confusing maze of overlapping features and inconsistencies. Samsung also makes it all the more difficult to install Google TalkBack releases on its phones. Let’s hope they resolve this sibling rivalry soon because the users are the ones caught in the crossfire.
8. Divide the Controls Item in TalkBack’s Reading Controls
Status: Implemented in TalkBack 15.1.
Finally, some good news! TalkBack 15.1 has introduced more refined controls, allowing users to add navigation items for the web. It’s a welcome improvement for those of us who have struggled to jump between checkboxes, edit boxes, and combos. I’d call it a win, even if it’s one of the few. For details, see this overview of TalkBack 15.1.
9. Improve Braille Support for TalkBack
Status: Almost nothing visible has been done.
Despite the promises and the potential, improvements to Braille support have been minimal at best. If you’re a Braille user, it seems like you’re still on the waiting list. Here’s hoping for a more inclusive future… eventually.
Status: TalkBack 15 and newer can generate image descriptions based on Google Gemini.
TalkBack can now generate image descriptions using Google’s Gemini AI. For Pixel 9 users, there’s even a limited offline mode — though descriptions are short and not always the most accurate. It’s a promising start, but more work is needed to make these descriptions richer and available to a wider audience.
In Conclusion
It’s a mixed bag. While Google deserves some applause for a few overdue improvements (hello, Lookout and TalkBack’s web navigation!), most of the critical items from the original blueprint still remain on the “to-do” list. On the plus side, we’ve seen the implementation of continuous reading from the current position and improvements in opening links in TalkBack 15.1, which make navigation smoother. But beyond that, the road to accessibility seems to be littered with good intentions that often get lost in the shuffle. As they say, the road to accessibility is paved with good intentions… and a fair share of missed opportunities. So, here’s hoping Google picks up the pace and starts treating accessibility as more than just a checkbox on their update list. Until then, we’ll keep advocating, waiting, and — let’s be honest — occasionally rolling our eyes.
Stay tuned, and as always, keep advocating for a more accessible digital world.
sadly I think it will be years before things change if at all.