Search

Items tagged with: A11y



Hello @GrapheneOS screen-reader users and other #a11y friends,

There was an interesting debate going on at the end of may where screen reader users were asking for #tts engine included with GrapheneOS base system.
grapheneos.social/@GrapheneOS/…

I understand this is very unlikely to change in the near future as I am not aware of a TTS system that is open-source and modern enough to be included.
@Accessible Android has a list of TTS engines sorted by language at this page: accessibleandroid.com/list-of-…
Except of eSpeak-ng and RHVoice there is another opensource app called SherpaTTS that can use Piper TTS and Coqui based voices at: github.com/woheller69/ttsEngin…
Including eSpeak-ng, RHVoice, SherpaTTS and the list of TTS engines mentioned by accessible android, is there a viable TTS engine or at least one that is close enough to be viable to get included in the foreseable future?

Another approach I have been thinking about is to add / inject the TTS app or any other app I'd like as a part of the install process. It turns out I am not the only one speculating about that idea and it's not practical and feasible either as it's also breaking the security model.
It's been discussed recently at: discuss.grapheneos.org/d/25899…

Another way on how to install an app on an android device would be using adb install from a computer. I am not definatelly sure on this but GrapheneOS does not allow enabling ADB on production builds. In order to instal a TTS app over ADB we'd need to find a way on how to install GrapheneOS with ADB preenabled on first run. This is a huge security hole as well.

There might be a way to build my own flavour of GrapheneOS, but that's too involved, I'd need very powerfull machine for the actual build process and I would again compromise security by either disabling or handling future updates on my own building each new release on my own.

So given the current state I am afraid we screen reader users are out of luck and there is no way to get this thing running on my own with no help from someone else.

The end result is that I'll either get security or I can look elsewhere to get accessibility.

Please am I getting it right or might I have overlooked something that might help me to install GrapheneOS on my own?

Thanks for reading to the end


Les lecteurs d’écran restituent-ils par défaut les textes en gras et en italique ?

Selon les tests menés par @juliemoynat, la réponse est non. C'est le style CSS qui est restitué et non la présence d'une balise (strong, em, b ou i).

Un paramétrage spécifique et complexe du lecteur d'écran est possible, mais la restitution peut être lourde.

a42.fr/restitution-le

#a11y #NVDA #JAWS #VoiceOver



Sensitive content






Yo @ThePSF the vendor you use for the board election ballot is not screen reader accessible. Does that then mean that me and other blind people are unable to vote?

Choked to say the least here...

#a11y #blind #python #psf #accessibleelections


Ein sehr guter Blogbeitrag von meinem KIT-Kollegen Gerhard zum Thema Urlaub - der gut erklärt, warum auch eine Behinderung wie Geburts-Blindheit durchaus kontextabhängig nicht behindernd sein kann.

blindnerd.de/2025/08/20/unter-…
#a11y #accessibility
#blindNerd




Will anyone be updating the NVDA AudioScreen add-on for renewed compatibility with more recent versions of the NVDA screen reader from NV Access? E.g. keyboard shortcuts appear reassigned github.com/nvaccess/audioScree… @NVAccess #blind #a11y #accessibility

Once up-to-date again, I'll gladly add a link to the NVDA AudioScreen add-on in the white paper on brain implants for the blind versus visual-to-auditory sensory substitution artificialvision.com/neuralink… Global accessibility matters.


Has anyone written up best practices for #accessibility with #GoogleSheet's charts & graphs? I'm struggling to deal with the best of bad choices. Text isn't legible or it is hard to differentiate between dark bars.

I wish they had patterns, but someone must have written some guidance on this. #a11y


Monarch tip 12

Yes, you can indeed plug in a HDMi cable to the Monarch, and have all of its output sent to a HDMI Monitor including audio output.

Just plug in a HDMI cable to the port on the right hand side at the front of the Monarch, other end in to your TV, select the correct HDMI channel, and off you go.
Woody
#a11y #Braille #Monarch


Monarch tip 15 and the final one in this initial tip post series

If you have ever used any of the Braille devices from Humanware, then you know how to use the Monarch overall.
This is because the Monarch, like all other Braille devices in the main from Humanware are or were all based on KeySoft which has been around since 1990.
As with all Braille devices from HW, you will find the User Guide on the device.
In the Monarch, and depending on how you have your main menu customised, you will either find the User Guide on the Main Menu or under All Applications.
Enjoy
Woody
#a11y #Braille #Monarch



The slides from my last talk (of 3) from #OSSummit can be found below. Adding the W3C’s New ARRM To Improve Your Project’s A11y — Accessible Roles and Responsibilities Mapping

docs.google.com/presentation/d…

#ARRM #W3c #A11y #Accessibility

/c @wai


My eyes are so itchy and watery (presumably due to seasonal allergies) that I haven't been able to get much work done in the past few days. I'm writing this toot with my eyes closed most of the time. 😑

Dear #accessibility hivemind, is there an easy way to have #Orca working with a natural-sounding text-to-speech voice, that is not eSpeak, but rather something like #MyCroft's Mimic3 ?

What's the state of the art for screenreader TTS voices on #Linux and how do I get it in #Fedora?

#a11y








NV Access is pleased to announce that version 2025.2 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

Full info & Download at: nvaccess.org/post/nvda-2025-2/

This release includes improvements in Windows 11, browse mode, and Microsoft Word. Plus improved Braille display support, updated LibLouis and eSpeak-NG & more!

#NVDA #NVDAsr #ScreenReader #Accessibility #A11y #News #Update


With agentic AI contributing to the AI hype-cycle, I've been giving it some thought from the point of view of a disabled person, and also as an accessibility specialist who's already witnessing the arrival of the agentic web first-hand:
tetralogical.com/blog/2025/08/…

#AI #agentics #accessibility #a11y


On the other hand, insertion of comments (ctrl-alt-c) is still inaccessible with #LibreOffice Writer and #NVDA. #a11y


Sensitive content


🆕 blog! “How long does it take to upgrade an eBook?”

The older I get, the more comfortable I become with complaining. Not merely moaning on social media, but writing a direct email to the perpetrator of some annoyance.

I'd purchased an eBook and was appalled by how crappy the accessibility was. If you don't know, modern ePub books are just HTML…

👀 Read more: shkspr.mobi/blog/2025/08/how-l…

#a11y #accessibility #books #ebook #ebooks






How to Convince People to Care and Invest in Accessibility
stephaniewalter.design/blog/ho…
#accessibility #a11y