Skip to main content

Search

Items tagged with: talkback


So they did not mention it but a ton of the google apps have actions now, I keep finding them without a hint they are there. Also not sure why you have issues with it speaking over voice recording, that stopped for me ages ago, like #TalkBack 12.1 ages ago, though this does seem to break with third party tts engines, also the #braille support if you did not know is currently on #Humanware to push a firmware update because even if the HID bluetooth had been released those devices would not work, so people need to pester Humanware about that. Also as of the last month or two Lookout appears as an accessibility app and can be mapped to a shortcut.


What’s New in TalkBack 15.1 accessibleandroid.com/whats-ne… #Android #TalkBack


The @thunderbird team just released the first beta of their email client for Android. I've filed two accessibility bugs on GitHub, and within hours one is addressed and will be in the next beta release (with a pleasant thank you note to boot).

If you feel so inclined, please consider downloading the app and reporting accessibility problems. Especially if you're a native TalkBack user.

#a11y #Accessibility #AndroidAccessibility #Android #TalkBack #ScreenReader #Thunderbird


This has been broken for ages, it will respect it after toggled until the the phone or #talkback restarts, but then forgets it until toggled again.


We’ve launched a comprehensive database to catalog TalkBack and Jieshuo (CSR) screen reader bugs affecting blind and low vision Android users. Our mission is to raise awareness of these issues and help developers address them more effectively and promptly. Join us in improving accessibility for all! Feel free to add your screen reader bugs to make the database more comprehensive. 🌍 accessibleandroid.com/bugs/ #Accessibility #TalkBack #Jieshuo #AndroidAccessibility


Meta has finally fixed a long-standing accessibility issue with Instagram for Android. With Instagram V350.1.0.46.93, TalkBack and Jieshuo users can utilize the standard one-finger double-tap gesture to open Stories. With older releases, the gesture would fail to open Stories in most instances, and only Jieshuo users could utilize the "direct click" function to open Stories.
#Accessibility #Instagram #Android #TalkBack #Jieshuo


So one quick note, bychanging the setting in #talkback for text in images from unlabeled to always the feature will work as before, which I have found acceptable.


Impressions of Google TalkBack 15.0’s Detailed Gemini Image Description: A Feature with Great Potential accessibleandroid.com/impressi… #AI #Gemini #TalkBack


This is a bit technical, but the following new Google-produced video is really interesting if you want more details about TalkBack 15, including better Braille support.
Updates to Android accessibility features and API: youtube.com/watch?v=qLCK0HO_tN…
#Android #Accessibility #TalkBack #Braille #AI


Following the latest updates and changes to WhatsApp, we have updated our accessibility notes to address the regression in usability with TalkBack. Please spread the word. accessibleandroid.com/app/what… #Android #Accessibility #TalkBack


GAAD 2024 and Google: 8 new accessibility updates across TalkBack, Lookout, Maps and more:
Gemini’s integration with TalkBack, Lookout's Find mode, Look to Speak, etc.:
blog.google/outreach-initiativ…
#Accessibility #Google #GAAD #AI #TalkBack


TalkBack 14.2 has been Released: Here’s What you should Know accessibleandroid.com/talkback… #Android #Accessibility #TalkBack


New article on Accessible Android: Sorry Google, but Geo-Restricting TalkBack’s Beta Testing Is Not the Right Decision accessibleandroid.com/sorry-go… #Android #Google #TalkBack


New article on Accessible android: Opinion: Why Samsung/Google TalkBack Separation is Nothing but a Headache accessibleandroid.com/opinion-… #Android #TalkBack


New forum topic under Bugs: Talkback must be turned off to be able to dial a phone number tinyurl.com/4pjhmxvf #TalkBack #Bug #Pixel7Pro


Google publishes the source code for their TalkBack screen reader. GrapheneOS maintains a fork of it and includes it in GrapheneOS with the help of a blind GrapheneOS user who works on their own more elaborate fork. Eventually, we'd like to include more or all of their changes.

TalkBack depends on a text-to-speech (TTS) implementation installed/configured/activated. It needs to have Direct Boot support to function before the first unlock of a profile. Google's TTS implementation supports this and can be used on GrapheneOS, but it's not open source.

We requested Direct Boot support from both prominent open source implementations:

RHVoice: github.com/RHVoice/RHVoice/iss…
eSpeak NG: github.com/espeak-ng/espeak-ng…

eSpeak NG recently added it but it's not yet included in a stable release and their licensing (GPLv3) is too restrictive for us.

RHVoice itself has acceptable licensing for inclusion in GrapheneOS (LGPL v2.1), but has dependencies with restrictive licensing. Both these software projects also have non-free licensing issues for the voices. Neither provides close to a working out-of-the-box experience either.

Google's Speech Services app providing text-to-speech and speech-to-text works perfectly. Their proprietary accessibility services app with extended TalkBack and other services also works fine. However, many of our users don't want to use them and we need something we can bundle.

There aren't currently any usable open source speech-to-text apps. There are experimental open source speech-to-text implementations but they lack Android integration.

We also really need to make a brand new setup wizard with both accessibility and enterprise deployment support.

GrapheneOS still has too little funding and too few developers to take on these projects. These would be standalone projects able to be developed largely independently. There are similar standalone projects which we need to have developed in order to replace some existing apps.

AOSP provides a set of barebones sample apps with outdated user interfaces / features. These are intended to be replaced by OEMs, but we lack the resources of a typical OEM. We replaced AOSP Camera with our own app, but we still need to do the same with Gallery and other apps.

Google has started the process of updating the open source TalkBack, which only happens rarely. We've identified a major issue: a major component has no source code published.

github.com/google/talkback/pul…

Google has been very hostile towards feedback / contributions for TalkBack...

This is one example of something seemingly on the right track significantly regressing. Another example is the takeover of the Seedvault project initially developed for GrapheneOS. It has deviated substantially from the original plans and lacks usability, robustness and security.

In the case of Seedvault, GrapheneOS designed the concept for it and one of our community members created it. It was taken over by a group highly hostile towards us and run into the ground. It doesn't have the intended design/features and lacks usability, security and robustness.

All of these are important standalone app projects for making GrapheneOS highly usable and accessible. What we need is not being developed by others and therefore we need to the resources including funding and developers to make our own implementations meeting our requirements.

#grapheneos #privacy #security #android #mobile #accessibility #texttospeech #speechtotext #talkback #blind #backup