Okay, seriously, TalkBack image descriptions are amazing with memes! On r/emulationOnAndroid there's a meme titled "new phone". It's basically an old keypad cell phone, with a game controller put onto it, so the phone screen is in the middle between the two halves of the controller. And the text below the meme says, "So what games can I run on this?"

It's a hilarious meme to me, and I doubt VoiceOver's image classification image descriptions could describe it well enough for me to understand the meme.

#ai #Android #TalkBack #Google

First, they shut down the Basic HTML site, forcing many of us to switch to clients such as Thunderbird. Now, they're using qr codes which are not only inaccessible to the blind but also to those who don't use smartphones! This is ridiculous! Yes, they do still have the option to click whether it's you trying to sign in or not (which still requires a smartphone and a carrier, which they claim to be concerned about), but how long before they remove that, too?

pcmag.com/news/google-is-repla…

#accessibility #Android #authentication #blind #Google #GMail #IOS #Narrator #NVDA #sms #Talkback #technology #Voiceover #Windows

If anyone uses Android with TalkBack and the onscreen Braille keyboard, please try to reproduce and report this issue:

In Talkback, if onscreen keyboard echo is set to words, and a word with punctuation after it is typed, TalkBack does not read the word when Space is typed. Similarly, if an emoticon is typed, like ":)" nothing is spoken when Space is typed.

Steps to reproduce:

• Turn on TalkBack, and open TalkBack settings by tapping once with three fingers. Set up the TalkBack Braille keyboard under the Braille section.
• Go to Verbosity settings, then the keyboard echo option for onscreen keyboards, and set it to "words."
Now, open a text box, turn on the TalkBack Braille Keyboard, and type something like "this is a test." Note the period after test. Then, swipe right with one finger to enter a space.

Expected results:

TalkBack should read "this" "is" "a" "test period."

Actual results:

TalkBack reads "this" "is" "a" and is silent after test is written.

I also put it up on Google's issue tracker if anyone wants to start it.

issuetracker.google.com/issues…

#accessibility #android #blind #TalkBack #Braille

Please boost for reach:

I wonder if Fedi has anyone who works at OnePlus, or knows any way of getting in touch with a human there that can help fix some accessibility issues? I got my OnePlus phone yesterday, and love the hardware, the customizability, and the haptic motor. It's maybe the only Android phone right now that comes with the option to set phone audio to the earpiece when you hold the phone to your ear. And TalkBack is amazingly responsive on it. However, there are accessibility issues, like TalkBack's support for the fingerprint sensor being broken so that it always instructs me to move my finger up, no matter where it is around the sensor, suggested apps on the recent apps screen not always showing the correct app that will be launched, and volume and brightness sliders in quick settings not working correctly with TalkBack. I'm not sure if OnePlus has any accessibility staff, but since they're using AudioEye on their website, I'd guess they have at least thought of accessibility slightly, even if there are often no audio captchas so I can't log into my OnePlus account. Overall though, it's a great phone and may be the one that allows me to settle into Android full time.

#accessibility #Boost_OK #blind #OnePlus #Android #OnePlus #OnePlus13 #OP13 #TalkBack

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

add Direct Boot support for Android so RHVoice can be used with TalkBack before the initial unlock · Issue #271 · RHVoice/RHVoice

More information: https://developer.android.com/training/articles/direct-boot https://github.com/GrapheneOS/platform_packages_apps_Updater is a trivial example of using this. You need to mark a sub...

^GitHub