mastodon - Link to source

NVDA 2025.1 beta 1 is now available for testing! 2025.1 includes NVDA Remote, OneCore & SAPI 4 & 5 improvements, OCR, Microsoft & LibreOffice improvements, Add-on store improvements, Braille updates & new tables plus heaps more! Download from: nvaccess.org/post/nvda-2025-1b…

Please note the "What's new" link doesn't currently work, we're fixing it, but in the meantime, run the installer & open what's new from the NVDA menu.
#NVDA #NVDAsr #Beta #News #Update #PreRelease #FOSS #FLOSS #OpenSource


NVDA 2025.1beta1 available for testing

Beta1 of NVDA 2025.1 is now available for download and testing. For anyone who is interested in trying out what the next version of NVDA has to offer before it is officially released, we welcome yo…
NV Access
#foss #opensource #floss #nvdasr #News #update #nvda #beta #prerelease

reshared this

in reply to Majid Hussain

mastodon - Link to source

NV Access

@mhussain I see the issue here: github.com/nvaccess/nvda/issue… Looks like there is an open PR which would fix it which needs some more work.

In the meantime, the workaround would be to set the pitch to 1.

I'm curious which synthesizer / voice / language you are using that pitch 0 is even comfortable? Most synthesizers are generally designed that pitch 50 (in the middle) suits most people, perhaps with a bit of tweaking one way or the other - but not generally so far as 0 or 11


NVDA fails to announce capital letters when pitch is set to 0 · Issue #10940 · nvaccess/nvda

Steps to reproduce: Switch to eSpeak Enable "Say 'cap' before capitals" Ensure that "capital pitch change percentage" is set to value different than 0 Set pitch to 0 Try to read character by charac...
GitHub
@Majid Hussain
in reply to Majid Hussain

mastodon - Link to source

NV Access

@mhussain We're certainly keeping an eye on what is happening with AI etc - but we appreciate that our users value accuracy and consistency in information, as well as privacy, so we're not about to dive headfirst down that rabbit hole - BUT we appreciate that AI can bring benefits such as better image description for an unlabeled image, than we can otherwise do, but also to that end - we've had add-ons for over six years which used AI image recognition, so you've definitely got your choice!
@Majid Hussain
in reply to Zvonimir Stanecic

mastodon - Link to source

NV Access

@asael Thank you for your query Zvonimir. We planned for this - and in fact this is how we normally do it - we haven't yet entered the "Translatable string freeze" period - so while we've just about got everything how we think it will be, I anticipate there will be more betas and at the very least, we won't move towards putting out a release candidate before the string freeze ends.
@Zvonimir Stanecic
in reply to NV Access

mastodon - Link to source

Dave Taylor

Hi, OK, here we are again. i have an issue with 25.1 beta 1, but I wouldn't know how to make it explaininable on Git or anything. There's a game I play that has links for various parts of the game. Pressing enter on them opens up a list below the link. NVDA used to leave me exactly where I was, so I could go down the list for what I wanted. 2024.1 still does this, but 2025.1 takes me back to the top of the page instead, thus is much slower. I suspect I actually need the focusable element behavour back but am not sure if that is the issue. The game requires a login so I can't send you a page. I love absolutely everything else in the beta though, really good stuff.
in reply to Dave Taylor

mastodon - Link to source

NV Access

@davetaylor2112 Here is the PR to remove that option with links to the issues: github.com/nvaccess/nvda/pull/… Note: "The behaviour of "Automatically set system focus to focusable elements" is not reliable or well supported.
It is known to cause many bugs and unexpected behaviour in browse mode.
If it is to be reimplemented, clear user stories, well defined behaviour and a better implementation is required."

I don't have a workaround, but for good use cases, an issue could be considered


Remove 'Automatically set system focus to focusable elements' by seanbudd · Pull Request #17598 · nvaccess/nvda

Link to issue number: Closes #16469 Closes #15463 Closes #15780 Summary of the issue: The behaviour of "Automatically set system focus to focusable elements" is not reliable or well suppo...
GitHub
@Dave Taylor
in reply to NV Access

mastodon - Link to source

Dave Taylor

2024.4 had the same behaviour as 2024.1, but I have easier access to the latter I'm using the same browser for both tests, although I am finding that NVDA with Edge seems to be becoming problematic on more and more sites, and similarly with NVDA and Firefox. It's getting to the point where most sites seem to work with one or the other but not both. I doubyt that is NVDAs fault, but it's getting harder and harder
in reply to Dave Taylor

mastodon - Link to source

NV Access

@davetaylor2112 Configuration Profiles are actually very useful for giving you different settings in different contexts. Here is a blog piece we wrote on using configuration profiles between programs: nvaccess.org/post/in-process-1… You can also set keystrokes to configuration profiles to use, for instance, on different websites within the one browser

In-Process 19th August 2021

In recent editions, we’ve covered some of the new features in NVDA 2021.1. The exciting news this time, is we’re already up to a beta of NVDA 2021.2! NVDA 2021.2 Beta 1 NVDA 2021.2 Beta 1 is …
NV Access
@Dave Taylor
⇧