Android’s Talkback 15 Review

In this episode of Double Tap, Steven Scott and Shaun Preece welcome John Dyer, a TalkBack expert, to review TalkBack 15 and discuss the latest updates in Android accessibility. John shares insights on the new features, including the integration of Google Gemini for AI-powered image descriptions, giving blind and low-vision users more autonomy when navigating inaccessible content.

“The biggest new feature in TalkBack 15 is the ability to describe images and on-screen content using Google Gemini,” John explains. “Instead of needing a separate app like Be My Eyes, you can now use TalkBack directly to get descriptions of anything within focus, whether it’s an image, a menu, or even an unlabeled button on a website.” He demonstrates how users can activate this by accessing the TalkBack menu or assigning a custom gesture, allowing for seamless interaction.

Discussing how well Google Gemini compares to other AI description tools, John notes that while it provides detailed descriptions similar to Be My AI, it sometimes adds unnecessary commentary. “I was looking at a Mario Kart play set, and it told me, ‘This would be a great gift for any fan of the Mario franchise.’ That’s not the kind of information I needed,” he jokes. He also highlights a current limitation: “Unlike Be My AI, you can’t interrogate the response further. If you want to ask follow-up questions, you’d have to use Gemini separately.”

Beyond image descriptions, TalkBack 15 introduces refinements like new Braille display gestures, improved punctuation settings, and changes to continuous reading behavior. “Previously, continuous reading would start from the next item, but now it begins from the current item, which most people seem to prefer,” John explains. However, he acknowledges that TalkBack’s development pace is slower than Apple’s VoiceOver. “Google updates TalkBack three times a year, but it doesn’t have the same development resources that Apple dedicates to VoiceOver.”

The discussion also covers the challenges of using TalkBack on Samsung devices. John clarifies that Samsung ships its own version of TalkBack, which can prevent users from easily enabling Google’s version. “If you want Google’s TalkBack, you need to remove Samsung’s version using Android debug bridge,” he explains. While Samsung’s TalkBack includes optimizations for Bixby and foldable devices, it often lags behind in feature updates. “Samsung’s approach means users won’t get Gemini integration right away. They’ll have to wait for the next One UI update.”

Looking ahead, John hopes that TalkBack will continue evolving to match VoiceOver’s customization options, particularly per-app settings. “Right now, TalkBack settings apply system-wide, whereas VoiceOver lets you customize per app. That would be a great addition.” He also emphasizes the need for a dedicated Android accessibility community, recommending listeners check out Blind Android Users and Accessible Android, which aim to be the Android equivalent of AppleVis.

As the episode wraps up, John shares his overall impression of TalkBack 15. “It’s a solid update, but aside from Gemini integration, it’s mostly minor refinements. Android accessibility is improving, but there’s still room for growth.”