NVDA (NonVisual Desktop Access) is a free, open source screen reader for Microsoft Windows. It is developed by NV Access in collaboration with a global community of contributors. To learn more about NVDA or download a copy, visit the main NV Access website.
Please note: the NVDA project has a Citizen and Contributor Code of Conduct. NV Access expects that all contributors and other community members read and abide by the rules set out in this document while participating or contributing to this project.
Either if you are a beginner, an advanced user, a new or a long time developer, or if you are an organization willing to know more or to contribute to NVDA, you can get support through the documentation in place as well as several communication channels dedicated for the NVDA screen reader. Here is an overview of the most important support sources.
- NVDA User Guide
- NVDA Developer Guide
- NVDA Add-ons Development Internals
- NVDA ControllerClient manual
- Further documentation is included in the Wiki of this repository and in the Community Wiki
- NVDA Users Mailing List
- NVDA Developers Mailing List
- NVDA Add-ons Mailing List
- Instant Messaging channel for NVDA Support
- Other sources including groups and profiles on social media channels, language specific websites and mailing lists etc.
You can also get direct support from NV Access. See the NV Access website for more details.
Other Key Project Links
- NVDA on GitHub
- NVDA issues on GitHub: Bug reports, feature requests, etc.
- NVDA development snapshots: Automatically generated builds of the project in its current state of development
- NVDA add-ons: Get add-ons to enhance NVDA
- NVDA Add-ons coordination and support center: all about NVDA's addons environment
- NVDA Add-ons Template: A repository for generating the Add-ons template
- Translating NVDA: Information about how to translate NVDA into another language
- NVDA Controller Client (2010-02-19): NVDA API for external applications to directly speak or braille messages, etc.
- Contributing to NVDA: Guidelines for contributing to the NVDA source code
- NVDA commits email list: Notifications for all commits to the Git repository
- Old email archives: contain discussions about NVDA development
Getting the Source Code
The NVDA project uses the Git version control system for its source code and documentation.
The NVDA Git repository is located at https://github.com/nvaccess/nvda.git. You can clone it with the following command, which will place files in a directory named
git clone --recursive https://github.com/nvaccess/nvda.git
--recursive option is needed to retrieve various Git submodules we use.
The NVDA source depends on several other packages to run correctly.
The following dependencies need to be installed on your system:
- Python, version 3.7, 32 bit
- Use latest minor version if possible.
- Don't use
3.7.6it causes an error while building, see #10696.
- Microsoft Visual Studio 2019 Community, Version 16.3 or later:
- Download from https://visualstudio.microsoft.com/vs/
- When installing Visual Studio, you need to enable the following:
- On the Workloads tab
- in the Windows group:
- Desktop development with C++
- Then in the Installation details section, under Desktop for C++, Optional grouping, ensure the following are selected:
- MSVC v142 - VS 2019 C++ x64/x86 build tools
- Windows 10 SDK (10.0.19041.0)
- C++ ATL for v142 build tools (x86 & x64)
- C++ Clang tools for Windows
- in the Windows group:
- On the Individual components tab, ensure the following items are selected:
- MSVC v142 - VS 2019 C++ ARM64 build tools
- C++ ATL for v142 build tools (ARM64)
- On the Workloads tab
Most of the dependencies are contained in Git submodules.
If you didn't pass the
--recursive option to git clone, you will need to run
git submodule update --init.
Whenever a required submodule commit changes (e.g. after git pull), you will need to run
git submodule update.
If you aren't sure, run
git submodule update after every git pull, merge or checkout.
For reference, the following run time dependencies are included in Git submodules:
- comtypes, version 1.1.7
- wxPython, version 4.0.3
- eSpeak NG, version 1.51-dev commit 1fb68ffffea4
- Sonic, commit 4f8c1d11
- IAccessible2, commit cbc1f29631780
- ConfigObj, commit f9a265c
- Six, version 1.12.0, required by wxPython and ConfigObj
- liblouis, version 3.15.0
- Unicode Common Locale Data Repository (CLDR) Emoji Annotations, version 38.0
- NVDA images and sounds
- Adobe Acrobat accessibility interface, version XI
- Adobe FlashAccessibility interface typelib
- MinHook, tagged version 1.2.2
- brlapi Python bindings, version 0.8 or later, distributed with BRLTTY for Windows, version 6.1
- lilli.dll, version 220.127.116.11
- pySerial, version 3.4
- Python interface to FTDI driver/chip
- Java Access Bridge 32 bit, from Zulu Community OpenJDK build 13.0.1+10Zulu (13.28.11)
Additionally, the following build time dependencies are included in Git submodules:
- Py2Exe, version 0.9.3.2 commit b372a8e
- Python Windows Extensions, build 224, required by py2exe
- txt2tags, version 2.5
- SCons, version 4.0.1
- Nulsoft Install System, version 2.51
- NSIS UAC plug-in, version 0.2.4, ansi
- xgettext and msgfmt from GNU gettext
- epydoc, version 3.0.1 with patch for bug #303
- Boost Optional (stand-alone header), from commit 3922965
To lint using Flake 8 locally using our SCons integration, some dependencies are installed (automatically) via pip. Although this must be run manually, developers may wish to first configure a Python Virtual Environment to ensure their general install is not affected.
The following dependencies aren't needed by most people, and are not included in Git submodules:
To generate developer documentation for nvdaHelper: Doxygen Windows installer, version 1.8.15:
When you are using Visual Studio Code as your integrated development environment of preference, you can make use of our prepopulated workspace configuration for Visual Studio Code. While this VSCode project is not included as a submodule in the NVDA repository, you can easily check out the workspace configuration in your repository by executing the following from the root of the repository.
git clone https://github.com/nvaccess/vscode-nvda.git .vscode
Preparing the Source Tree
Before you can run the NVDA source code, you must prepare the source tree. You do this by opening a command prompt, changing to the root of the NVDA source distribution and typing:
You should do this again whenever the version of comtypes changes or language files are added or changed.
Note that if you want to access user documentation from the help menu while running the source version, you will also need to add
user_docs to the command line like so:
scons source user_docs
While simply testing or committing changes, it may be faster usually just doing
scons source as user documentation will change each time the revision number changes.
Compiling NVDAHelper with Debugging Options
Among other things, preparing the source tree builds the NVDAHelper libraries.
If trying to debug nvdaHelper, you can control various debugging options by building with the
nvdaHelperLogLevel command line variables.
nvdaHelperLogLevel variable specifies the level of logging (0-59) you wish to see, lower is more verbose. The default is 15.
nvdaHelperDebugFlags variable takes one or more of the following flags:
- debugCRT: the libraries will be linked against the debug C runtime and assertions will be enabled. (By default, the normal CRT is used and assertions are disabled.)
- RTC: runtime checks (stack corruption, uninitialized variables, etc.) will be enabled. (The default is no runtime checks.)
- analyze: runs MSVC code analysis on all nvdaHelper code, holting on any warning. (default is no analysis).
The special keywords none and all can also be used in place of the individual flags.
An example follows that enables debug CRT and runtype checks
scons source nvdaHelperDebugFlags=debugCRT,RTC
Symbol pdb files are always produced when building, regardless of the debug flags.
However, they are not included in the NVDA distribution.
scons symbolsArchive will package them as a separate archive.
By default, builds also do not use any compiler optimizations.
Please see the
release keyword argument for what compiler optimizations it will enable.
Running the Source Code
Most developers run directly from source by:
cd source pythonw.exe nvda.pyw
Note: Since NVDA is a Windows application (rather than command line), it is best to run it with
However, if during development you encounter an error early in the startup of NVDA, you can use
python.exe which is likely to give more information about the error.
To view help on the arguments that NVDA will accept, use the
These arguments are also documented in the user guide.
A binary build of NVDA can be run on a system without Python and all of NVDA's other dependencies installed (as we do for snapshots and releases).
Binary archives and bundles can be created using scons from the root of the NVDA source distribution. To build any of the following, open a command prompt and change to this directory.
To make a non-archived binary build (equivalent to an extracted portable archive), type:
The build will be created in the dist directory.
Building the installer
To create a launcher archive (one executable allowing for installation or portable dist generation), type:
The archive will be placed in the output directory.
Building the developer documentation
To generate the NVDA developer guide, type:
The developer guide will be placed in the
devDocs folder in the output directory.
Note that the Python 3 sources of NVDA currently do not support building NVDA developer documentation using the
scons devDocs command.
To generate developer documentation for nvdaHelper (not included in the devDocs target):
The documentation will be placed in the
devDocs\nvdaHelper folder in the output directory.
Generate debug symbols archive
To generate an archive of debug symbols for the various dll/exe binaries, type:
The archive will be placed in the output directory.
Generate translation template
To generate a gettext translation template (for translators), type:
Customising the build
Optionally, the build can be customised by providing variables on the command line:
- version: The version of this build.
- release: Whether this is a release version.
- This enables various C++ compiler optimizations such as /O2 and whole-program optimization.
- It also instructs Python to generate optimized byte code.
- publisher: The publisher of this build.
- certFile: The certificate file with which to sign executables. The certificate must be in pfx format and contain the private key.
- certPassword: The password for the private key in the signing certificate. If omitted, no password will be assumed.
- certTimestampServer: The URL of the timestamping server to use to timestamp authenticode signatures. If omitted, signatures will not be timestamped.
- outputDir: The directory where the final built archives and such will be placed.
- targetArchitectures: The target architectures that NVDA should support. Possible values are all, x86 and x86_64. This should generally be left as the default.
For example, to build a launcher with a specific version, you might type:
scons launcher version=test1
For more see the
Running Automated Tests
If you make a change to the NVDA code, you should run NVDA's automated tests. These tests help to ensure that code changes do not unintentionally break functionality that was previously working.
To run the tests (unit tests, translatable string checks), first change directory to the root of the NVDA source distribution as above. Then, run:
To run only specific unit tests, specify them using the
unitTests variable on the command line.
The tests should be provided as a comma separated list.
Each test should be specified as a Python module, class or method relative to the
For example, to run only methods in the
TestSelection classes in the file
tests\unit\test_cursorManager.py file, run this command:
scons tests unitTests=test_cursorManager.TestMove,test_cursorManager.TestSelection
Translatable string checks
To run only the translatable string checks (which check that all translatable strings have translator comments), run:
Linting your changes
In order to ensure your changes comply with NVDA's coding style you can run the Flake8 linter locally.
Some developers have found certain linting error messages misleading, these are clarified in
Running via SCons will use Flake8 to inspect only the differences between your working directory and the specified
If you create a Pull Request, the
base branch you use here should be the same as the target you would use for a Pull Request. In most cases it will be
scons lint base=origin/master
To be warned about linting errors faster, you may wish to integrate Flake8 other development tools you are using.
For more details, see
You may also use
scons to run the system tests,
though this will still require the dependencies to be set up.
For more details (including filtering and exclusion of tests) see
Contributing to NVDA
If you would like to contribute code or documentation to NVDA, you can read more information in our contributing guide.