Close

What are you looking for?

cancel
Showing results for 
Search instead for 
Did you mean: 

A message for Samsung Accessibility Regarding Google TalkBack

(Topic created on: 22-12-2024 10:53 AM)
1219 Views
Ciprian14
Journeyman
Options

Hi Samsung Team,
I'm writing about how TalkBack works on Samsung phones. Right now, Samsung uses its own version of TalkBack instead of Google's, and this causes some problems for visually impaired users.
First, Samsung TalkBack updates only come with big One UI updates. This means I have to wait longer for new features and fixes compared to people on other Android phones, who get them straight from the Play Store. Also, older Samsung phones might never get new TalkBack versions. The Samsung TalkBack also doesn't have all the features Google's has, like the better image descriptions.
Another issue is that I can't choose to use Google's TalkBack, even if I install it. I'm stuck with Samsung’s version. The only way to use Google’s is a complicated method that most people don't know how to do. Samsung's own Galaxy Watches use Google's TalkBack, which shows it works well, so why not on phones?
These issues make it harder for me to use my phone. It’s important that I have the newest features and a consistent experience. While I appreciate the work on Samsung’s TalkBack, linking it to One UI updates slows things down for users who need the most up-to-date accessibility tools.
To make things better, I suggest using Google’s TalkBack from the Play Store. This would give me quick updates and all the features. If this isn't possible, please let me choose between Samsung's and Google's TalkBack in the settings, like how we choose web browsers.
This is a common issue discussed by people who use accessibility features. You can read more about it here:

https://accessibleandroid.com/opinion-why-samsung-google-talkback-separation-is-nothing-but-a-headac...

https://accessibleandroid.com/google-vs-samsung-the-android-accessibility-showdown-for-2025-and-beyo...
I hope Samsung will think about these problems to make sure visually impaired users have the best possible experience. Thanks for your time.

12 REPLIES 12
JohnDyer
First Poster
Options

I 100 percent agree. I could not have said it better myself. 

SalihKunduz
First Poster
Options

Great post explaining the issues. I 100% agree.

AntS
Moderator
Moderator
Options

Hi @Ciprian14 (and others), Thanks for the feedback!

 

As well as the better image descriptions (and quicker updates) are there any other specific things you and others would like to be implemented in the TalkBack feature to improve the experience? I'll pass those suggestions on to the developers. 

Ciprian14
Journeyman
Options

Simply let Samsung devices use Google TalkBack, just like any other manufacturer. Allow us to receive updates via the Google Play Store and Google will take care of the features.

AndrewL
Moderator
Moderator
Options

@Ciprian14: I have gone ahead and passed your suggestion to our Research and Development Team, and will keep you updated with any feedback I receive regarding the implementation of Google TalkBack in future products and updates. 

amirhs
First Poster
Options

As a Samsung and TalkBack user, I fully support these suggestions. In fact, it's a huge pain that my S24 Ultra's Samsung TalkBack is always behind the official Google TalkBack release in terms of features. This is a flagship device, after all. And Samsung's refusal to support Gemini-based descriptions for TalkBack, or any image description per se, is extremely irksome. The issues are so bothersome that I'm considering ditching Samsung as my next smartphone, and this trend of "Samsung being inattentive to accessibility" is finding supporters among the visually impaired on Mastodon. It's time Samsung got their act together.

Ciprian14
Journeyman
Options

I totally agree! This is a real issue with Samsung updates and accessibility. Also, the fact that TalkBack doesn't behave the same on all the Galaxy device lineups. is an issue. as well. I talked about this in my article here:https://accessibleandroid.com/samsung-android-accessibility-framework-34-1-1-highlights-paid-a-buck-...
As a suggestion for Samsung, inovating and bringing change in TalkBack is possible. It would be best, and honestly I'd see TalkBack going so far, if you worked with Google to improve TalkBack for all the users, by working with Google on Accessibility Suite itself, just like you worked with them on Messages and other products. 
Samsung always showed that there's place for better. With legendary devices like the S10+ and later S23Ultra, You, Samsung, had shown that you are a company hard to beat and almost impossible to reach in many areas.
Accessibility is a bit of an issue, though, with none of the Samsung apps supporting accessibility actions, which would also be needed. BUt working together with Google to improve TalKBack for everyone and show everyone that not just Samsung devices can benefit from the accessibility team that builds the best accessibility framework on a firmware.

KareenKiwan
First Poster
Options

Well said and explained; I 100% agree. The current separation between Samsung and Google TalkBack, along with the way updates are handled on Samsung devices, has a direct negative impact on the accessibility experience for blind users. Additionally, not including essential features from Google TalkBack, such as the Gemini detailed image description, is a serious omission that leaves many users unable to benefit from this advancement. A capable, up-to-date screen reader is not a supplemental service for blind users; it is an essential necessity.

Thaqib Mir
First Poster
Options

I agree 1000000000 percent. This is just a way to make users not use the Samsung talkback , instead to make them switch to another reader. Samsung should really consider either giving us options to choose between the two versions of tb, or else, dich this fiasko all together. I don't even see the point here. I'd understand if samsung would've been doing better, but it's worse than the google's talkback. Thus, it's nothing but a way to drop the userbase in my opinion.