#nvdasr — Public Fediverse posts

Hi everyone,

The NVDA Satisfaction Survey 2026 is now open: https://www.nvaccess.org/survey2026

We are always interested in understanding the satisfaction of our NVDA users, what is important to you & what we can do more effectively. The survey is anonymous & we encourage you to add comments on the survey.

We're interested in hearing from as many people as possible, so please feel free to pass this on to others.

#NVDA #NVDAsr #ScreenReader #Survey #Accessibility #Feedback

New PR "Announce enclosing regions and groupings when focusing web applications" (#20854 by michaelDCurran)
https://github.com/nvaccess/nvda/pull/20854
#nvdasr-pr

New PR "Update dev doc for submodules management" (#20853 by CyrilleB79)
https://github.com/nvaccess/nvda/pull/20853
#nvdasr-pr

New PR "Add sync repo step before submitting WinGet PR" (#20851 by mdanish-kh)
https://github.com/nvaccess/nvda/pull/20851
#nvdasr-pr

Merged PR "Drop virtual buffer attributes with invalid XML names" (#20629 by akj)
https://github.com/nvaccess/nvda/pull/20629
#nvdasr-merged-pr

Merged PR "Reduce intermittent system test failures" (#20756 by LeonarddeR)
https://github.com/nvaccess/nvda/pull/20756
#nvdasr-merged-pr

NVDA 2026.3 Beta 2 is now available for testing! Changes from Beta 1 include:

- Updates to eSpeak and translations
- Fix Magnifier’s “Show screen overview”
- Improvements to alt+upArrow & alt+downArrow
- fix Magnifier colour filtering
- Update to the Chinese Word Segmentation

Read more & Download at: https://www.nvaccess.org/post/nvda-2026-3beta2/

#NVDA #NVDAsr #Update #Beta #NewVersion

NVDA 2026.3 Beta 2 is now available for testing! Changes from Beta 1 include:

- Updates to eSpeak and translations
- Fix Magnifier’s “Show screen overview”
- Improvements to alt+upArrow & alt+downArrow
- fix Magnifier colour filtering
- Update to the Chinese Word Segmentation

Read more & Download at: https://www.nvaccess.org/post/nvda-2026-3beta2/

#NVDA #NVDAsr #Update #Beta #NewVersion

NVDA 2026.3 Beta 2 is now available for testing! Changes from Beta 1 include:

- Updates to eSpeak and translations
- Fix Magnifier’s “Show screen overview”
- Improvements to alt+upArrow & alt+downArrow
- fix Magnifier colour filtering
- Update to the Chinese Word Segmentation

Read more & Download at: https://www.nvaccess.org/post/nvda-2026-3beta2/

#NVDA #NVDAsr #Update #Beta #NewVersion

NVDA 2026.3 Beta 2 is now available for testing! Changes from Beta 1 include:

- Updates to eSpeak and translations
- Fix Magnifier’s “Show screen overview”
- Improvements to alt+upArrow & alt+downArrow
- fix Magnifier colour filtering
- Update to the Chinese Word Segmentation

Read more & Download at: https://www.nvaccess.org/post/nvda-2026-3beta2/

#NVDA #NVDAsr #Update #Beta #NewVersion

NVDA 2026.3 Beta 2 is now available for testing! Changes from Beta 1 include:

- Updates to eSpeak and translations
- Fix Magnifier’s “Show screen overview”
- Improvements to alt+upArrow & alt+downArrow
- fix Magnifier colour filtering
- Update to the Chinese Word Segmentation

Read more & Download at: https://www.nvaccess.org/post/nvda-2026-3beta2/

#NVDA #NVDAsr #Update #Beta #NewVersion

Merged PR "Update valid tracked translations from Crowdin" (#20848 by github-actions[bot])
https://github.com/nvaccess/nvda/pull/20848
#nvdasr-merged-pr

New PR "Update valid tracked translations from Crowdin" (#20848 by github-actions[bot])
https://github.com/nvaccess/nvda/pull/20848
#nvdasr-pr

@xgebi That was why people started using #NVDAsr on Twitter. When we moved over here, I've been jumping on the bots posting about NVIDIA with #NVDA - though NVDA is their stock code, I have never seen a genuine human post about them using that & I would put money on no actual human has ever searched for them using NVDA rather than NVIDIA. The point of hashtags is to find related content, so if they stick to NVIDIA & we stick to NVDA, it lets each community find what they want without pollution.

I bundled my #NVDASR notification sounds plugin into an NVDA add-on and added a Settings GUI to configure it. It's not on the add-on store though. http://files.jantrid.net/notificationSounds.nvda-addon

Anyone else experience the stupid bug in #NVDASR 2026.x where sliders do not say custom values provided by an application but instead say the raw value of where it is? I see this in #Pubsplash when I get to the volume sliders for each device etc. It's pretty stupid if you ask me. NVDA 2025.3.3 does not do this, but I'm about to disable all add-ons and look into this further. The value is "20" for "100%" if the volume is boosted and so on. It's really annoying.

New PR "Change log fixes" (#20847 by CyrilleB79)
https://github.com/nvaccess/nvda/pull/20847
#nvdasr-pr

Quite a few apps now, including web apps, can deliver standard Windows notifications, but many of them don't allow you to configure custom sounds for specific notifications; e.g. messages from specific people. During long work meetings or when I'm deeply focused, it's either not feasible for me to check each notification or the notifications all just become noise that I end up ignoring. I got sick of missing the doorbell or important messages from my wife in those situations.
So I wrote a hacky #NVDASR global plugin to search for regular expressions in incoming notifications and play the sound associated with the matching expression. It's configured with a simple tab separated notificationSounds.conf file in the NVDA configuration directory. For example:
doorbell pressed C:\sounds\doorbell.wav
If anyone's interested, here's the plugin. I can't be bothered developing a GUI, polishing it and distributing it as a proper add-on. You'll need to put this in the developer scratchpad. If you don't know what that is, probably best to ignore this.
https://gist.githubusercontent.com/jcsteh/803c16cf8d46e3bddda77c17eddac7c0/raw/cf73b66bc1695a4a1727d9315400edefbbe8c84d/notificationSounds.py

Speaking of git-related things, GitHub's PR stacks are kinda cool, but the CLI extension for them absolutely sucks. It's a horrible TUI thing that depends heavily on colour to communicate state. It doesn't move the caret at all to communicate focus or the actual text insertion point, so using it with a screen reader is very much a game of guessing what's interactive, reading text formatting, performing an action, then repeating to see if you achieved what you wanted to.
And the CLI commands it does support are extremely lacking. The most accessible way I've found to create a PR stack is to manually create a chain of PRs, then use the website to link them into a stack.
Curious if anyone knows of a more accessible way of using them.

#github #accessibility #a11y #screenreader #nvda #nvdasr #commandline #cli