My relative is currently using a OnePlus Nord CE 2 5G; he is visually handicapped and has enabled TalkBack on his phone to assist his daily use. Both System language and TalkBack language are set to Simplified Chinese, but after several minutes of use, the voice will speak in Chinese but with an American accent. It's quite hard to understand what the voice is saying due to the accent. I've tried looking around on various websites but am still unable to find any solution or explanation. Is there any fix or solution for this problem?

We have some locked down tablet leased out for our truck drivers to use. Every now and then, one of them will accidentally activate the talk back feature. We do not have access to the settings menu of the tablet to turn it off. I learned a few months ago that you could just hold both volume buttons to disable this feature which worked for a while, but is now not fixing the problem. Does anyone know how to turn off the talk back screen reading feature without going into the settings menu?

I accidentally turned on TalkBack in the Accessibility menu. When I turned it on, I got some kind of walkthrough on how to use it. I couldn't cancel it. So I turned off my phone. When I turned it back on again, it took me 15 minutes to unlock my phone. Apparently I had to touch a button to give it focus and then double-tap it to click it. Now my question is: how do I turn this off? I can't reach the settings because I don't know how to access a dropdown and I can't scroll through all my apps.

When a blind user is using TalkBack to listen to text, they may want to figure out the actual spelling of the text. Can TalkBack be used to spell a Chinese character or stream of Chinese characters in terms of Chinese radical or Chinese character component names, so that the blind user may know what the characters that are being read out are made of? How can this be enabled in Android?

I am new to Android development. I have a doubt with regard to the Android TalkBack feature and how it is used with a braille display. In my project, I'm trying to use this TalkBack feature to print/display the text on the screen to a braille reading device (for example: Orbit Reader 20). I don't know how the Android TalkBack feature scans for nearby braille displays/reading devices. I know it sends some packets to and from the braille display/reading device, but I don't know what exactly they are. Any help would be appreciated, including documentation/resources! Thanks!

I would like to know whether on Android devices it is possible to input a combined touch plus swipe gesture. For instance, I could touch with one or more fingers with the left hand, and simultaneously swipe left to right or right to left with the right hand. As an application, with TakBack, this could be used, with one finger plus swipe left to right or right to left, to skip forward or backward one word while text is being read, with two fingers plus swipe left to right or right to left, to skip forward or backward one sentence while text is being read, and three fingers plus swipe to toggle pausing while text is being read. I think, this could be significantly useful in improving usability of TalkBack for blind users. When will this be available in Android? Thanks.

I am trying to use TalkBack on a Realme 6 Android 11 phone. When I activate TalkBack by pressing the volume up and volume down keys simultaneously, I can then iterate through the following entries by swiping up then down to move forward, or down then up to move backwards: - Spoken language - Speech rate - Windows - Links - Controls - Headings - Paragraphs - Words - Characters However, I don't understand what these entries are. What are they, what do they do, or how do I use them, using TalkBack? Thank you for your replies.

On the Samsung Galaxy Tab A 10.1, after downloading the latest OS, some settings got changed and the TalkBack comes on. However, I cannot find a TalkBack accessibility item to turn off. What's the workaround to shut this off/remove it?

I am using Android on a Realme 6 phone. When reading interface elements out with TalkBack, it wastes a lot of time reading out what is on the screen as I explore by touch or use linear navigation. It would be nice if TalkBack had a feature where you could switch back and forth between normal mode and another "quick cue" mode. In this quick cue mode, when TalkBack encounters an element, it plays a very brief sound corresponding to the type of widget encountered. The user learns to recognize these sounds and can browse quickly through the interface without being distracted, closer to how a seeing user of the interface would. When the user wants to know what type of element the sound corresponds to, the user swipes left then up then right, to be reminded. Otherwise scrolls quickly till they get to what they want, quickly building a mental idea of what's there. To read out the text of a button, since the sound cue alone is played out, the user swipes right then up the left. The button text, which takes longer to be read out, is then read aloud. Or the user can switch back to normal mode and proceed. The sound cues may correspond to things like "time", "share button", "tool button", "add button", "modify button", "delete button", "done button", "submit button", "text widget", "caption", "text entry widget", and so on. Markup, following a given markup XML prefix for the standard set of standardized sounds included, would be supplied, and available in the source code to support this, for the benefit of these very blind users so that they may be able to hear these standard assigned cues for faster less stressful browsing in TalkBack than I'd text would have to be read out everywhere. Many times when we view a time widget we don't read the time out. Similarly, when viewing a share button, we don't read out "share" to ourselves, we simply recognize the button. With a sound cue, the non-seeing users experience corresponds more closely to a seeing user's experience. This would thus enhance the blind user's ability to use a variety of apps, including apps that were designed primarily for seeing users, but that included blind user support. Perhaps, in many cases, a separate interface should be designed and made accessible to blind users in apps. However, it is not guaranteed that developers would do this, although it would only be right if they were pushed to do this through development tools, and, in this case, how would a blind user access the separate blind user-specific interface to the given apps supporting this feature. There could be a special swipe gesture in TalkBack to switch between normal mode and quick cue mode. For instance, up then right then down, or up then left then down. Does TalkBack currently support such a behavior, or does anyone know whether Google and Android have plans to support this behavior for blind users in the future? Thanks.

I was wondering about a question I raised in another post about accessibility. That is, how would an app provide a separate interface for blind users? The Android system, would have to support a special feature, "navigate in blind mode". Android already has TalkBack, but that is designed to explore apps in their standard layout, a layout that may not always be completely accessible or convenient for blind users, who might require or get more benefit from something else. How does Android provide support, if any, for this. Is there a switch for blind and non blind mode which does not end up in being TalkBack, that can be used? Thanks.

I would like to know what Android does to support blind Android users with sort attention span. One of the problems with these users, is, that while the user interface talks, the sound of the reading voice itself distracts them to the point where they focus on the sounds and not on the letters that make up the words. In this manner, they can never understand the words, that are being spoken out. The words are just spoken out too fast, and everything just goes too fast for them to keep track of everything. What these users need, besides linear navigation in TalkBack, is a way to control the speed at which words and pauses are pronounced. They need to be able to drag out the pronunciation of the words over a long length of time. This slows everything down. Never mind. The point is that they must understand. Not only, they must be able to memorize and keep track of what goes by while it is being spoken. Ideally these users should be able to control, not only swiping forward and backward between one word and another to navigate, but also, the length of time for each letter to be pronounced. They should have access to quadruple tap and drag a slider to control the speed, which they need to change as needed while everything is read. Because, at any given point in time, their ability to focus on longer pronunciations or shorter pronountiations as reading speed changes, and there is always, at any given point of time, matching their awareness and awakeness, a right, optimal, speed, with which to read the words out aloud. The same goes for sound clues. These, just like the words, should also be sounded out longer or shorter, to allow the blind user with attention problems to have the time they need, in their slowness, to focus on them, and say to themselves, "yes, I've heard the sound i recognize as being such and such", and this must take place before the sounds finishes. The user must be able to talk to themselves during the sound, not after, when the sound had finished and the user has forgotten about it before they were able to say anything to themselves, about it. So, my question is, does Android have anything to support this feature, which would be indispensably necessary to make the device accessible to blind users with sort attention span? Thanks.

I would like to know how to use TalkBack to search for entries by issuing a given partial keyword or regular expression. Perhaps, as an alternative, the user could speak an entry, and, after the text was entered, the user could check the text for correctness, by having it read aloud, letter per letter, or as a whole, and then issue the search. This could be useful in several contexts, for instance, the blind person is coding or using some app with menus or am interface with a list of buttons and wants to get to a given menu entry without remembering its position, without getting confused by listening to other entries, which may make them forget what they're doing. Or they may be going through the chronology of a web browser, and cannot find what they're looking for. It would be nice if there were a way to do this, because it would really help. Thanks.

I have a Motorola Moto E running KitKat 4.4.4. It somehow got into TalkBack mode and now I can't swipe the screen to get into Settings. I did a factory reset, but it's still there! How can I change the settings when I can't get to them?

I have Samsung S21 5G Android 11 mobile. This device Talkback talking speed is very fast that I am not able to catch it. How can I reduce speed ?

What is the difference between Text-to-Speech and TalkBack and Google Talk? (also, I am unable to open the TalkBack tutorial on my Samsung Galaxy SIII Neo Android 4.4.2 (it just crashes the Settings app)). Any idea where I may find a better tutorial? Thanks.

I am developing apps for Android and now have started to use Android 8 (Oreo) on my Pixel 2-phone. While working on the accessibility of an app I've noticed that a certain entry in the "Global Context Menu" is missing when you use the gesture to open the menu (Swipe down -> then right while Talkback is enabled). Namely the entry "pause feedback" is gone, which ... well ... paused the Talkback-reader, so you could click normally around in your app. The entry is still mentioned [here](https://support.google.com/accessibility/android/answer/6007066?hl=en) by Google. This makes it somewhat harder to work on accessibility for an app, since you need either to click around a lot more or constantly enable / disable the Talkback-reader. Is there another way to pause the Talkback-reader temporarily or to get the "pause feedback" entry back?

How can I override Talk back on my samsung galaxy J1 phone. When I switch on my phone I cannot access my menu as the voice keeps telling me to press the select menu twice

Can you switch out the voice of the Talkback-reader completely? In car-navigationsystems you can download "funny" or different sounding persons (male, female, actor, ...). But the for the Talkback-reader you can only change the pitch and speed that it should use. I am not sure if Talkback is using voice-samples internally, which would make it necessary to record a real person like an actor speaking. Or if Talkback is using synthesized speech, with which parameters you can fiddle around. So can you change the voice of the Talkback-reader? For instance into a funny voice, or Hawking-like, or your own, ...?

When I am on an invisible recaptcha audio challenge (see image below) and I am using Google TalkBack is there a gesture to repeat the voice saying the numbers? When I press the play button focus seems to go to the textfield below and TalkBack describes the change of focus at the same time with the recaptcha voice saying the audio challenge making it difficult for me to hear both voices at the same time and solve the 'puzzle'. When I use VoiceOver on Mac, if I press ctrl button, the recaptcha voice repeats the audio challenge and I can solve the puzzle without having to hear both voices simultaneously. Is there a gesture for TalkBack to repeat the challenge without moving the focus somewhere else?

I'm blind and I tried Android 5.0 and it seemed not very good using talkback. Does someone know if there are many differences with the new version?