Pratik Patel38m 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.

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 Access2d 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 Lee2d ago
@NVAccess @agowa338 As a workaround, you can use #NVDASR hashtag instead to clealry differnetiate the screen reader versus a big tech company.
NV Access4d ago

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
FlorianMar 11
Hot #screenReader take: I'll take #VoiceOver's "busy busy busy" over #NVDAsr's "oh god, too much text, baiiii!" any day. Absolutely not just NVDA's fault, bit of a product of NVDA + Python + Windows APIs + no doubt a bunch of other things but if I get a "whatever you're trying to do, stop it and return to nominal" button for NVDA for 2026.2 that alone would make me update in an instant. Particularly working with large amount of commandline input is a disaster with this problem occurring practically every few minutes, but other random things, like landing on a window that's hanging or not responding, will do it as well, and if it's the 20th time on a day it can get pretty aggression-inducing.
kaveinthranMar 10
Anyone uses the favourite links #nvda add-on here? I would like to reach out to someone that can spend some time with my pull request number 41 and 42 as I'm really struggling with it. I've explained on the pull request review and the comment on what I'm trying to do. If anyone can look at my code and either fix it or suggest some improvements, it would be really great. Of course, no worries if you couldn't do it. I'm just trying to reach out in case anyone got some free time and available energy to work on this as I'm not a coder and I am working with AI assistance.
https://github.com/EdilbertoFonseca/favoriteLinks/pull/42
#coding #Blind #screenReader #vibeCoding #NVDASR
Pratik PatelMar 10

@NVAccess posted:

In-Process 10th March 2026

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

#NVDASR #accessibility

NV Access | In-Process 10th March 2026