@Daniel Gultsch I'm sorry to bring this up again as it's somewhat personal, but I feel there is a bit of downside when it comes to #XMPP adoption among #screenReader users. The issue is that #conversations is the only #accessible xmpp app I know off. Ideally we'd appreciate at least single accessible XMPP based messenger per platform what @ArcaneChat @Delta Chat (39c3) have already.
Dear #QT toolkit, recently I'm again looking into your #screenreader #a11y into #QML in particular. I'm trying to make one of my favorite apps @Mixxx DJ Software a bit more accessible. Last night I have managed to turn the menu with items such as 4 decks, Library, Effects and more into aria toolbar pattern in terms of keyboard navigation. It only consumes single tab stop when navigating through it and other buttons can be reached using the arrow keys. Of course there is much more to do and I've started a forum topic documenting my attempts.
New #screenReader verbosity settings for messages are now widely available in #Slack, under the #accessibility category of preferences. You can now control which parts of messages are spoken and in what order.
As part of this change, you'll also find that recent replies in threads now have relative timestamps (e.g. "just now" or "2 minutes ago") instead of absolute ones. This update brings the screen reader experience in line with the visual interface, with absolute timestamps still being used outside of threads.
If you have suggestions or run into problems, please use the /feedback command and mention that you use a screen reader. Alternatively I'm also happy to pass along any issues if I can reproduce them.
Ist hier jemand, der mir Fragen zu Screenreadern für Personen mit Sehbehinderung beantworten kann? Ich schreibe gerade Alt-Texts für eine Website und habe eine spezifische Frage: Wie kommen Screenreader mit englischen Begriffen und Abkürzungen klar?
In this edition: - Holiday Season Trading Hours - NVDA with Digitech Reece - World Blindness Summit Presentation - Finding Things
Do check it out, have a wonderful break if you are having time off or a holiday, spend time with loved ones, and we look forward to catching up with everyone in 2026!
The new offline Ava HD voice available for Windows 11 insiders in the Narrator #screenreader is...wild. Who...what...why? She wants so badly to be my friend and I hate it! I just want her to read the things on the screen. Why is she so smiley and happy? To be fair, all of the other natural voices for Narrator are nearly perfect. If they were just a bit quicker, and had fewer weird pauses, and worked with NVDA, they could almost replace eloquence.
The World #Blind Union General Assembly and World #Blindness Summit in São Paulo, #Brazil in September was an amazing opportunity not only to talk about NVDA, but to give a presentation on the amazing MOVEMENT behind the world's favourite free #screenreader! We have two videos of the presentation and a full transcript for you, complete with an audience-initiated chant of "#NVDA NVDA NVDA!" at the end!
As with any open source project, 64-bit eloquence wouldn't be possible without the community behind it. This release brings us the following:
fixes to indexes, and further code simplification (Tha...
If you saw our recent post on here about Reece, the young boy from Australia who got the ABC to put audio description on "Behind the News", then you'll love this follow up video he made especially about NVDA. It is THE feel-good piece to watch this holiday season!
Just discovered an incredible resource for accessible Bible study: World Bible Plans
As a totally blind, autistic, chronically ill Christian, finding tools that are both spiritually rich and screen‑reader friendly isn't easy. Their EPUB plans (like the World English Bible with David Guzik's commentary) have proper headings for navigation, built-in cross-references, and formatting that makes daily devotions possible without frustration.
I don't know if all their plans are accessible by default, so I suggest mentioning in the “additional requests” box that you're blind and need screen‑reader friendly formatting. That's what I did, and the result was excellent.
Also note that if you choose a Bible version that isn't in the public domain, the plan will only give you a guide showing which verses to read, not the full text.
If you've struggled with inaccessible study tools, this might be a game‑changer.
WBP offers custom-made free bible reading plans with scriptures and commentaries in your language
:
Custom-made specifically for you per your requirements
.
Do I understand correctly that Narrator is currently not available in the installer for #Windows11? Does this apply to the out-of-box experience, or only the bit before that? I.e. if I buy a computer with Win 11 already installed, will Narrator work for the setup? #accessibility #screenReader
I am working on some Gemini related stuff (the protocol, not Google AI) and would be interested in hearing about how Gemini stacks up from an accessibility perspective. Are there any specific clients or screen readers that work best? Is there any specific Gemini formatting that helps or hinders? Is there any accessible-specific content that you think should be made available via Gemini?
On a related note, am I wrong in thinking that Gemini is well suited to a low/no vision user? And if so, why?
This week's In-Process is a bumper one - but don't miss it because as well as all the news on NVDA 2025.3.2, more on configuration profiles and the NEW Web interface for the add-on store, we've also got a BLACK FRIDAY SALE!
Ok, so this is another of those weird questions which I post because people here use their brains more than most. I want to have one NVDA Remote client control two machines at the same time. That is, I want my laptop to control my desktop and my second desktop, but I want both desktop1 and desktop2 to have their NVDA heard through the laptop at the same time. I also want to switch back and forth between the two machines, as well as to and from the laptop itself, with a keystroke. There are two solutions I've found for this, but both are a bit of a mess. I can use thenvdaremote:// URLs to disconnect from desktop1 and connect to desktop2 with one keystroke, and have another keystroke to do the reverse. The problem there is that I can't hear both machines' NVDA at the same time. Also, and this isn't as big a deal, I'm just a perfectionist, switching takes a few seconds. Secondly, I can run a virtual machine and have that connected to desktop2, with the host machine connected to desktop1. That allows easy switching of the keyboard, just alt+tab to the VM window and hit ctrl+g when I want to control desktop2. It also allows both desktops to have their NVDA run through the speaker at the same time and also, which is very nice, allows braille to swap with any display which supports channels. The problem there is the latency of the VM audio, which I can't seem to shrink. It seems a bit overkill, I may say, to run an entire windows OS just for NVDA remote in a VM. Does anyone have any better solutions. Can anyone think of something which would get all three things running, fast switching, simultaneous NVDA, and no latency? Ideas would be very gratefully received and boosts would be appreciated. #NVDA #blind #a11y #screenreader #remote #nvdaremote
Yesterday an open-source developer Christian has released life changing update to the privacy respecting #android app called #MakeACopy. The app now features so called #accessibility mode that is enabling #screenReader users to take pictures of the paper documents independently. Accessibility guide is available on github. The latest prerelease version provides clear Accessibility guidance phrases with screen readers such as Talkback, Corvus, Jieshuo and others that can handle announcement accessibility event.
I am verry happy about this. We are now getting privacy respecting open-source based screen reader accessible solution that performs very well and is easy to use.
MakeACopy is an open-source document scanner app for Android that allows you to digitize paper documents with OCR functionality. The app is designed to be privacy-friendly, working completely offli...
NV Access is pleased to announce that version 2025.3.2 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.
Who here uses manual configuration profiles in NVDA? What do you use them for? Do please let us know!
And if you're not sure what configuration profiles are all about, check out the recent In-Process blog, which covered them: nvaccess.org/post/in-process-1…
Question for the fediverse tech folk: work has asked me to learn Google’s Big Query. Does anyone know how #accessible it is with a #screenreader? And where is the best place to start for someone mostly familiar with small scale postgresql deployment? #bigquery
This week's In-Process blog post is out! Featuring: - NVDA 2025.3.1 - Reece gets Behind the News with Audio Description - Manual configuration profiles - Featured add-on: “Check Input Gestures” - Bonus tip: Report keystroke
I've said it before, but it's disappointing when small things let down the #accessibility of an otherwise good interface.
For instance, I've told many people that the Tailscale web UI is actually quite good with a #screenReader. Unfortunately, the first thing an NVDA user hears after authenticating is a bunch of nonsense caused by an unlabelled SVG, and it doesn't create the best first impression:
" banner landmark visited link graphic graphic visited link graphic graphic visited link graphic graphic visited link graphic graphic visited link graphic graphic visited link graphic graphic visited link graphic graphic visited link graphic graphic visited link graphic graphic "
Hey guys. I hope you’re all doing well. So, I’m using #Abletonlive12 with a #Screenreader, which works quite well. However, there’s very little information to help those screen reader users getting started, and I’m worried about falling behind on my work as a result. I’ve also run into another problem. It seems as though an upcoming module in my degree requires that you have ableton sweet. I managed to get myself up to standard, but with all the expenses I’ve had to pay including for university I wasn’t able to afford suite even with a 50% discount. Is there some sort of Beta program that I can join that would allow me to upgrade to suite for free in return for giving them feedback?
So ...there's various situations where .NET UI #accessibility just isn't as automatic as it should be. Loads of times I see perfectly good label texts within buttons, listItems, etc. that for whatever internal reason isn't actually the button's #accessible name. This has been a problem for close to twenty years now and I doubt #microsoft is ever going to fix it, so I had a crack at it. All the disclaimers apply, this is mostly just a thing I wrote for myself and I figured it might be helpful to some: github.com/zersiax/dotnet_fix If you have to use .NET apps that seemingly have a bunch of unlabeled buttons, but object navigation reveals text inside, this might help some. No guarantees, and if it breaks you get to keep both pieces :P #foss #NVDA #screenReader #blind
As a full-time #JAWS user who uses #NVDA only for testing and when JAWS really can't cope with an element, I simply didn't think about this issue but now it makes me laugh and cringe at the same time, as it was raised in a YouTube stream about NVDA I've recently seen. In JAWS, when you script something, you may assign a keystroke to your scripts, and as soon as you do that, JAWS will warn you about a conflict if the keystroke has already been assigned. In NVDA however, if, say, user A develops an addon that does a thing and assigns Ctrl+Insert+1 to it, then user B develops another addon that does another thing, an absolutely different one, and assigns Ctrl+Insert+1 to it also, guess what happens when user C installs both? Hold your breath… It's random! Apparently, the addon installed later overwrites the keystroke, but you as an end-user press a key, expecting, metaphorically, to get a cup of cappuccino, but you get all your windows in the whole house open, because NVDA doesn't warn devs that another addon has this key already assigned! And how can it, probably, since there are tons of addons? Anyway, I'm sure it's possible but, I mean… hahahaha (sorry). And guess what? There is another addon that allows you (as an end-user!) to check duplicates and reassign whatever you need. Phew! I mean… no comments, other than splendors and miseries of #OpenSource (yes, I know, you're mad at me, I repeat this phrase every day, but I will do it more, as it expresses the state of things perfectly). #Accessibility #ScreenReader
Switching to #NVDASR #ScreenReader in December 2022 from a paid solution was one of the best accessibility choices I've made in my entire life. That is all.
The thing about JAWS vs NVDA is that it doesn't matter if @freedomscientific packs it with objectively better features. NVDA is free, easy to use (within the context of desktop screen readers), and it's good enough for the vast majority of screen reader users. Want to browse the web? Want to check your email? Need to type up an assignment? Need to track data with spreadsheets? Want to write some code? Want to run virtual machines? Just wanna keep up with your communities on Discord? Want to test your app for accessibility? NVDA can do all of those things. There is no faffing, no caveats, no running obscure commands, and no license to install. You download it. You install it. You run it. That's it. Want it to do more stuff? Open the addon store which is built into NVDA. If you know Python, you can write your own addons and share them with other users. FS is relying on organizations like schools and governments where paying hundreds and hundreds of dollars is normal and expected and you can't just install an addon to an existing app. This does not work outside of those organizations. The blind kid who wants to listen to memes and keep up with their friends doesn't have several hundred dollars per year, but they probably know that they can go download a free screen reader that will let them listen to memes and keep up with their friends. NVDA is winning because it's good enough for most people and costs nothing. If you do have the money to spare for a license and you want to use JAWS because you prefer it, that's fantastic! I'm glad you found a screen reader that you like. Most people will choose the free option because they just wanna listen to their favorite streamer while they type up their research paper. #blind #AccessForAll #ScreenReader #nvda #jaws #jaws26
How is the state of PDF #accessibility on macOS for #screenReader users? If I gave someone a PDF that was prepared in a fully #accessible way, what would they use to read it with #VoiceOver, and to what extent would the accessibility be retained?
Note that I'm specifically not interested in applications that strip out all of the text to essentially make a plain version. Those can be useful when you just need to read something and don't care how, but the degree to which accessible semantics like headings, tables, lists, etc. are kept at that point is usually zero.
I'm also not asking about applications that reinvent the accessibility for PDFs and ignore what's already there, as many browsers do.
NV Access is pleased to announce that version 2025.3.1 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.
This is a patch release to fix a security issue and a bug.
It is a shame how little control #WebDevelopers have over the #ScreenReader user experience. Blind folks are getting the audio version of the black text on white background experience, without any design or flair.
This is a perfect example of how nebulous #screenReader #accessibility is, and why it confuses so many laymen. I am looking at a web page right now that has a "Download" button. The button is an a (anchor) tag, with a div inside of it with the CSS class for a download button. Obviously this is awful HTML, but it works fine, if you can see. There's a big fat button with "DOWNLOAD!" in all caps on the screen. Clicking this button starts the download. Seems good, no? Well, no. This div has no actual textual content, and the anchor tag has no href or text either. So this huge honking button is entirely invisible to screen readers. How do I even begin to explain this to, say, a customer support rep? :)
The Zed code editor is now available for Windows. To save anybody else wasting their time trying it with a #screenReader, it isn't #accessible so don't bother. #accessibility
while I'm at the topic of #screenreaders - just found out NVDA is a project by 'NV Access' - an Australian non-profit that develops NVDA as a free, open source screen reader for WIN nvaccess.org/download #screenreader #thanksguys
OK #Blind #Linux people, is it really worthwhile to consider dual booting @elementary or at least testing it out in a VM? I’m probably not going to be able to give up windows completely, correct? What can I do natively under Lennox and what can’t I do? How is word processing, spreadsheets, making presentations? How about editing music notation? what works, what doesn’t, and what am I going to be giving up in terms of time and efficiency? Boosts appreciated and input very much welcome. #BlindMasto #BlindMastodon #BlindFedi @mastoblind @blind #OpenSource #ElementaryOS #ScreenReader #Accessibility #A11Y
Shower thought: I wonder if any #blind kids today are growing up on espeak the way we grew up on eloquence? Is there a future where espeak is out of date and ancient, and people are clinging to it with the desperation people today cling to eloquence and dectalk? Honestly y'all, espeak read isn't that bad. I just wish espeak was usable on IOS; the available app is old and littered with bugs. #a11y#screenreader#accessibility
Are you in Adelaide today? Come down to U-City where See Differently are hosting Tech Fest. There are lots of organisations here with everything to help you make the most of your tech - including James and Quentin from NV Access!
Section508.gov is the official U.S. government resource for ensuring digital accessibility compliance with Section 508 of the Rehabilitation Act (29 U.S.C. 794d).
I just learned that I need to put alt text on URLs for more accessible PDFs, but -- what should it say?
I am formatting academic citations that include a URL, so all the information about where that link will take you is in the text. I don't want it to read the URL to you and I don't want to just repeat the same information you just heard. What do you find most helpful in this situation?
