NVDA 2026.2beta1 available for testing

[NVDA Screen Reader Discussion]

Beta1 of NVDA 2026.2 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 you to download the beta and provide feedback using our issue reporting process. By installing the beta you will be opting into NVDA’s beta channel, and will only receive update notifications for beta and release candidate (RC) builds. The beta/RC channel will always keep you up to date with the latest NVDA version. The last RC in a release cycle is identical to the final stable release. To return to the stable release channel, upgrade manually to the latest stable build.

Links

• Download NVDA 2026.2beta1
  • SHA256 sum: 25b0f893f6a45017d4e8f1388e45feb8707052baafc47af713332de6fde5dd48
• What’s new in this release of NVDA
• Please report any issues on GitHub.

Highlights

This release includes a new built-in Magnifier feature, improvements to touch gestures and navigation, and expanded speech and braille capabilities.

The Magnifier provides zoom and color filtering options to assist users with visual impairments. The Magnifier currently only supports fullscreen mode, with docked modes planned in a future release.

Touch support has been significantly expanded with new pinch gestures and touch-based browse mode navigation for web content. You can now navigate between links, headings, form fields, and other elements using touch flicks.

Speech features have been enhanced with support for custom speech dictionaries that can be provided by add-ons and new dictionary entry types for more granular control. A new voice setting for OneCore voices was added to control pauses after punctuation. A new command allows repeating the last spoken information, with the ability to display it in a browsable message. The default gesture to repeat the last spoken information is NVDA+x, which can be changed in the Input Gestures dialog.

The braille display can now automatically scroll and DotPad devices support multi-button combinations.

Liblouis has been updated with new Italian and Estonian braille tables.

When resetting NVDA to factory defaults, an Undo button is now available to restore the previous configuration.

[Gene Asner]

When I uncheck the check box to control pause length for punctuation for One Core voices, there is no difference.  Also, why isn't there a way to set the pause length when the check box is unchecked.  Evidently the natural pause setting when checked is for whatever the setting is in One Core voices but if this is going to be allowed to be not adhered to, users should be able to set the pause length perhaps in a combo box.

Gene

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/8c5b737c-5530-401e-887f-aae5ee74baabn%40nvaccess.org.

[Fettah Pınar]

I agree.
If a delay setting is to be added, it should be in the form of a checkbox or a slider, and the user should be able to adjust the slider as desired.
Additionally, this setting should not be limited to One Core voices; it should be available for all supported synthesizers.

NVDA Screen Reader Discussion <nvda-...@nvaccess.org>, 2 Haz 2026 Sal, 04:06 tarihinde şunu yazdı:

[Veli Laasala]

The latest beta has serious issue in user dictionaries. It has lost all
comments of my hundreds of dictionary entries.

Veli

NVDA Screen Reader Discussion kirjoitti 2.6.2026 klo 4:06:
> Beta1 of NVDA 2026.2 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 you to download
> the beta and provide feedback using our issue reporting process

> <https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/
> readme.md>. By installing the beta you will be opting into NVDA’s beta

> channel, and will only receive update notifications for beta and release
> candidate (RC) builds. The beta/RC channel will always keep you up to
> date with the latest NVDA version. The last RC in a release cycle is
> identical to the final stable release. To return to the stable release

> channel, upgrade manually to the latest stable build <https://
> www.nvaccess.org/download/>.
>
> Links
>
> * Download NVDA 2026.2beta1 <https://download.nvaccess.org/
> releases/2026.2beta1/nvda_2026.2beta1.exe>
> o SHA256 sum:
> 25b0f893f6a45017d4e8f1388e45feb8707052baafc47af713332de6fde5dd48
> * What’s new in this release of NVDA <https://download.nvaccess.org/
> releases/2026.2beta1/documentation/changes.html>
> * Please report any issues on GitHub <https://github.com/nvaccess/
> nvda/issues>.

>
> Highlights
>
> This release includes a new built-in Magnifier feature, improvements to
> touch gestures and navigation, and expanded speech and braille capabilities.
>
> The Magnifier provides zoom and color filtering options to assist users
> with visual impairments. The Magnifier currently only supports
> fullscreen mode, with docked modes planned in a future release.
>
> Touch support has been significantly expanded with new pinch gestures
> and touch-based browse mode navigation for web content. You can now
> navigate between links, headings, form fields, and other elements using
> touch flicks.
>
> Speech features have been enhanced with support for custom speech
> dictionaries that can be provided by add-ons and new dictionary entry
> types for more granular control. A new voice setting for OneCore voices
> was added to control pauses after punctuation. A new command allows
> repeating the last spoken information, with the ability to display it in
> a browsable message. The default gesture to repeat the last spoken
> information is NVDA+x, which can be changed in the Input Gestures dialog.
>
> The braille display can now automatically scroll and DotPad devices
> support multi-button combinations.
>
> Liblouis has been updated with new Italian and Estonian braille tables.
>
> When resetting NVDA to factory defaults, an Undo button is now available
> to restore the previous configuration.
>

> NVDA logo on a purple background
>
>

> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
> NV Access expects that all community members will read and abide by the
> rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via nvda-

> users+m...@nvaccess.org.

> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send

> an email to nvda-users+...@nvaccess.org <mailto:nvda-
> users+un...@nvaccess.org>.

> To view this discussion visit https://groups.google.com/a/nvaccess.org/
> d/msgid/nvda-users/8c5b737c-5530-401e-887f-aae5ee74baabn%40nvaccess.org

> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-
> users/8c5b737c-5530-401e-887f-aae5ee74baabn%40nvaccess.org?
> utm_medium=email&utm_source=footer>.

[Sean Budd]

Apologies, I think I sent my previous reply to gene only.
The setting matches an internal API setting Microsoft controls. It has two options, about 750ms delay after punctuation, or no delay. Unfortunately we cannot configure it.
NVDA only has so much control over how synthesizers decide to output speech. All we can really do is send speech text and any additional commands or config they support themselves.

You can contact the group owners and moderators via nvda-users+managers@nvaccess.org.

---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+unsubscribe@nvaccess.org.

[NVDA Screen Reader Discussion]

Hi all,

Beta2 of NVDA 2026.2 is now available for download and testing. Please see the original thread message for more information about the release and beta testing.

Download: https://www.nvaccess.org/post/nvda-2026-2beta2/

Changes introduced in Beta 2:

• Updates to translations
• Removed the Magnifier option "keep mouse centered"
• Improvements to Magnifier settings names and layout

[Cyrille BOUGOT]

Hello

I have looked at my dictionaries and have found that comments have actually disappeared on my end too. Opening the corresponding .dic files, I can see they are still there, but they don't show up in NVDA's GUI.

I have tried to launch NVDA 2026.1 and 2025.3.3 with these .dic files but the comments do not show up either. So I'm not sure if this is a 2026.2 regression or not.

You may open a GitHub issue for this, more if you think that comments were present in 2026.1.

Cheers,

Cyrille

[Quentin Christensen]

Not sure if it is a regression, but definitely sounds like a bug.  Would it be possible for someone to create an issue for this please? https://github.com/nvaccess/nvda/issues

(Veli, I did see the emails you sent directly to us, and I apologise for not having had the chance to reply yet, but they did come through!)

You can contact the group owners and moderators via nvda-user...@nvaccess.org.

---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/c0382c4f-6198-4f77-b1ac-4355e822da3dn%40nvaccess.org.

--

Quentin Christensen

Training and Support Manager

NV Access

www.nvaccess.org 

Celebrating 20 years of NVDA

Training: https://www.nvaccess.org/shop/

Certification: https://certification.nvaccess.org/

Blog, releases & news by email: https://nvaccess.org/newsletter

User group: https://nvaccess.org/nvda-users

Mastodon: https://fosstodon.org/@NVAccess

Other socials & community: https://www.nvaccess.org/#socials

[Cyrille BOUGOT]

Hello

An issue has been opened for this: #20315.

Even if it iniitally mentions sapi_32 Voice Dictionary, I have checked that it also applies to default one.

Cheers,

Cyrille

[NVDA Screen Reader Discussion]

Hi all,

Beta3 of NVDA 2026.2 is now available for download and testing. Please see the original thread message for more information about the release and beta testing.

Download: https://www.nvaccess.org/post/nvda-2026-2beta3/

Changes introduced in Beta 3:

• Pressing NVDA+control+w on secure screens now opens Magnifier settings as expected.
• Highlighter and Magnifier now follow the focused cell in Excel

• Improvements to Magnifier settings names and layout

On Tuesday, June 2, 2026 at 11:06:15 AM UTC+10 NVDA Screen Reader Discussion wrote:

[Cyrille BOUGOT]

Hello

In addition to what has been mentioned, the following changes has been introduced in beta3:

* Fixed a bug where settings dialog could not be validated after Magnifier settings had been displayed (part of #20261 but it was not correctly documented in the PR, sorry)

Cheers,

Cyrille

[NVDA Screen Reader Discussion]

Hi all,

Beta4 of NVDA 2026.2 is now available for download and testing. Please see the original thread message for more information about the release and beta testing.

Download: https://www.nvaccess.org/post/nvda-2026-2beta4/

Changes introduced in Beta 4:

• Updates to translations
• Changed the button layout in the “Add dictionary entry” dialog to vertical
• Changed the magnifier tracking from the center of an object to the start (e.g. top-left for left-to-right languages)
• Fixed saving comments in speech dictionaries
• Added a debug log category for magnifier

• Improvements to Magnifier settings names and layout

[Obaida Tamimi]

في ثلاثاء، 23 يونيو، 2026 في 5:00 ص، كتب NVDA Screen Reader Discussion

Dear NVDA community,

I am writing to share a critical issue regarding the accessibility of hardware BIOS/UEFI settings, which I am currently escalating to the FBI's Internet Crime Complaint Center (IC3).

I have faced persistent barriers in accessing these essential settings, which prevent me from managing my computer independently. I believe this lack of accessibility is a serious concern that affects users' rights and ability to utilize their technology effectively.

I wanted to bring this matter to your attention as part of my ongoing efforts to seek accountability and ensure that accessibility is prioritized by hardware manufacturers and firmware developers.

Thank you for your time and for the vital work you do in supporting the screen reader community.

Best regards,
Obaida

<nvda-...@nvaccess.org>:

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/e09caaab-14e3-417c-b89d-a50bbeea184cn%40nvaccess.org.

[Obaida Tamimi]

Hi everyone,

I'm frustrated by the constant barrier of inaccessible BIOS/UEFI settings. As a screen reader user, this keeps me from managing my own computer independently.

I’m currently escalating this issue to the FBI (IC3) because, frankly, it’s not just a technical inconvenience—it’s a matter of rights and independence that manufacturers keep ignoring.

I wanted to share this with the community. We shouldn't have to accept that our hardware remains off-limits to us.

Best,
Obaida

[blind...@gmail.com]

I do not believe the IC3 is going to want anything to do with this issue as it is not an internet crime to choose whether or not to make UEFI or BIOS accessible.

 

This is an ongoing issue that we have face since time immemorial, and, I suspect this is an issue we are going to continually face as firmware changes and interfaces change. To keep up with computer hardware.

 

I’m about to use a crass saying here, however it applies. While ever your arsehole points to the ground, you are going to face the problem of everchanging firmware and everchanging interfaces.

 

How, for one would you apply that accessibility, when firstly, you are at the bare bones of the hardware itself and can, if you make a mistake, render your machine inoperable. And secondly, there is no sound at that point as you likely cannot access it at that stage of the boot up process.

 

I like many of us on here would love to gain access to that part of the system as it will assist my own efforts in computer management, however, on occasion, and I believe this to be one of them, unless we get a universal UEFI or BIOS, this, will, not, happen!

 

I would strongly advise not wasting the FBI’s time on this matter, as it’s not a matter for them to be dealing with in the first place.

 

 

 

Shaun Oliver

 

VK5ESE

 

Adaptive technology consultant

 

Mobile: +61 477 83-6199

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkRSRSbFSKqqm--z%3Dmzuyp0v%2Bq4nrh7%2Buexd_0otQ1NCcg%40mail.gmail.com.

[Richard Turner]

The problem since time began is that there are no sound drivers at the bios level.

 

Find a way around that, and we will have access to the bios.

 

 

 

Richard, USA,

The only way to make sense out of change is to plunge into it, move with it, and join the dance."

-- Alan Watts (1915-1973)

 

My web site: https://www.turner42.com

 

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/0f2d01dd0313%2433a3d5e0%249aeb81a0%24%40gmail.com.

[Obaida Tamimi]

Hi Shaun and Richard,

Thank you for your candid feedback and for sharing your technical perspective. I completely understand that there are no sound drivers at the BIOS level and that this is a long-standing, complex challenge.

However, I believe that classifying this solely as a technical hurdle often leads us to a dead end. Whether or not it is an "internet crime" in the eyes of the IC3, my goal is to frame this as an accessibility rights issue. If we do not push for accountability from hardware manufacturers at a systemic level, we will continue to face these same barriers indefinitely.

I appreciate your insights, but I feel that continuing to highlight this issue to official channels is a necessary step to eventually force manufacturers to prioritize accessibility in firmware design.

Best regards,
Obaida

[Obaida Tamimi]

Hi Shaun and Richard,

Thank you for your candid feedback and for sharing your technical perspective. I completely understand that there are no sound drivers at the BIOS level and that this is a long-standing, complex challenge.

However, I believe that classifying this solely as a technical hurdle often leads us to a dead end. Whether or not it is an "internet crime" in the eyes of the IC3, my goal is to frame this as an accessibility rights issue. If we do not push for accountability from hardware manufacturers at a systemic level, we will continue to face these same barriers indefinitely.

I appreciate your insights, but I feel that continuing to highlight this issue to official channels is a necessary step to eventually force manufacturers to prioritize accessibility in firmware design.

Best regards,

Obaida

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00bc01dd0317%2461ffd430%2425ff7c90%24%40comcast.net.

[Obaida Tamimi]

Hi Shaun and Richard,

Thank you for your candid feedback and for sharing your technical perspective. I completely understand that there are no sound drivers at the BIOS level and that this is a long-standing, complex challenge.

However, I believe that classifying this solely as a technical hurdle often leads us to a dead end. Whether or not it is an "internet crime" in the eyes of the IC3, my goal is to frame this as an accessibility rights issue. If we do not push for accountability from hardware manufacturers at a systemic level, we will continue to face these same barriers indefinitely.

I appreciate your insights, but I feel that continuing to highlight this issue to official channels is a necessary step to eventually force manufacturers to prioritize accessibility in firmware design.

Best regards,

Obaida

في ثلاثاء، 23 يونيو، 2026 في 4:51 م، كتب 'Richard Turner' via NVDA Screen Reader Discussion <nvda-...@nvaccess.org>:

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00bc01dd0317%2461ffd430%2425ff7c90%24%40comcast.net.

[Richard Turner]

I think you are targeting the wrong group for escalating this issue.

You would be better off focusing on the regulatory offices that oversee manufacturing.

For the US, I would start with the Federal Trade Commission FTC, and the Attorney General's office, possibly starting with the State you reside in if you live in the US.

Otherwise, whomever regulates business practices where you live.

This has absolutely nothing to do with the Internet.

It has everything to do with accessibility to hardware.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkS62QFfeKoLannxwaf%3D%3Dw%3D8g9%2BuKDnv79ScHuzxNWgQnA%40mail.gmail.com.

[Obaida Tamimi]

Hi Richard,

I appreciate the suggestion. However, I have already engaged with various regulatory bodies, including the FTC and other relevant authorities, in the past regarding this exact issue.

Unfortunately, as many of us have experienced, these channels often result in a "dead end" where the issue is either ignored or redirected indefinitely. That is precisely why I am exploring different, perhaps less conventional, avenues to get some attention to this systemic failure.

While I agree that the problem lies with hardware manufacturers, it seems that until we find a way to make them legally or socially accountable, these technical barriers will persist.

Best regards,
Obaida

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00ef01dd031b%2409e9f1f0%241dbdd5d0%24%40comcast.net.

[blind...@gmail.com]

There is a saying. You attract more flies with honey than with vinegar.

 

However, I believe you are now subject hijacking. This was the wrong thread to attach this to.

 

 

Shaun Oliver

 

VK5ESE

 

Adaptive technology consultant

 

Mobile: +61 477 83-6199

 

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of Obaida Tamimi

Sent: Tuesday, 23 June 2026 06:59
To: nvda-...@nvaccess.org

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkSGuentmd1YWXUPJmjJEZuyuHM6zGtSy0R52LLPD_c5KA%40mail.gmail.com.

[blind...@gmail.com]

It is absolutely purely a technical issue.

 

As I stated earlier, there’s no sound at the bios/UEFI level. You cannot hope to get any kind of speech feedback during CMOS setup or post, for that matter.

 

In short, I do not believe you are going about this in the correct manner.

 

Furthermore, forcing hardware vendors to make something accessible or rather, in this case, useable for what is in reality a piddling amount of people that dabble in the area of computer and hardware management, is a good way to get the kind of flack we, as a community neither need nor want, Especially, if we want our voices to continue to be heard when we want to make our own lives much easier.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkRf28%3D1KfT_c3Fzitk_9z9GHV_u2yfpJF%3Dy14f%2BMyShPg%40mail.gmail.com.

[Rui Fontes]

Hello!

Please, do not forget that the scope of the group is NVDA!

Rui Fontes
Moderator

[Obaida Tamimi]

Hi Rui,

Understood and thank you for the reminder.

My intent in raising this issue was simply to explore if there is any collective interest in advocating for better BIOS accessibility from hardware manufacturers like HP and AMI. I agree that the NVDA group is for NVDA-specific support, and I will respect that moving forward.

Best,
Obaida

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 
You can contact the group owners and moderators via nvda-user...@nvaccess.org.
---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+...@nvaccess.org.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/f18cdaa8-2b81-4d3a-8b18-cfd12c7c3322%40gmail.com.

[Gene Asner]

The FBI never has and is not given the job of dealing with accessibility
issues. I am not sure where you would raise it but after how many
decades, with nothing being done, you are not on firm ground if you
think that one petition more or one group of emails more here or there
is going to make any difference. If you want to pursue this further, I
would suggest consulting those with knowledge in the field, such as the
NFB or the ACB and perhaps AFB would have knowledgeable people on the
subject.

Gene

On 6/23/2026 9:01 AM, Obaida Tamimi wrote:
> Hi Shaun and Richard,
>
> Thank you for your candid feedback and for sharing your technical
> perspective. I completely understand that there are no sound drivers at
> the BIOS level and that this is a long-standing, complex challenge.
>
> However, I believe that classifying this solely as a technical hurdle
> often leads us to a dead end. Whether or not it is an "internet crime"
> in the eyes of the IC3, my goal is to frame this as an accessibility
> rights issue. If we do not push for accountability from hardware
> manufacturers at a systemic level, we will continue to face these same
> barriers indefinitely.
>
> I appreciate your insights, but I feel that continuing to highlight this
> issue to official channels is a necessary step to eventually force
> manufacturers to prioritize accessibility in firmware design.
>
> Best regards,
> Obaida
>
>
> في ثلاثاء، 23 يونيو، 2026 في 4:51 م، كتب 'Richard Turner' via NVDA
> Screen Reader Discussion <nvda-...@nvaccess.org

> <mailto:nvda-...@nvaccess.org>>:

>
> The problem since time began is that there are no sound drivers at

> the bios level.____
>
> __ __
>
> Find a way around that, and we will have access to the bios.____
>
> __ __
>
> __ __
>
> __ __
>
> Richard, USA,____

>
> The only way to make sense out of change is to plunge into it, move

> with it, and join the dance." ____
>
> -- Alan Watts (1915-1973)____
>
> __ __
>
> My web site: https://www.turner42.com <https://www.turner42.com/>____
>
> __ __
>
> __ __
>
> *From:*nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>
> <nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>> *On
> Behalf Of *blind...@gmail.com <mailto:blind...@gmail.com>
> *Sent:* Tuesday, June 23, 2026 6:21 AM
> *To:* nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>
> *Subject:* RE: [NVDA] Re: Escalating the issue of inaccessible
> BIOS/UEFI to the FBI (IC3)____
>
> __ __

>
> I do not believe the IC3 is going to want anything to do with this
> issue as it is not an internet crime to choose whether or not to

> make UEFI or BIOS accessible.____
>
> __ __

>
> This is an ongoing issue that we have face since time immemorial,
> and, I suspect this is an issue we are going to continually face as
> firmware changes and interfaces change. To keep up with computer

> hardware.____
>
> __ __

>
> I’m about to use a crass saying here, however it applies. While ever
> your arsehole points to the ground, you are going to face the

> problem of everchanging firmware and everchanging interfaces.____
>
> __ __

>
> How, for one would you apply that accessibility, when firstly, you
> are at the bare bones of the hardware itself and can, if you make a
> mistake, render your machine inoperable. And secondly, there is no
> sound at that point as you likely cannot access it at that stage of

> the boot up process.____
>
> __ __

>
> I like many of us on here would love to gain access to that part of
> the system as it will assist my own efforts in computer management,
> however, on occasion, and I believe this to be one of them, unless

> we get a universal UEFI or BIOS, this, will, not, happen!____
>
> __ __

>
> I would strongly advise not wasting the FBI’s time on this matter,

> as it’s not a matter for them to be dealing with in the first place.____
>
> __ __
>
> __ __
>
> __ __
>
> Shaun Oliver____
>
> __ __
>
> VK5ESE____
>
> __ __
>
> Adaptive technology consultant____
>
> __ __
>
> Mobile: +61 477 83-6199____
>
> __ __
>
> *From:*nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>
> <nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>> *On
> Behalf Of *Obaida Tamimi
> *Sent:* Tuesday, 23 June 2026 04:50
> *To:* nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>
> *Subject:* [NVDA] Re: Escalating the issue of inaccessible BIOS/UEFI
> to the FBI (IC3)____
>
> __ __

>
> Hi everyone,
>
> I'm frustrated by the constant barrier of inaccessible BIOS/UEFI
> settings. As a screen reader user, this keeps me from managing my
> own computer independently.
>
> I’m currently escalating this issue to the FBI (IC3) because,
> frankly, it’s not just a technical inconvenience—it’s a matter of
> rights and independence that manufacturers keep ignoring.
>
> I wanted to share this with the community. We shouldn't have to
> accept that our hardware remains off-limits to us.
>
> Best,

> Obaida____
>
> __ __
>
> __ __
>
> فيثلاثاء،23 يونيو،2026 في12:07 م،كتبObaida Tamimi
> <altamim...@gmail.com <mailto:altamim...@gmail.com>>:____
>
> __ __
>
> __ __
>
> فيثلاثاء،23 يونيو،2026 في5:00 ص،كتبNVDA Screen Reader Discussion____

>
> Dear NVDA community,
>
> I am writing to share a critical issue regarding the
> accessibility of hardware BIOS/UEFI settings, which I am
> currently escalating to the FBI's Internet Crime Complaint
> Center (IC3).
>
> I have faced persistent barriers in accessing these essential
> settings, which prevent me from managing my computer
> independently. I believe this lack of accessibility is a serious
> concern that affects users' rights and ability to utilize their
> technology effectively.
>
> I wanted to bring this matter to your attention as part of my
> ongoing efforts to seek accountability and ensure that
> accessibility is prioritized by hardware manufacturers and
> firmware developers.
>
> Thank you for your time and for the vital work you do in
> supporting the screen reader community.
>
> Best regards,

> Obaida____
>
> <nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>>:____
>
> Hi all,____

>
> Beta4 of NVDA 2026.2 is now available for download and
> testing. Please see the original thread message for more

> information about the release and beta testing.____
>
> Download: https://www.nvaccess.org/post/nvda-2026-2beta4/
> <https://www.nvaccess.org/post/nvda-2026-2beta4/>____
>
> Changes introduced in Beta 4: ____
>
> * Updates to translations____
> * Changed the button layout in the “Add dictionary entry”
> dialog to vertical____
> * Changed the magnifier tracking from the center of an

> object to the start (e.g. top-left for left-to-right

> languages)____
> * Fixed saving comments in speech dictionaries____
> * Added a debug log category for magnifier____
> * Improvements to Magnifier settings names and layout____
>
> __ __

>
> On Tuesday, June 16, 2026 at 10:46:34 AM UTC+10 NVDA Screen

> Reader Discussion wrote:____
>
> Hi all,____

>
> Beta3 of NVDA 2026.2 is now available for download and
> testing. Please see the original thread message for more

> information about the release and beta testing.____
>
> Download:
> https://www.nvaccess.org/post/nvda-2026-2beta3/
> <https://www.nvaccess.org/post/nvda-2026-2beta3/>____
>
> Changes introduced in Beta 3:____
>
> * Pressing NVDA+control+w on secure screens now opens
> Magnifier settings as expected.____
> * Highlighter and Magnifier now follow the focused
> cell in Excel____
>
> * Improvements to Magnifier settings names and layout____

>
> On Tuesday, June 2, 2026 at 11:06:15 AM UTC+10 NVDA

> Screen Reader Discussion wrote:____

>
> Beta1 of NVDA 2026.2 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 you to
> download the beta and provide feedback using our
> issue reporting process

> <https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/readme.md>. By installing the beta you will be opting into NVDA’s beta channel, and will only receive update notifications for beta and release candidate (RC) builds. The beta/RC channel will always keep you up to date with the latest NVDA version. The last RC in a release cycle is identical to the final stable release. To return to the stable release channel, upgrade manually to the latest stable build <https://www.nvaccess.org/download/>.____
>
> Links ____
>
> * Download NVDA 2026.2beta1
> <https://download.nvaccess.org/releases/2026.2beta1/nvda_2026.2beta1.exe> ____
>
> o SHA256 sum:
> 25b0f893f6a45017d4e8f1388e45feb8707052baafc47af713332de6fde5dd48____
>
> * What’s new in this release of NVDA
> <https://download.nvaccess.org/releases/2026.2beta1/documentation/changes.html>____
> * Please report any issues on GitHub
> <https://github.com/nvaccess/nvda/issues>.____
>
> Highlights ____

>
> This release includes a new built-in Magnifier
> feature, improvements to touch gestures and
> navigation, and expanded speech and braille

> capabilities.____

>
> The Magnifier provides zoom and color filtering
> options to assist users with visual impairments. The
> Magnifier currently only supports fullscreen mode,

> with docked modes planned in a future release.____

>
> Touch support has been significantly expanded with
> new pinch gestures and touch-based browse mode
> navigation for web content. You can now navigate
> between links, headings, form fields, and other

> elements using touch flicks.____

>
> Speech features have been enhanced with support for
> custom speech dictionaries that can be provided by
> add-ons and new dictionary entry types for more
> granular control. A new voice setting for OneCore
> voices was added to control pauses after
> punctuation. A new command allows repeating the last
> spoken information, with the ability to display it
> in a browsable message. The default gesture to
> repeat the last spoken information is NVDA+x, which

> can be changed in the Input Gestures dialog.____

>
> The braille display can now automatically scroll and

> DotPad devices support multi-button combinations.____

>
> Liblouis has been updated with new Italian and

> Estonian braille tables.____

>
> When resetting NVDA to factory defaults, an Undo
> button is now available to restore the previous

> configuration.____
>
> NVDA logo on a purple background____
>
> __ __

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor
> Code of Conduct.
> NV Access expects that all community members will read and
> abide by the rules set out in this document while
> participating in this group.

> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>

>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-users%2Bman...@nvaccess.org>.

> ---
> You received this message because you are subscribed to the
> Google Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails
> from it, send an email to
> nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/e09caaab-14e3-417c-b89d-a50bbeea184cn%40nvaccess.org <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/e09caaab-14e3-417c-b89d-a50bbeea184cn%40nvaccess.org?utm_medium=email&utm_source=footer>.____

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of
> Conduct.
> NV Access expects that all community members will read and abide by
> the rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-user...@nvaccess.org>.

> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkRSRSbFSKqqm--z%3Dmzuyp0v%2Bq4nrh7%2Buexd_0otQ1NCcg%40mail.gmail.com <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkRSRSbFSKqqm--z%3Dmzuyp0v%2Bq4nrh7%2Buexd_0otQ1NCcg%40mail.gmail.com?utm_medium=email&utm_source=footer>.____

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of
> Conduct.
> NV Access expects that all community members will read and abide by
> the rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-user...@nvaccess.org>.

> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/0f2d01dd0313%2433a3d5e0%249aeb81a0%24%40gmail.com <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/0f2d01dd0313%2433a3d5e0%249aeb81a0%24%40gmail.com?utm_medium=email&utm_source=footer>.____

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of
> Conduct.
> NV Access expects that all community members will read and abide by
> the rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-users%2Bman...@nvaccess.org>.

> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00bc01dd0317%2461ffd430%2425ff7c90%24%40comcast.net <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00bc01dd0317%2461ffd430%2425ff7c90%24%40comcast.net?utm_medium=email&utm_source=footer>.

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
> NV Access expects that all community members will read and abide by the
> rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org.
> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkRf28%3D1KfT_c3Fzitk_9z9GHV_u2yfpJF%3Dy14f%2BMyShPg%40mail.gmail.com <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkRf28%3D1KfT_c3Fzitk_9z9GHV_u2yfpJF%3Dy14f%2BMyShPg%40mail.gmail.com?utm_medium=email&utm_source=footer>.

[Gene Asner]

You won't get any attention by asking agencies that do no such
enforcement and, as far as I know, have no jurisdiction to act on the
matter. Just contacting this or that agency with no idea if it even has
jurisdiction is a waste of everyone's time, including yours.

Gene

On 6/23/2026 9:27 AM, Obaida Tamimi wrote:
> Hi Richard,
>
> I appreciate the suggestion. However, I have already engaged with
> various regulatory bodies, including the FTC and other relevant
> authorities, in the past regarding this exact issue.
>
> Unfortunately, as many of us have experienced, these channels often
> result in a "dead end" where the issue is either ignored or redirected
> indefinitely. That is precisely why I am exploring different, perhaps
> less conventional, avenues to get some attention to this systemic failure.
>
> While I agree that the problem lies with hardware manufacturers, it
> seems that until we find a way to make them legally or socially
> accountable, these technical barriers will persist.
>
> Best regards,
> Obaida
>
>
> في ثلاثاء، 23 يونيو، 2026 في 5:17 م، كتب 'Richard Turner' via NVDA
> Screen Reader Discussion <nvda-...@nvaccess.org

> <mailto:nvda-...@nvaccess.org>>:
>
> I think you are targeting the wrong group for escalating this issue.____

>
> You would be better off focusing on the regulatory offices that

> oversee manufacturing.____

>
> For the US, I would start with the Federal Trade Commission FTC, and
> the Attorney General's office, possibly starting with the State you

> reside in if you live in the US.____
>
> Otherwise, whomever regulates business practices where you live.____
>
> This has absolutely nothing to do with the Internet.____
>
> It has everything to do with accessibility to hardware.____

>
> __ __
>
> __ __
>
> __ __
>
> Richard, USA,____
>

> The only way to make sense out of change is to plunge into it, move

> with it, and join the dance." ____
>
> -- Alan Watts (1915-1973)____
>
> __ __
>
> My web site: https://www.turner42.com <https://www.turner42.com/>____
>
> __ __
>
> __ __
>
> *From:*nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>
> <nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>> *On

> Behalf Of *Obaida Tamimi
> *Sent:* Tuesday, June 23, 2026 7:02 AM

> *To:* nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>

> *Subject:* Re: [NVDA] Re: Escalating the issue of inaccessible
> BIOS/UEFI to the FBI (IC3)____
>
> __ __

>
> Hi Shaun and Richard,
>
> Thank you for your candid feedback and for sharing your technical
> perspective. I completely understand that there are no sound drivers
> at the BIOS level and that this is a long-standing, complex challenge.
>
> However, I believe that classifying this solely as a technical
> hurdle often leads us to a dead end. Whether or not it is an
> "internet crime" in the eyes of the IC3, my goal is to frame this as
> an accessibility rights issue. If we do not push for accountability
> from hardware manufacturers at a systemic level, we will continue to
> face these same barriers indefinitely.
>
> I appreciate your insights, but I feel that continuing to highlight
> this issue to official channels is a necessary step to eventually
> force manufacturers to prioritize accessibility in firmware design.
>
> Best regards,

> Obaida____
>
> __ __
>
> __ __
>

> في ثلاثاء، 23 يونيو، 2026 في 4:51 م، كتب 'Richard Turner' via NVDA
> Screen Reader Discussion <nvda-...@nvaccess.org

> <mailto:nvda-...@nvaccess.org>>:____

>
> The problem since time began is that there are no sound drivers

> at the bios level.____
>
> ____
>
> Find a way around that, and we will have access to the bios.____
>
> ____
>
> ____
>
> ____
>
> Richard, USA,____

>
> The only way to make sense out of change is to plunge into it,

> move with it, and join the dance." ____
>
> -- Alan Watts (1915-1973)____
>
> ____
>

> My web site: https://www.turner42.com

> <https://www.turner42.com/>____
>
> ____
>
> ____

>
> *From:*nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>
> <nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>> *On
> Behalf Of *blind...@gmail.com <mailto:blind...@gmail.com>
> *Sent:* Tuesday, June 23, 2026 6:21 AM
> *To:* nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>

> *Subject:* RE: [NVDA] Re: Escalating the issue of inaccessible
> BIOS/UEFI to the FBI (IC3)____
>
> ____

>
> I do not believe the IC3 is going to want anything to do with
> this issue as it is not an internet crime to choose whether or

> not to make UEFI or BIOS accessible.____
>
> ____

>
> This is an ongoing issue that we have face since time
> immemorial, and, I suspect this is an issue we are going to
> continually face as firmware changes and interfaces change. To

> keep up with computer hardware.____
>
> ____

>
> I’m about to use a crass saying here, however it applies. While
> ever your arsehole points to the ground, you are going to face
> the problem of everchanging firmware and everchanging

> interfaces.____
>
> ____

>
> How, for one would you apply that accessibility, when firstly,
> you are at the bare bones of the hardware itself and can, if you
> make a mistake, render your machine inoperable. And secondly,
> there is no sound at that point as you likely cannot access it

> at that stage of the boot up process.____
>
> ____

>
> I like many of us on here would love to gain access to that part
> of the system as it will assist my own efforts in computer
> management, however, on occasion, and I believe this to be one
> of them, unless we get a universal UEFI or BIOS, this, will,

> not, happen!____
>
> ____

>
> I would strongly advise not wasting the FBI’s time on this
> matter, as it’s not a matter for them to be dealing with in the

> first place.____
>
> ____
>
> ____
>
> ____
>
> Shaun Oliver____
>
> ____
>
> VK5ESE____
>
> ____
>
> Adaptive technology consultant____
>
> ____
>
> Mobile: +61 477 83-6199____
>
> ____

>
> *From:*nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>
> <nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>> *On
> Behalf Of *Obaida Tamimi

> *Sent:* Tuesday, 23 June 2026 04:50

> *To:* nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>

> *Subject:* [NVDA] Re: Escalating the issue of inaccessible
> BIOS/UEFI to the FBI (IC3)____
>
> ____

>
> Hi everyone,
>
> I'm frustrated by the constant barrier of inaccessible BIOS/UEFI
> settings. As a screen reader user, this keeps me from managing
> my own computer independently.
>
> I’m currently escalating this issue to the FBI (IC3) because,
> frankly, it’s not just a technical inconvenience—it’s a matter
> of rights and independence that manufacturers keep ignoring.
>
> I wanted to share this with the community. We shouldn't have to
> accept that our hardware remains off-limits to us.
>
> Best,

> Obaida____
>
> ____
>
> ____

>
> فيثلاثاء،23 يونيو،2026 في12:07 م،كتبObaida Tamimi
> <altamim...@gmail.com <mailto:altamim...@gmail.com>>:____
>
> ____
>
> ____
>
> فيثلاثاء،23 يونيو،2026 في5:00 ص،كتبNVDA Screen Reader
> Discussion____
>

> Dear NVDA community,
>
> I am writing to share a critical issue regarding the
> accessibility of hardware BIOS/UEFI settings, which I am
> currently escalating to the FBI's Internet Crime Complaint
> Center (IC3).
>
> I have faced persistent barriers in accessing these
> essential settings, which prevent me from managing my
> computer independently. I believe this lack of accessibility
> is a serious concern that affects users' rights and ability
> to utilize their technology effectively.
>
> I wanted to bring this matter to your attention as part of
> my ongoing efforts to seek accountability and ensure that
> accessibility is prioritized by hardware manufacturers and
> firmware developers.
>
> Thank you for your time and for the vital work you do in
> supporting the screen reader community.
>
> Best regards,

> Obaida____
>
> <nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>>:____
>
> Hi all,____
>

> Beta4 of NVDA 2026.2 is now available for download and
> testing. Please see the original thread message for more

> information about the release and beta testing.____
>
> Download:
> https://www.nvaccess.org/post/nvda-2026-2beta4/
> <https://www.nvaccess.org/post/nvda-2026-2beta4/>____
>
> Changes introduced in Beta 4: ____
>
> * Updates to translations____

> * Changed the button layout in the “Add dictionary
> entry” dialog to vertical____
> * Changed the magnifier tracking from the center of an

> object to the start (e.g. top-left for left-to-right

> languages)____
> * Fixed saving comments in speech dictionaries____
> * Added a debug log category for magnifier____
> * Improvements to Magnifier settings names and layout____
>
> ____

>
> On Tuesday, June 16, 2026 at 10:46:34 AM UTC+10 NVDA

> Screen Reader Discussion wrote:____
>
> Hi all,____

>
> Beta3 of NVDA 2026.2 is now available for download
> and testing. Please see the original thread message
> for more information about the release and beta

> testing.____
>
> Download:
> https://www.nvaccess.org/post/nvda-2026-2beta3/
> <https://www.nvaccess.org/post/nvda-2026-2beta3/>____
>

> Changes introduced in Beta 3:____
>
> * Pressing NVDA+control+w on secure screens now
> opens Magnifier settings as expected.____
> * Highlighter and Magnifier now follow the focused
> cell in Excel____
>
> * Improvements to Magnifier settings names and
> layout____

>
> On Tuesday, June 2, 2026 at 11:06:15 AM UTC+10 NVDA

> Screen Reader Discussion wrote:____

>
> Beta1 of NVDA 2026.2 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 you to download the beta
> and provide feedback using our issue reporting
> process

> <https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/readme.md>. By installing the beta you will be opting into NVDA’s beta channel, and will only receive update notifications for beta and release candidate (RC) builds. The beta/RC channel will always keep you up to date with the latest NVDA version. The last RC in a release cycle is identical to the final stable release. To return to the stable release channel, upgrade manually to the latest stable build <https://www.nvaccess.org/download/>.____
>
> Links ____
>
> * Download NVDA 2026.2beta1
> <https://download.nvaccess.org/releases/2026.2beta1/nvda_2026.2beta1.exe> ____
>
> o SHA256 sum:
> 25b0f893f6a45017d4e8f1388e45feb8707052baafc47af713332de6fde5dd48____
>
> * What’s new in this release of NVDA
> <https://download.nvaccess.org/releases/2026.2beta1/documentation/changes.html>____
> * Please report any issues on GitHub
> <https://github.com/nvaccess/nvda/issues>.____
>
> Highlights ____
>

> This release includes a new built-in Magnifier
> feature, improvements to touch gestures and
> navigation, and expanded speech and braille

> capabilities.____

>
> The Magnifier provides zoom and color filtering
> options to assist users with visual impairments.
> The Magnifier currently only supports fullscreen
> mode, with docked modes planned in a future

> release.____

>
> Touch support has been significantly expanded
> with new pinch gestures and touch-based browse
> mode navigation for web content. You can now
> navigate between links, headings, form fields,

> and other elements using touch flicks.____

>
> Speech features have been enhanced with support
> for custom speech dictionaries that can be
> provided by add-ons and new dictionary entry
> types for more granular control. A new voice
> setting for OneCore voices was added to control
> pauses after punctuation. A new command allows
> repeating the last spoken information, with the
> ability to display it in a browsable message.
> The default gesture to repeat the last spoken
> information is NVDA+x, which can be changed in

> the Input Gestures dialog.____

>
> The braille display can now automatically scroll
> and DotPad devices support multi-button

> combinations.____

>
> Liblouis has been updated with new Italian and

> Estonian braille tables.____

>
> When resetting NVDA to factory defaults, an Undo
> button is now available to restore the previous

> configuration.____
>
> NVDA logo on a purple background____
>
> ____

>
> --
> ***
> Please note: the NVDA project has a Citizen and
> Contributor Code of Conduct.
> NV Access expects that all community members will read
> and abide by the rules set out in this document while
> participating in this group.

> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>

>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-users%2Bman...@nvaccess.org>.

> ---
> You received this message because you are subscribed to
> the Google Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails
> from it, send an email to
> nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/e09caaab-14e3-417c-b89d-a50bbeea184cn%40nvaccess.org <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/e09caaab-14e3-417c-b89d-a50bbeea184cn%40nvaccess.org?utm_medium=email&utm_source=footer>.____

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code
> of Conduct.
> NV Access expects that all community members will read and abide
> by the rules set out in this document while participating in
> this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-user...@nvaccess.org>.

> ---
> You received this message because you are subscribed to the
> Google Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkRSRSbFSKqqm--z%3Dmzuyp0v%2Bq4nrh7%2Buexd_0otQ1NCcg%40mail.gmail.com <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkRSRSbFSKqqm--z%3Dmzuyp0v%2Bq4nrh7%2Buexd_0otQ1NCcg%40mail.gmail.com?utm_medium=email&utm_source=footer>.____

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code
> of Conduct.
> NV Access expects that all community members will read and abide
> by the rules set out in this document while participating in
> this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-user...@nvaccess.org>.

> ---
> You received this message because you are subscribed to the
> Google Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/0f2d01dd0313%2433a3d5e0%249aeb81a0%24%40gmail.com <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/0f2d01dd0313%2433a3d5e0%249aeb81a0%24%40gmail.com?utm_medium=email&utm_source=footer>.____

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code
> of Conduct.
> NV Access expects that all community members will read and abide
> by the rules set out in this document while participating in
> this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-users%2Bman...@nvaccess.org>.

> ---
> You received this message because you are subscribed to the
> Google Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00bc01dd0317%2461ffd430%2425ff7c90%24%40comcast.net <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00bc01dd0317%2461ffd430%2425ff7c90%24%40comcast.net?utm_medium=email&utm_source=footer>.
>
> ____

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of
> Conduct.
> NV Access expects that all community members will read and abide by
> the rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-user...@nvaccess.org>.

> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkS62QFfeKoLannxwaf%3D%3Dw%3D8g9%2BuKDnv79ScHuzxNWgQnA%40mail.gmail.com <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkS62QFfeKoLannxwaf%3D%3Dw%3D8g9%2BuKDnv79ScHuzxNWgQnA%40mail.gmail.com?utm_medium=email&utm_source=footer>.____

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of
> Conduct.
> NV Access expects that all community members will read and abide by
> the rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org

> <mailto:nvda-users%2Bman...@nvaccess.org>.

> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00ef01dd031b%2409e9f1f0%241dbdd5d0%24%40comcast.net <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00ef01dd031b%2409e9f1f0%241dbdd5d0%24%40comcast.net?utm_medium=email&utm_source=footer>.

>
> --
> ***
> Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
> NV Access expects that all community members will read and abide by the
> rules set out in this document while participating in this group.
> https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
> <https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md>
>
> You can contact the group owners and moderators via
> nvda-user...@nvaccess.org.
> ---
> You received this message because you are subscribed to the Google
> Groups "NVDA Screen Reader Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to nvda-users+...@nvaccess.org

> <mailto:nvda-users+...@nvaccess.org>.

> To view this discussion visit

> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkS%3Dq7d2SUTj0bFOeFXQNdJqxddktaR3YjNF39X0v6bvag%40mail.gmail.com <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkS%3Dq7d2SUTj0bFOeFXQNdJqxddktaR3YjNF39X0v6bvag%40mail.gmail.com?utm_medium=email&utm_source=footer>.

[tim m]

Ben there and done all that back in the 90's with GwMicro.

We had a board that fit in a expansion slot hooked to a doubleTalk.

The problem was in navigating the screen to read it instead of getting it all in one chunk.

The project died when windows xp came out and funding went byby from government.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkS62QFfeKoLannxwaf%3D%3Dw%3D8g9%2BuKDnv79ScHuzxNWgQnA%40mail.gmail.com.

[NVDA Screen Reader Discussion]

Hi all,

This conversation (despite the subject header) is currently hijacking the 2026.2 release thread (see quoted replies to see how the thread started).
Please explicitly start a new thread for this, this thread is for discussing the 2026.2 release cycle.
I will be locking this thread until the next beta to ensure the conversation stops.
Please do not reply to this message unless you intend to discuss the 2026.2 beta.

Thanks

You can contact the group owners and moderators via nvda-users+managers@nvaccess.org.

---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+unsubscribe@nvaccess.org.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/e09caaab-14e3-417c-b89d-a50bbeea184cn%40nvaccess.org.

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 

You can contact the group owners and moderators via nvda-users+managers@nvaccess.org.

---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+unsubscribe@nvaccess.org.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/CAO0BCkRSRSbFSKqqm--z%3Dmzuyp0v%2Bq4nrh7%2Buexd_0otQ1NCcg%40mail.gmail.com.

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 

You can contact the group owners and moderators via nvda-users+managers@nvaccess.org.

---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+unsubscribe@nvaccess.org.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/0f2d01dd0313%2433a3d5e0%249aeb81a0%24%40gmail.com.

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 

You can contact the group owners and moderators via nvda-users+managers@nvaccess.org.

---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+unsubscribe@nvaccess.org.

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/00bc01dd0317%2461ffd430%2425ff7c90%24%40comcast.net.

--
***
Please note: the NVDA project has a Citizen and Contributor Code of Conduct.
NV Access expects that all community members will read and abide by the rules set out in this document while participating in this group.
https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md
 

You can contact the group owners and moderators via nvda-users+managers@nvaccess.org.

---
You received this message because you are subscribed to the Google Groups "NVDA Screen Reader Discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nvda-users+unsubscribe@nvaccess.org.