in reply to Mister Krabs

1/n Thanks for your feedback! We do genuinely appreciate you tagging us so that we can respond. I have taken the time to consider each of your points. Please find responses below.

As mentioned by others, Remote Access has been regularly requested by users. All reports are that it works quite well, and we have ironed out several issues for NVDA 2025.2, but if you are aware of any still present, please do let us know.

in reply to NV Access

2/n And if you don't want to use it, know that it is disabled by default, so doesn't impact your use of NVDA in the slightest. In terms of the work importing it, while we did contribute to it, a lot of the work was done by the original NVDA Remote add-on author. That is one of the beauties of being a community-driven, open-source project, and also why we often DON'T prioritise importing add-ons over adding completely new features (or fixing bugs).
in reply to NV Access

4/n
If having NVDA able to describe images without alt text is of no interest to you, then again, you will be able to avoid using that feature.

Out of 33 points on that page, only THREE involve AI and at least two of those are blue-sky ideas for well in the future. I'm not sure where filling NVDA with AI bloat is? (For comparison, have you looked at MS Office lately?). Collecting ANONYMOUS data will help us prioritise the features YOU the users request.

in reply to NV Access

6/6
We know users in general are also interested in any information we collect & we will be sure to share this in our blog (sign up at nvaccess.org/newsletter ) and likely here on social media. Again, can you find the same information for many of the other programs you use?

Finally, if you do have specific concerns with anything on our roadmap, or any NVDA features, please do let us know. NVDA continues to be, as it ever was, a community driven project & we thrive on feedback.

<end>

in reply to NV Access

@NVAccess Thanks for your response. AI and image recognission (Especially on-device) as well as remote, is great. I'm glad that they're optional and disabled by default. However, the point I'm trying to raise, and that people don't seem to be getting, is why add these to the core codebase when they could be addons just like so many other features? Especially for users on low-resource devices which NVDA has historically served better than JAWS, app size is very important.
Over the years, JAWS has grown to be insanely bloated. The install takes 20-30 minutes, even using a good internet connection with a fast computer. Part of the reason for this is that a lot of the features that aren't exactly things that could be considered core are in the core codebase. The NVDA installer is still quite small, (30-50 MB last I checked). Maintaining a quick and simple download and installation process and a more basic default feature set would improve user trust. All addon code is publicly available, and the addon store provides an extra layer of security for companies and individuals with privacy concerns.

I have the same view of AI regardless of the project. If AI can be an optional feature, via an addon or other method, I support it. I'm not unfairly going after NVDA here, MS offices' decisions regarding AI are awful for many reasons and I've spoken about that at length before, on and off of social media.

Also, regarding the collection of user data. A lot of companies hide the information they collect on their users, but that doesn't make unnecessary data collection acceptable. There are plenty of public forums where you can accept feedback. Just use those. There's no need for telemetry here.
I hope this helps to get us on the same page.

in reply to Mister Krabs

With Remote, adding that to core allows us to add extra security to it which wasn't possible as an add-on. I just looked at my portable versions. 2025.1.2 takes up 213MB compared to 217MB for 2024.4.2, so it's actually SMALLER. And if you don't use it, it doesn't use any other resources.

With AI image recognition, we are still exploring how that even works, and no decision has been made regarding implementation - certainly size will be a consideration. Thanks for asking!

in reply to Sean Randall

@jpellis2008 I don't recall JAWS being anywhere near as transparent about security when they launched picture smart. or it was probably part of a podcast nobody has the time to listen to.
Obviously Picture Smart is not an on-device service and goes out to GPT just like be my eyes does, but the wording even in the roadmap from Nv Access shows that privacy and security are preplanned, not afterthoughts.
in reply to Scarlet Phoenix Collective

@the_spc We're glad to be your gaming go to :) Assuming you otherwise use our main competitor, here's a handy guide to switching from one to the other, just in case you hadn't already seen it: github.com/nvaccess/nvda/wiki/… - re Remote, no fiasco we've ever heard about - it's a feature (similar to Jaws Tandem, I gather?) which used to be an add-on. It's disabled by default, so if people don't want to use it, they don't need to do anything at all :)
in reply to Scarlet Phoenix Collective

@the_spc If you've got access to both and one works better in one situation then go for it. If there is anything NVDA specifically lags in we could improve, please do let us know!

And I wasn't sure whether you meant you need Jaws for a specific job search (site?) or whether you feel you need it for work - but we do have information for employers / companies in setting up NVDA: nvaccess.org/corporate-governm…

And we are happy to answer any questions an organisation may have about NVDA :)