Community proposal: a table of screen reader settings equivalents

[joseph....@gmail.com]

Hi all,

In light of NV Access In-Process blog post on moving from JAWS to NVDA (see Quentin’s earlier post) and a discussion on community spaces on NVDA settings equivalent to JAWS settings, I would like to propose that the community work on a document listing equivalent settings between screen readers. From time to time the community receives comments such as “I wish NVDA had this JAWS setting” when in fact NVDA does have an equivalent setting. Having a document that maps settings across screen readers can be another resource we can point people to as folks move between screen readers.

Regarding who should work on it: anyone is welcome to work on it, but I would like to request that people moving from JAWS to NVDA (and vice versa) take the initiative in this effort. First, this allows new NVDA users to read the existing documentation and experiment with NVDA settings to learn which setting corresponds to ones used in other screen readers. Second, this allows document writers to point out inconsistencies or confusing aspects of NVDA user guide and other documentation and can serve as an indirect feedback to NV Access and the community.

Thanks.

Cheers,

Joseph

[Ed Marquette]

Joseph:

This is just a question of clarification. You spoke of a kind of table showing corresponding "settings" across screen readers. Are you talking about "settings" in a strict sense, e.g.,  the on/off setting for reading text attributes, or are you talking about corresponding "functions," e.g., Insert + F7 displays a list of links in JAWS while Insert + F-7 in NVDA displays a list of elements, including links?

---

From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> on behalf of joseph....@gmail.com <joseph....@gmail.com>
Sent: Friday, January 23, 2026 17:25
To: nvda-...@nvaccess.org <nvda-...@nvaccess.org>
Subject: [NVDA] Community proposal: a table of screen reader settings equivalents

 

--
***
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/000201dc8cbf%249d142ea0%24d73c8be0%24%40gmail.com.

[joseph....@gmail.com]

Hi,

For now, let’s focus on settings.

Cheers,

Joseph

To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/DM6PR11MB35638E2A531D6C08AFEAC021F795A%40DM6PR11MB3563.namprd11.prod.outlook.com.

[Quentin Christensen]

Hi Joseph and everyone,

I think this is a great idea - I'm not sure what you had in mind for a document, but I feel such a table would be a great addition to the existing page, rather than a separate resource.  Certainly a lot of it could be informed by the content on the existing page, and as other rows are added, it might also prompt new paragraphs in the text of the rest of the page as well (I envisage such a table could be a quick reference of commands, with much of the rest of the page clarifying where things are different, or even similar but different).

Kind regards

Quentin

--

***
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/000201dc8cbf%249d142ea0%24d73c8be0%24%40gmail.com.

--

Quentin Christensen

Training and Support Manager

NV Access

www.nvaccess.org 

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

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

Subscribe to email updates (blog, new versions, etc): https://eepurl.com/iuVyjo

User group: https://groups.google.com/a/nvaccess.org/g/nvda-users

Other groups: https://github.com/nvaccess/nvda/wiki/Connect 

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

Facebook: http://www.facebook.com/NVAccess 

[Sarah Alawami]

I'm thinking sections and braking the table up to prevent cognitive load. so, a section  for x, then table. then section for y then table etc,. Thoughts?

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