Rui Batista13h ago
If anybody is interesting at a Rust port of the #nvdasr remote relay here it is, in need of user testing: https://github.com/ragb/nvda-remote-server-rs I know nobody needs and asked for it but has I had this code around....
GitHub - ragb/nvda-remote-server-rs

Contribute to ragb/nvda-remote-server-rs development by creating an account on GitHub.

GitHub
NV Access21h ago

NVDA 2026.1 Beta 8 is now avaialble from https://www.nvaccess.org/post/nvda-2026-1beta8/

Changes since Beta 7:
- Fixed the “Speech style” setting in Math settings being empty when using languages other than English.
- Updates to translations.

See the release announcement for the full highlights of NVDA 2026.1

#NVDA #NVDAsr #ScreenReader #NewVersion #Update #PreRelease #FOSS #FLOSS #Free #News

Show threadPratik Patel1d ago

Terminal Access for NVDA updated to 1.4.0. New features: error/warning audio cues with word-boundary regex detection, output activity tones, profile selection dialog, search results dialog, gesture scoping (terminal-only activation), and enhanced bookmarks with line labels.

Settings panel reorganized with Audio Cues section. Gesture conflicts checklist shows only NVDA-conflicting gestures. Terminal detection uses exact process name match.

https://github.com/PratikP1/Terminal-Access-for-NVDA/releases/tag/v1.4.0

#accessibility #NVDA #NVDASR

Release V1.4.0 · PratikP1/Terminal-Access-for-NVDA

Major refactoring and feature release. Main plugin reduced from 9,590 to 3,890 lines with 12 extracted lib modules. 1,073 tests passing. New features: error/warning audio cues with word-boundary re...

GitHub
Pratik Patel3d ago

Would there be any interest in Having the KittenTTS voices integrated as an NVDA add-on? before I do the work, I want to know whether people are actually interested. This sounds like an interesting project. The voices are ML based but they use the CPU for processing.

Turns out @fastfinge has already done an early version of it. I might look at the code but sounds like it's not worth the time.

https://github.com/KittenML/KittenTTS
#accessibility #NVDA #NVDASR

GitHub - KittenML/KittenTTS: State-of-the-art TTS model under 25MB 😻

State-of-the-art TTS model under 25MB 😻 . Contribute to KittenML/KittenTTS development by creating an account on GitHub.

GitHub
Show threadNV Access5d ago
@joslee #NVDAsr was really only used as a last resort on Twitter because all the crypto scammers took over #NVDA. Here is much cleaner, and the thing is if you are a financial person interested in NVIDIA, you really won't find much by searching for #NVDA - you'll find what you want with #NVIDIA which doesn't have any alternate meanings.
Show threadJoseph Lee6d ago
@NVAccess @agowa338 As a workaround, you can use #NVDASR hashtag instead to clealry differnetiate the screen reader versus a big tech company.
NV AccessMar 16

What did you think of our article about add-on development and AI in last week's In-Process newsletter? Did we cover the main points? Did we miss anything? If you are visual and into graphics, what did you think of our AI-generated image?

https://www.nvaccess.org/post/in-process-10th-march-2026/

#NVDA #NVDAsr #Newsletter #Addons #Ecosystem #Development #FOSS #FLOSS #Contributing

Joseph LeeMar 13
To #NVDASR community: please, PLEASE don't just use an AI system to submit pull requests:
https://github.com/nvaccess/nvda/pull/19787
1/
kaveinthranMar 12
@doubletap covered the Difficulty that's hitting InnoSearch hard. Just to look back at history, in around January 2011, @NVAccess folks posted a very similar note on their blog that's now archived. At that time, #NVDA lacked funding and ability to fund and pursue the project beyond July 2011.
here's extract
"Jamie and Mick, the core developers of NVDA, are essentially paid minimum wage for their experience, knowledge and skills, which they are prepared to accept because they love the fact that they are making a positive contribution to the blind community and the accessibility industry more generally. Despite their willingness to carry on, however, there will be no money to pay them after July 2011 unless we receive some financial assistance." #nvdasr
I've elaborated more here. https://disabled.social/@kaveinthran/115585944542499774
Kaveinthran (no longer here) (@[email protected])

@[email protected] @[email protected] @[email protected] I found the post when exactly this financial difficulty hits them hard, it's on the archive.org and dated Jan 2011 https://web.archive.org/web/20110207173859/http://www.nvaccess.org/blog/NVDANeedsYou

disabled.social
kaveinthranMar 12

@doubletap the most recent @AccessOn @nfb.social episode is packed with #NVDA vibes, featuring 3 core people from the org talking about the #screenReader.

I hope you can get into at least one of the talking points there - specifically about patents in the screen reader world.

What happens if NVDA copies features already patented by other screen reader vendors? Or if add-on authors replicate features that other screen reader script authors have worked on for years and built their bread-and-butter livelihood around?
FYI, They also covered quite a bit on the things you often touched on, the relationship between open source and security.
https://accesson.pinecast.co/episode/ec320614/nvda-in-the-past-present-and-future
#Blind #jaws #pattent #accessibility #nvdasr

NVDA in the Past, Present, and Future

On this week's episode of Access On: Introduction 0:00 Looking ahead to next week's CSUN recap 0:53 Join us for our Access On seminar on Windows screen readers 1:56 NVDA past, present, and future 3:08 Closing and contact info 1:09:26

Access On