Skip to main content


NVDA 2024.2 beta 1 is now available for testing from: nvaccess.org/post/nvda-2024-2b…

For anyone who is interested in trying out what NVDA has to offer before release, we welcome your feedback.

Highlights
- Sound Split
- New Synth Settings ring & quick navigation commands
- New braille features & fixes, including "Display speech output".
- Updated eSpeak, adding new language Tigrinya.

There are many minor bug fixes for applications

#NVDA #NVDAsr #ScreenReader #Beta #News #Accessibility #A11y #FOSS

in reply to NV Access

Ooh, some nice things in here. I feel like single letter nav keystrokes need to be different in browsers than other apps, but saying that, please can we have sentence navigation in browsers? It's literally way the most efficient way to get to the start of the main text on most sites now. I really miss the sentence nav addon. Thanks.
in reply to Dave Taylor

@davetaylor2112 NVDA 2024.2 DOES have a binding for a quick nav key for paragraph navigation, and just looking at upcoming features - not quite here yet, but there is a feature being worked on for sentence nav (in general, but including in browsers) - that looks like it's not quite ready and currently aimed at 2024.3: github.com/nvaccess/nvda/pull/…

Re your other comment - how would you have single letter nav keystrokes different between browsers & other apps?

in reply to NV Access

This paragraph, does this now apply in browsers too? It doesn't so far with the control arrow keys, which is a pity
in reply to Dave Taylor

@davetaylor2112 The new paragraph navigation is a quick nav key, P, although control+up arrow and control+down arrow also work here for me. Note that in NVDA's "Document Navigation" settings you can control what constitutes a paragraph break - the default is to let the application handle it, but that means it doesn't necessarily work in some places like Notepad++. You can set it to requiring a single or double blank line
in reply to NV Access

Hi, where is it I email logs to to help debug issues? I think I've found something relating to the weird keyboard issues I sometimes get. It actually seems to be related to Explorer as far as Ican tell.
in reply to Dave Taylor

@davetaylor2112 Thanks face, email info@nvaccess.org - if you can set NVDA's log level (on general settings screen) to debug, then press NVDA+q, down arrow to "restart with add-ons disabled" and enter, recreate the issue, then send the logs and description etc to us.
in reply to NV Access

Thanks, difficult indeed, because it's a random problem, and it may well be caused by an addon, and this won't help me work out which addon
in reply to NV Access

Oh, neat, I've discovered one of my version of Eloquence works with addons disabled, and it is even legal!
in reply to Dave Taylor

@davetaylor2112 The Sapi 5 version will still work I expect because NVDA works with sapi5 voices natively so that particular one doesn't need an addon
in reply to NV Access

This is actually the SAPI 4 from Kurzweil. I'm afraid I will not ever use Code Factory products, and don't like to support anyone that even suggests people should. They always were completely unethical and unprofessional
in reply to NV Access

Yeah, it's an addon causing problems when Iswitch windows, but it doesn't show which one
in reply to Dave Taylor

@davetaylor2112 If you disable all add-ons and then enable them one at a time, you'll eventually get to which one (or if you have a lot, enable half, if it works, enable half the rest, or if it doesn't work disable half of the ones you just enabled, etc.
in reply to NV Access

hopefully I can change "find" from nvda + F 3 again. it was in the 2024.1 betas , but not in the rc/public release .
in reply to Sean | Ginsenshi The blindwolf

@ginsenshi Where were you (what program was open / focussed) when you tried to change the keystroke? You can only change keystrokes which are available to you at the time you open it - so in say a web browser, find will be listed in Input Gestures, but in File Explorer, it isn't. It's here in my Input Gestures on 2024.1