Skip to main content


Items tagged with: screenreaders

Thanks to Jonathan Mosen on the @podcast Living Blindfully podcast for an informative review of
Phonak's hearing aid technology. I am currently in a trial of Phonak devices, and Jonathan's helpful review coheres with my experience. I haven't yet tried any of the accessories, such as remote microphones, that are also addressed in the review.…
#HearingAids #ScreenReaders #Accessibility

If image generation gets good enough to make me Twitch banners, or blog featured images, or make small video edits for me, or write me CSS that actually looks good, you bet your glutal hemispheres I'm going to make use of it. Purely a matter of efficiency. We haven't had a decent video editor that's #accessible as long as I've been alive, I think i've waited long enough for hoomans to step up. If AI can do it, AI can do it. Screen readers can't tell me if CSS is doing what I want, so if AI can do it that just means I can be more productive as a developer. Again, I've waited for this situation to improve in #screenreaders for my entire professional career, so if what is for all intents and purposes a new tool can enable me to do this, I will happily make use of it. Summarizing articles in between all the newsletter popups, ads, images without alt text and silent videos? Absolutely. Just another #accessibility tool at this point. So yeah. Bad, but not all bad.

Sometimes, you might think that previous #accessibility wisdom has been superseded by new "facts". Maybe someone told you that #screenReaders don't work well with a particular design pattern, but you tested #ScreenReader X and it seemed to work fine. Perhaps you heard that an interactive HTML input doesn't persist with forced colours styling, but you tried a High Contrast mode in Microsoft Edge and it seemed to be there.

There are three considerations usually missing here:

1. How are you defining and evaluating the working state? Do you have a functional, accurate understanding of the #accessTechnology or accessibility feature you are asserting things about?
2. You tested one thing in relation to a statement about multiple things, e.g. a statement is made about screen readers, plural, and you only tested with #VoiceOver (it's always VoiceOver). Beyond posting on the web-a11y Slack, how do you propose testing more broadly, if you plan to at all?
3. Possibly the most critical at all: is this question worth its overheads? If answering it conclusively would require me to test ten screen readers with 45 speech engines, or seven browsers with 52 permutations of CSS properties, maybe following the advice is "cheaper" than determining whether the advice is still completely relevant.

Important disclaimer: this relates specifically to cases where following the advice would not actively make things worse for users.

TL;DR: when you know doing a thing won't make things bad, doing the thing is usually quicker than evaluating whether not doing the thing is also bad.

To what degree does NVDA actually have support for TUIs? When I look at TUIs (terminal user interfaces) for tools like Joplin, Vim, practically anything that requires using arrow keys/tab within a terminal, it almost always is a horrible experience. Are there things TUI developers can do to better accommodate NVDA? @NVAccess @tspivey
Do terminal-first tools like TDSR in a WSL2 shell improve this at all? #nvdasr #screenreaders #accessibility

How screen readers read special characters:… Be sure to read the Takeaway. #a11y #webdev #screenreaders

@nah @fvsch @sonny @matt But here’s the thing: Wayland would never have been made the default if, say, fonts didn’t render correctly. Not having a functional screen reader is as big an issue for people who rely on screen readers. So at some point, someone at Canonical decided that it didn’t matter that people who use screen readers would be excluded. And so they should be ashamed.

#a11y #canonical #wayland #orca #screenReaders #accessibility

People who use #ScreenReaders, imagine a feature on your instance where you can automatically hide any post that contains images/videos without alt text.

If you reply with an opinion and YOU PERSONALLY don't need alt text for accessibility reasons, I will probably block you.

#poll #ScreenReader #accessibility #a11y #blind

  • It's a great idea (32%, 16 votes)
  • No strong feelings (6%, 3 votes)
  • It's a bad idea (6%, 3 votes)
  • I don't use a screen reader (56%, 28 votes)
50 voters. Poll end: 2 months ago

👁‍🗨Screen Readers support for text level HTML semantics

"A long time ago (2008) I wrote an article: Screen Readers lack emphasis. At the time, 15 years ago..."

#a11y #webDev #HTML #screenReaders…

@Matthias ✔ Ah yes now I understand. Unfortunatelly that part is not yet #screenreaders #accessible thus when using up and down arrow keys to make the choice I don't know what I'm selecting. I'll first try to look into it my-self and if I won't be able to fix it on my own I'll file it as a feature request then.
Thanks for your patience explaining this feature to me.

Ensuring negative numbers are available for everyone. "The minus character (−) yields great support in most screen readers, and suffers less situational gotchas than the hyphen-minus character"…

Great article written by 2 of my favorite comrades.

#webdev #webdesign #a11y #html #tips #screenreaders

Oh, #screenreaders cutting off long #alttext is a myth?…

That is fantastic news, I was really worried we'd have to do ridiculous things with longdesc (deprecated) or visible alt text.

Ahh! Finally.

it's odilia, the odilia screenreader! finally, the long awaited by some, version 0.1.0 is out, it has been for afew hours now, but as they say, the news are only old if you heard them at least once, so for most people they should be fresh. If you want to check it out, feel free to do so, dropping bug reports as you find them, never hesitate to pop things in that issue tracker, or come talk to us in our matrix space,, or irc,, and
the releace announcement can be found at
finally, we're here! A big thank you to the community who waited patiently for this release, as well as everyone who contributed, in one way or another, to the project's growth, we're here, we hear you, and we'll never forget our community! let's show the world it can indeed be done, make linux great again!
#accessibility #screenreader #screenreaders #blind #linux #odilia

Staying still in the land of open source projects, this slipped yesterday through my Reddit reading:
FeedGears is a web-based, self-hostable RSS client with particular attention to accessibility. According to the dev, it was tested against the WCAG 2.1 guidelines on the AA level, has integrated shortcuts, consistent keyboard navigation and automatic announcements for system events. It's pretty new so a lot of features might be missing but that's for the contact mechanisms and the feedback. :)
I haven't tested this myself yet but the landing page looks definitely alright.
#Accessibility #OpenSource #RSS #Blind #ScreenReaders

Browsing Github last night, I came across two interesting, potentially accessible open source projects related to radio.
1. Salamandra Radio - an automation software for station in its early development. Screen reader specific fixes have been mentioned in the release notes and so were hotkeys, although these do not seem to be documented anywhere; the app starts in Portuguese by default but a change to English is possible in the settings; also buttons in the toolbar do not seem to be labelled but upon focusing them, a tooltip is read out so we can go by those to tell what the buttons are doing.…
2. Axios - a simple radio player supporting the Radio Browser API. It is accessible in a similar way as Salamandra, allows for searching the directory, playing whatever is found, and controlling the volume.
Feel free to explore, hack, spread the word or do whatever else you usually do in such cases.
#Accessibility #Blind #ScreenReaders #Radio #OpenSource

A guide for using #screenReaders with #Mastodon.

#a11y #accessibility…