NVDA 2024.4 Beta 3 is now available!

Changes introduced in Beta 3:

Updated LibLouis Braille translator to 3.31.0.

• Fixed translation of numbers in Spanish Braille.

• New Braille tables:

• Thai grade 1

• Greek international Braille (single-cell accented letters)

• Renamed tables:

• “Thai 6 dot” was renamed to “Thai grade 0” for consistency reasons.

• The existing “Greek international braille” table was renamed to “Greek international braille (2-cell accented letters)” to clarify the distinction between the two Greek systems.

Updates to translations.

Read more and download at: https://www.nvaccess.org/post/nvda-2024-4beta3/

Continuing my trend of being a bit late posting - NVDA 2024.4 Beta 2 is now available: https://www.nvaccess.org/post/nvda-2024-4beta2/

Changes introduced in Beta 2:

• The stability of NVDA’s Poedit support has been improved with the side effect that the minimum required version of Poedit is now version 3.5.
• NVDA no longer freezes while checking for add-on updates.
• Updates to translations.

Note that “NVDA is no longer as sluggish when arrowing up and down through large files in VS Code.” is listed on the release announcement as a new update - this was included in Beta 1 and inadvertently carried over to the Beta 2 announcement.

Thanks so much for pinning this - and for all the responses we’ve got! We are closing the survey today, so can remove the pinned post now.

Of course, we are always happy for feedback, so if anyone does have additional feedback they would like to give, please don’t hesitate to write to info@nvaccess.org

Kind regards

Quentin

I have also not encountered the credentials going stale issue. It might be worth clearing your browser cache (remember when we had to do that to fix ANYTHING? I have barely needed to do that in the last year or so, but it comes up occasionally).

Re navigating, the list of posts works ok - you can press H to jump from one post to the next. When you actually go into a post, the UI breaks down a bit. Mostly because (for me at least), n doesn’t seem to work to jump to the next non-linked text where it should (as in the body of motobojo’s post, or any replies). The “Skip to content” button also doesn’t seem to work - it comes up as the first item on the page, but you can’t activate it?

We’re going to be there all week. We are presenting in “Orange County 1-2” at 2:20pm on Thursday 21st March.

Uh, thanks?

We try to prioritise features and fixes that will have the most positive impact on the largest number of users. Not all features are used by every user, but there’s usually SOMETHING for everyone in each release.

I’m glad it sounds like we got some things in there for you this time around anyway!

Is it this one: “Added an experimental option to leverage the UIA notification support in Windows Terminal to report new or changed text in the terminal, resulting in improved stability and responsivity. (#13781) Consult the user guide for limitations of this experimental option.”

We don’t normally link directly to updated files in the what’s new, it’s really just to let you know what is new so you can try it out when you download the update. The easiest way is to open the user guide from the help menu - in this way, if you are using NVDA in a language other than English, you will also get the updated translation (if it is there yet).

To get to the file without downloading the beta, it’s a little roundabout, but you can go to the linked issue, and from there to the PR (“seanbudd closed this as completed in #14047 on Oct 25, 2022”: https://github.com/nvaccess/nvda/pull/14047 From there, go to files, and you will find the user guide as one of them, and you can view the file, which links me here: https://github.com/leonardder/nvda/blob/f6f6563b6872ec82b095ef9a930606b8d10e7f27/user_docs/en/userGuide.t2t

The raw file doesn’t have neat little links but if you search for “Windows terminal”, there aren’t too many other references.

If you run the new version / beta / alpha etc, you can pull up the user guide for that version from the help menu. The info in the release announcement / on the what’s new page is more designed to show you what has changed. Maybe I’m not quite understanding what you are after though?

You can use it now with NVDA 2023.2 Beta 1 which is currently available: https://www.nvaccess.org/post/nvda-2023-2beta1/

I must admit I haven’t looked into using track changes on Libre Office lately. I did find the Libre Office keystrokes here: https://help.libreoffice.org/latest/en-US/text/swriter/04/01020000.html What I was going to say was that The Document Foundation (makes of Libre Office) have hired Michael Weghorn as a developer focusing on accessibility of Libre office: https://blog.documentfoundation.org/blog/2023/07/04/welcome-michael-weghorn-new-developer-at-tdf/ We’ve worked with Michael for awhile now, although only when he was available to donate some time. Hopefully this will mean great things for Libre Office accessibility moving forward!