Search

Items tagged with: a11y






Even though I have spoken publicly on the topic of digital accessibility before, many of those instances weren't streamed online so whoever wasn't there where it happened, couldn't catch it. Next week I am presenting at the Wagtail Space 2025 in a talk entitled "Who's that code snippet? A Screen Reader guessing game", alongside Laura Wissiak who came up with this amazing idea at this year's A-Tag in Vienna and has agreed to take me for this fun ride as well. Expect tricky ARIA and HTML code and lots of Pokemon. Can you catch them all? wagtail.org/wagtail-space-2025… Our talk is on Thursday, Oct 9 at 3:30 PM CET. See you there! #Accessibility #A11y #Wagtail


#a11y


2 / 2: Did you know @GNOME Files aka #nautilus has a nifty feature where it can move selected files into a newly created folder? #ScreenReader #a11y is preserved.
In order to use it just select multiple files and find Move to new folder item in the shift+F10 popup menu.


1 / 2: Did you know @GNOME Files aka #nautilus has a nifty feature where it can batch rename files? Advanced features include adding sequential numbering, using placeholders and doing search and replace on the names of selected files. #ScreenReader #a11y is preserved.
In order to use it just select multiple files and find Rename item in the shift+F10 popup menu or simply press F2. Also... Don't be shy to press the add button in the batch rename dialog.




Yeah, I've updated my @Arch Linux to @GNOME 49.
There are some nifty #a11y related tweaks such as better labelling for gnome shell menus, refreshed settings UI, I like how presentation of various lists e.g. List of wireless networks is presented with screen reader including signal strength.

Thanks to everyone involved for the improvements.



At last, all the accessibility improvements on GNOME Calendar are finally available as a stable release. Get it on Flathub while it's hot!!!

flathub.org/en/apps/org.gnome.…

#Accessibility #GNOME #GTK #GTK4 #libadwaita #a11y #calendar #GNOMECalendar #Linux #GNU #OpenSource #FOSS #FreeSoftware #OSS




Accessibility matters ❤️ Here’s a quick demo of how the new Dice feature in Skoro works with VoiceOver, so even visually impaired users can use the app.

Skoro on the App Store:
➡️ apps.apple.com/app/id160831104…

#iOSdev #a11y #uxdesign #buildinpublic




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







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.



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