NVDA: The Free Screen Reader Built in the Open

Screen readers have historically been paid, closed-source software, licensed like enterprise tools rather than sold like consumer apps. NVDA — NonVisual Desktop Access — is the opposite bet: a free screen reader that's open source and built for Windows, with its entire codebase, license, roadmap links, and issue tracker sitting in public on GitHub for anyone to inspect.

That's the actual story worth checking, not taking on faith: does an accessibility tool built in the open, by a small team plus volunteers, actually hold up as a real, maintained product? Its own repository answers that in specifics — release dates, open issues, license terms — rather than marketing copy.

What NVDA's screen reader is, in the project's own words

NVDA's product vision statement states the goal plainly: "A world where blind and vision impaired people can independently and fully interact with the Windows Operating System and popular third party applications."

It works by converting what's on screen into synthetic speech or output to a refreshable Braille display. The same document frames that access as something every blind and vision impaired person deserves, no matter the language they speak, their geographic location, economic status, or sensory, physical, cognitive, or mental abilities.

It's developed by NV Access, an organization based in Australia whose GitHub profile describes its mission as "Empowering lives through non-visual access to technology," working alongside what the project's README calls "a global community of contributors."

The license is the business model

NVDA ships under a modified GNU General Public License version 2 or later. The GPL means anyone can copy, study, and redistribute it, but any distributed version has to stay free and under the same license — the mechanism that keeps NVDA from being forked into a closed, paid product by someone else.

Two carve-outs make that workable in practice. Third-party plugins can bundle non-GPL components as long as they don't interact with NVDA outside the plugin itself, and specific Microsoft runtime files needed to run on Windows can ship without being forced under GPL. Nothing in the license text blocks commercial use — you can charge for distributing NVDA or for support — the actual restriction is that whoever you give it to keeps the same freedoms you had.

It's still shipping, not abandoned

An open-source accessibility tool is only as good as whether it's still maintained, so it's worth checking the releases page directly rather than trusting a claim. The most recent stable build is 2026.1.1, published May 20, 2026. Behind that, the project has been publishing a steady chain of betas toward the next stable — 2026.2beta11 went out August 17, 2026, four days before this was written, following beta10, beta9, and so on back through June.

The main repo itself carries 25,692 commits on its master branch, roughly 2,200 open issues, and 18 open pull requests as of this check (GitHub rounds the issue and star counts on its own UI, so treat those two as approximate) — the profile of an actively used, actively triaged project, not a dormant one. On the organizational side, NV Access's GitHub org lists 36 public repositories and 246 followers, with the core nvda repo alone at roughly 2,600 stars.

The ecosystem around the core app

NVDA isn't just one repository. NV Access maintains a separate pipeline for its Add-on Store, which the repo describes as "a data pipeline for submitting and validating add-on data."

Submitters have to be manually vetted and approved by NV Access, and submissions get SHA256 checksums and a VirusTotal scan. But — notably — NV Access does not manually audit the code of every add-on, and it says plainly that add-ons are "run at user's own risk." The store is also non-exclusive: authors can distribute their add-ons outside it too.

Remote assistance is built in rather than bolted on: NV Access describes the remote-server repo as the relay server behind NVDA's built-in remote access functionality — the infrastructure behind NVDA Remote, which lets one NVDA session connect to another over a network.

Speech itself is also something NV Access builds rather than only licenses. NVSpeechPlayer is a Klatt-based speech synthesis engine the project describes as "a free and open-source prototype speech synthesizer that can be used by NVDA," positioned by its own README as an alternative to Klatt-based commercial synthesizers like Dectalk and Eloquence — which, per the same README, have become harder to get over the years, with multiple companies having end-of-lifed them.

Localization is broad but not infinite: NVDA's source/locale directory lists dozens of language folders, from Afrikaans through Korean and Chinese variants — real, browsable proof of multilingual support rather than a marketing claim.

Where it's honestly thin

Not everything NV Access ships stays maintained. nvda-ocr, an add-on for extracting text from otherwise-inaccessible interface elements, was archived by NV Access on November 2, 2023, and is no longer maintained under that repository — a reminder that "open source" doesn't mean every side project survives, even inside the org that owns the flagship tool.

More structurally, NVDA is built specifically for the Windows Operating System — there's no NVDA build for macOS or Linux, so its independence from any one paid vendor doesn't extend to independence from one operating system. And the Add-on Store's own documentation is upfront that the vetting process is submitter-approval plus automated scanning, not a manual code review — which means the trust model for third-party add-ons rests more on NV Access's gatekeeping than on any guarantee that every add-on's code has been read by a human.

What this generalizes to

The interesting thing about NVDA isn't that it's free — plenty of software is free. It's that every claim in this piece was checkable in the same place the software itself lives: the license terms, the release cadence, the open issue count, even which side projects got archived. For a category where impact claims usually come from a company's own press page, that's a different kind of accountability. The same GitHub-native maintenance signals — commit history, issue counts, release dates — that let you check whether a gamified habit app is actually still alive work just as well for checking whether an accessibility tool that blind and low-vision Windows users depend on is still being taken care of.

If you're evaluating any assistive technology, that's the practical takeaway: don't just read the vision statement — check the same repo for a shipping release in the last few months and an issue tracker that's actually being worked, the way NVDA's is.