We would prefer users download NVDA from our site, it helps us understand the uptake of a new version (through download stats), and reminds users to consider donating (which makes it possible to keep

Yes, it was failing to upload debug symbols to Mozilla's symbol store. This is a non-critical step in the build. Initial advice was to try again, after several attempts I rectified the issue by modify

Hello everyone, NVDA 2020.2 stable has just been released. See the full post at: https://www.nvaccess.org/post/nvda-2020-2 Thank you for all your contributions. The community is what makes NVDA what i

I can only guess, but based on what you are describing it seems possible that the speech indexes aren't calling back to the speech system. When a synth reaches an index it is expected to call notify o

Hello everyone, NVDA 2020.1 stable has just been released. See the full post at: https://www.nvaccess.org/post/nvda-2020-1-released/ Thank you for all your contributions. The community is what makes N

Hi all, On behalf of NV Access I would like to officially welcome Shubham Jain to the NVDA project, as our Google Summer of Code 2020 student. Between now and the end of August, Shubham will be workin

Yes, the GitHub project boards need some work to be easy to use with a screen reader that's for sure. Cards are just issues, but can be organized within the project by using the columns. The columns o

#project-idea

I'd like to take advantage of GitHub's projects feature to make it easier for new and existing developers to find work relevant to their interest, group related work to help ensure it works towards a

#project-idea

No, I'm not sure which message and I can't find it. Can you tell me the title?

Hi all, NVDA 2020.1rc1 has been released. This is a release candidate, and unless any critical issues are found, this will be identical to the 2020.1 release. Highlights and download links can be foun

I agree, that page could use updating, though it's a bit of a chicken and egg situation. We are currently working out the details of this process, and trying to be transparent about the changes we are

In the past we have aimed for 4 releases a year. The new approach will likely result in a variable number of releases per year. The releases will be smaller but more often. The release process takes a

The 2020.1 RC is currently blocked waiting for: https://github.com/nvaccess/nvda/pull/11040 We are aiming for a shorter release cycle, so we will likely start the 2020.2 beta as soon as the 2020.1 rel

Given that this works in Firefox, this is likely an issue in Chrome. See Aria atomic seems to be ignored in Chrome #10866 According to the issue there hasn’t been any investigation about whether NVDA

Hi everyone, NV Access would like to kindly ask contributors to temporarily hold off on creating new Pull Requests (PR's) specifically for features or enhancements to NVDA. This will be a temporary ar

> At least with Espeak, though, a comma between two words isn't spoken or indicated at all if no space is between it and the following word. This makes argument or parameter lists run together as a si

Hi Alex, What is your “Punctuation/symbol level” set to? You can use NVDA+p to toggle through the options, or check the option in the NVDA settings, speech category. When set to all, the comma should

I'd have to investigate carefully and probably need access to your app. Some hints that might help to understand what is happening: - First make yourself familiar with the developer info for the contr

Doing this well is quite a large project. I should note that we are gradually working towards making this easier, but there is still much to go. It is listed as one of the projects for this years Goog

Did you get it to build? Since the error is with the Arm64 build, it may be that you did not install the correct Arm64 dependencies? Can you check the readme, and confirm these are installed please?