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?
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.
As the premier free screen reader, #NVDA is very pleased to be trending in South Africa! Thank you to all our South African users, we do appreciate you! We understand the burden commercial software places on #blind users around the world and are glad to be the alternative! If you are new to screen readers, you can find out more about us at: nvaccess.org/
A brief overview of some of the things NVDA can do. The video demonstrates the screen reader at work in several programs and using different synthesizers (i...
Question to the people experienced with Screen readers: I'm currently writing a documentation where I insert lots of inline Screenshots, for example a little red cross. What would be the preferred way of writing Alt-Text for them? Usually I describe Images in a clear sentence, but I assume for inline screenshots it would make more sense to use a Single Word if possible. #accessibility #question #screenreader
We are pleased to announce we have rolled out a new, more intuitive issue template for reporting bugs or requesting features in NVDA. The form is still on GitHub & still requires the same information as previously, but now uses individual fields rather than one long edit box with comments. You can explore here (Note it IS live so if you submit an issue, it will be submitted as an actual issue): github.com/nvaccess/nvda/issue…
The NVDA 2025.3 Release Candidate is now available for testing. We encourage all users to download this RC and provide feedback. Unless any critical bugs are found, this will be identical to the final 2025.3 release.
This release includes improvements to Remote Access, SAPI5 voices, braille and the Add-on Store.
Question for fellow #NVDA users: why has the Office Desk addon been discontinued? I saw the message from the addon itself and read the homepage. It says it has been discontinued and that I should uninstall it, but it doesn't give a reason for it. I'd understand if it said something like, "The features in this addon have been merged into the core," or something like that, but it doesn't. #Accessibility #Blind #ScreenReader
Here's what a #Anker email looks like to my #ScreenReader today. Isn't it just full of excitement, expectation and complete and total understanding?
'1 1 3 4 5 6 1 1 1 1 11
Facebook Icon Youtube Icon Instagram Icon Twitter Icon Twitter Icon linkedin Icon discord1 Icon anker logo ankerwork logo ankermake logo soundcore logo eufy logo nebula logo US only.'
To NVDA users: Is anyone else having a problem with the NVDA+D keystroke to read additional details on something. Specifically, I went and tried to read the long description on a table in Word and while the long desc was in the description field, the file was a .docx, I am using 2025.2 of NVDA, Word365, and nothing I have tried returns anything but "No Additional details." Just reaching out in case there is something I missed. Tagging the professionals too. NVAccess@fosstodon.org #NVDA #screenreader #word365
NVDA 2025.3 Beta 1 is available for testing! Improvements to Remote Access, SAPI5, Braille, Add-on Store, and more! Read the full update and downloaad from: nvaccess.org/post/nvda-2025-3b…
