FW: [Tech-VI] From Darrell Shandrow Hilliker: One Week with NVDA: A JAWS User’s Immersion Journey
Richard Turner
David Goldfield just posted the below to his Tech-VI list and I thought it worth forwarding here.
One Week with NVDA: A JAWS User’s Immersion Journey
February 21, 2026 by Darrell Shandrow Hilliker
What started as a seven-day experiment ended with a new primary screen reader.
I’ll be honest: I didn’t expect this to go the way it did. On February 14th, 2026, I set myself a challenge — use NVDA exclusively on my personal computer for one full week, switching back to JAWS only if my work required it. I’ve been a longtime JAWS user, and NVDA has always been on my radar as the powerful, free, open-source alternative. But radar is different from reality. So I dove in.
One week later — and several days beyond that — I’m still running NVDA. It has become my primary Windows screen reader. I won’t be abandoning JAWS entirely; both tools have their place. But if you’ve been on the fence about giving NVDA a serious try, read on. Here’s everything that happened.
Day 1 (February 14): First Impressions and the Punctuation Problem
The very first thing that tripped me up was punctuation. NVDA defaults to “some” punctuation, while I was accustomed to “most” in JAWS. The practical effect: symbols like the underscore were being silently skipped. I switched to “most” punctuation right away, and that helped — but it opened its own can of worms.
In “most” mode, NVDA announces the underscore as “line.” I found that maddening. The colon inside timestamps (insert+F12 for the time) was also being spoken aloud, which felt odd. These were small things, but they added up quickly.
I also explored the NVDA Addon Store. It’s a great concept, but I found the execution a bit rough — many addons lack solid documentation, and reading user reviews means navigating away to an external website. There’s room to grow here.
One more early grievance: common commands like Control+C and Control+S are completely silent in NVDA. You press copy or save and hear… nothing. The option to speak command keys does exist, but it makes everything chatty — tab, arrows, all of it. That’s not what I wanted either.
Day 2 (February 15): Muscle Memory Wars and Customization Overload
Day two was the most turbulent. My JAWS muscle memory fought me at every turn, and I spent a significant portion of the day not doing productive work but rather reconfiguring NVDA to survive.
Browse Mode and Focus Mode were a constant source of confusion. In JAWS, Semi Auto Forms Mode handles a lot of this context-switching behind the scenes. With NVDA, I found myself stuck in the wrong mode repeatedly. A simple example: after submitting a prompt to Gemini and hearing its reply, I pressed H to navigate to the heading where the response started. NVDA just said “h” and sat there. I was still in Focus Mode. Insert+Space toggled Browse Mode on and then everything worked — but I had to consciously remember to do that. This will likely get easier with time, but on day two, it was genuinely frustrating.
I remapped a fistful of commands to save my sanity. The NVDA find command in Browse Mode is Control+NVDA+F — not Control+F — which felt deeply wrong. I added Control+F, F3, and Shift+F3 under Preferences > Input Gestures. I also kept repeatedly bumping into Insert+Q being the command to exit NVDA rather than announcing the active application, which nearly gave me a heart attack the first time it happened. I enabled exit confirmation in Preferences > General, then later reassigned Insert+Q to announce the focused app and moved the exit command to Insert+F4.
The underscore-as-“line” issue got its resolution today. The fix wasn’t in NVDA’s speech dictionaries as I first expected — it was in Preferences > Punctuation/Pronunciation. Problem solved. I also tackled the exclamation mark, which sits in the “all” punctuation tier rather than “most.” I mapped it to announce as “bang” when it appears mid-sentence.
There was also a frustrating addon conflict: the NVDA+Shift+V keystroke, officially assigned to announce an app’s version number, was instead being intercepted by the Vision Assistant Pro addon to open its command layer. Addon keystrokes can silently override core NVDA functionality — something worth knowing. I ended up assigning Control+NVDA+V to get version info.
One gap I noticed that NVDA doesn’t yet fill: quickly reading the current page’s URL without shifting focus to the address bar. JAWS handles this with Insert+A. NVDA doesn’t have an equivalent. Alt+D works, but it moves focus, which isn’t always what I want.
Day 3 (February 16): The Good, The Annoying, and a Genuine Win
By day three — President’s Day — I was settling into something like a rhythm, though NVDA was still throwing surprises at me.
One thing I couldn’t crack was typing echo. In JAWS, I run character-level echo at a much higher speech rate than everything else. This gives me fast, confident confirmation of each keystroke without slowing down general speech. NVDA doesn’t appear to support different speech rates per context, so typed characters come through at the same rate as everything else. I know I can’t be the only person who relies on this, so I kept digging — but no solution yet.
I also noticed a recurring issue: NVDA going silent after focus changes. Closing Excel or Word and returning to File Explorer? Silence. Switching browser tabs with Control+Tab? Sometimes silence. This felt like potential bug territory.
PDFs were another pain point. I work with many poorly tagged PDFs, and NVDA with Adobe Reader exposes every formatting flaw without mercy. JAWS has historically done more smoothing and pre-processing before those errors reach the user. I’m withholding final judgment here — there are third-party PDF tools that work well with NVDA, and I planned to test them.
I experimented briefly with turning off automatic say-all on page load to reduce repetitive speech on websites. Bad idea. After toggling an action, nothing was announced — I had to manually navigate just to figure out where I had ended up. I turned it back on immediately.
The genuine win of the day: the Vision Assistant Pro addon. While working on a freelance project that required a visual description of a web page’s layout, I pressed NVDA+Alt+V then O for an on-screen description. Within seconds I had exactly what I needed. A follow-up question was answered just as quickly. Cross-checking with other tools confirmed the accuracy. This was an impressive moment and a real argument for NVDA’s addon ecosystem.
Day 4 (February 17): The 32-Bit Revelation and Eloquence Arrives
I learned something on day four that genuinely surprised me: NVDA 2025.3.3, the current stable release, is 32-bit. I had assumed for years that I was running a 64-bit screen reader. This discovery came about through an unexpected path.
I came across a link to a 64-bit version of the Eloquence speech synthesizer built for NVDA. Excited, I installed it and restarted — only to find NVDA using Windows OneCore voices with no trace of Eloquence. After posting about it on Mastodon, the community quickly pointed out the 32-bit issue. The 64-bit Eloquence addon requires a 64-bit NVDA, which only exists in the 2026 beta builds. I grabbed the beta, installed everything, and was finally running Eloquence on NVDA. The 64-bit upgrade is coming in the official 2026.1 release — well worth watching for.
I also continued searching for an NVDA equivalent to JAWS’s Shift+Insert+F1, which gives a detailed browser-level view of an element’s tags, attributes, roles, and IDs. This is invaluable for accessibility work. I hadn’t found a satisfying answer by end of day.
Day 5 (February 18): Discovering NVDA in Microsoft Word
I don’t often think of Browse Mode as a Word feature, so I was pleasantly surprised to learn — after reading some documentation — that NVDA supports a version of it in Word, allowing quick navigation by headings using the H key. This made my document work much more manageable.
I also received another update to 64-bit Eloquence, which fixed bugs I hadn’t even noticed. As for the work computer, I decided against installing the NVDA beta there — my employer deserves results from the stable release. That upgrade will wait for the official 2026.1 launch.
Day 6 (February 19): The Quiet Day
Day six was uneventful in the best possible way. I used my computer heavily and NVDA just worked. No major incidents, no emergency remappings. I noticed I was reaching for JAWS less and less in my thoughts. That felt significant.
Day 7 (February 20): Amateur Radio and a Happy Ending
The final day of the official challenge coincided with the start of the ARRL International DX CW (Morse Code) contest — one of the bigger amateur radio events of the year. I was curious how N3FJP’s contest logging software would hold up with NVDA, since this is specialized, legacy-adjacent software that doesn’t rely on standard accessibility APIs.
The answer: it worked great — and actually felt snappier than with JAWS. The one wrinkle was reviewing the call log. The standard screen review commands on the numpad didn’t yield useful information at first. The solution was object navigation. By pressing NVDA+Numpad 8 to climb to the parent object (“call window”), I found that each column in the log is its own object. Navigating with NVDA+Numpad 4, 5, and 6 moved between objects at the same level, announcing “Rec Window,” “PWR Window,” “Country Window,” “Call Window,” and so on. From there, Numpad 9 and 7 moved through the log in reverse chronological order. Once I understood the structure, it worked beautifully.
My two radio control apps — JJRadio and Kenwood’s ARCP software — also worked flawlessly. Just when I was expecting NVDA to hit its limits, it didn’t.
What NVDA Does Really Well
After a week of intensive use, here’s what impressed me most:
· Speed and responsiveness. NVDA frequently felt faster than JAWS, especially in applications like the N3FJP logging software.
· Deep customizability. The Input Gestures system makes it relatively easy to remap commands. Preferences > Punctuation/Pronunciation gives granular control.
· The addon ecosystem. Despite rough edges, the Vision Assistant Pro addon alone demonstrated real power. The 64-bit Eloquence support is also a significant upgrade.
· Object navigation. Once I understood NVDA’s object model, navigating legacy and non-standard interfaces became genuinely manageable.
· Cost. NVDA is free, actively developed, and open source. The value proposition is extraordinary.
Where NVDA Still Has Room to Grow
· Silent focus changes. NVDA going quiet after closing apps or switching tabs is disorienting and may be a bug worth filing.
· PDF handling. Poorly tagged PDFs hit differently with NVDA than with JAWS, which smooths many errors before they reach the user.
· Typing echo speech rate. The inability to set a faster speech rate specifically for typed characters is a real productivity gap for fast typists.
· Element inspection. JAWS’s Shift+Insert+F1 for examining element attributes has no obvious NVDA equivalent, which matters for accessibility work when I just need to start with a quick-and-dirty answer before digging deeper into the code.
· URL reporting without focus change. A read-only way to hear the current page address — without moving focus to the address bar — is missing.
· Addon documentation and conflict resolution. Keystroke conflicts between addons and core NVDA aren’t surfaced clearly enough.
The Verdict: One Week Became the New Normal
I went in expecting to survive a week and then gratefully return to JAWS. Instead, I’m writing this article as an NVDA user. The first two days were genuinely hard — partly NVDA’s rough edges, partly years of JAWS muscle memory fighting back. But by day six, NVDA was simply humming along, and I wasn’t thinking about JAWS at all.
For experienced JAWS users considering a serious NVDA trial, my main advice is this: budget real time for reconfiguration in the first two days. The defaults won’t feel right. But the tools to make NVDA feel right are mostly there — they just require some digging. Preferences > Punctuation/Pronunciation and Input Gestures will be your best friends.
JAWS isn’t going anywhere in my toolkit. For professional accessibility auditing, PDF work, and certain specialized contexts, it remains the gold standard. But for day-to-day use on my personal computer? NVDA has earned the top spot.
The 2026.1 release — bringing official 64-bit support — is going to be a milestone worth watching. If you’ve been waiting for a good moment to give NVDA a real chance, that moment is here, now.
Sources
This article is primarily a firsthand account based on my direct experience. The following resources document or corroborate the specific factual claims made in the article.
· NV Access: NVDA 2025.3.3 Released — Official release announcement for the stable version of NVDA tested throughout this article, confirming it is a 32-bit build.
· NV Access: In-Process, 10th February 2026 — NV Access’s own blog post confirming that NVDA 2026.1 is the first 64-bit release, and discussing the scope of that transition.
· NV Access: NVDA 2026.1 Beta 3 Available for Testing — The beta release announcement for the 64-bit version of NVDA referenced in the Day 4 entry.
· NVDA 2025.3.3 User Guide — The official NVDA documentation covering Browse Mode, Focus Mode, Input Gestures, object navigation, Punctuation/Pronunciation settings, and the Add-on Store — all features discussed throughout the article.
· N3FJP’s ARRL International DX Contest Log — The official page for the N3FJP contest logging software tested with NVDA on Day 7.
· ARRL International DX Contest — The American Radio Relay League’s official page for the ARRL International DX CW contest referenced in the Day 7 entry.
Categoriesaccessibility, Amateur Radio, assistive technology, JAWS, Nonvisual Desktop Access, reviews, thought provoker, Uncategorized
David Goldfield,
Blindness Assistive Technology Specialist
Director of Marketing,
Blazie Technologies
Am Yisrael Chai
The Nation of Israel Lives!
Subscribe to the Tech-VI announcement list to receive blindness technology news, events and information.
Email: tech-vi+...@groups.io
HTH,
Richard, USA,
he 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
Gene Asner
screen-reader but there are certain things that in my opinion, he
shouldn't have done in this article.
First, he discussed an Eloquence add-on that is not legal. Any
Eloquence add-on that is free is, by definition, not legal. This
shouldn't have been done in an article that, it is reasonably
foreseeable, as our legal brothers and sisters say, will be sent widely
to e-mail lists, which generally don't allow discussion and promotion of
illegal software.
Second, I have never seen the silence problem he spoke of discussed
before and I have never encountered it. He writes of a problem he
encountered as though it is global. Performance problems should not be
generalized from one user. It is just one user's experience and that
should have been stated. Then, there is the remapping of key strokes.
This is recommended. It should have been stated as what he prefers and
did. Others may not wish to remap anything or much of anything.
As to particularly good points in the article, the writer spoke about
object navigation, something any demanding user of NVDA needs to know
and far too many people don't. He demonstrated that even with the time
and trouble it took him to adjust, the transition was still very worth
it for a demanding user such as himself, thus helping break down the
prejudice against NVDA that it is not a truly capable screen-reader. He
spoke of it being more responsive, which it is.
In general, it is a good article and it may encourage more people to try
NVDA.
Two last points:
This is not criticism, but with the emphasis the author placed on using
JAWS commands, he doesn't evidently know about the Numpad mode add-on,
which allows the JAWS read to end command to be used, numpad insert,
numpad 2. I don't expect someone as a new NVDA user to know about all
add-ons but I'm point this add-on out in case people may want to use the
command and don't know of the add-on. Although it isn't being
maintained, it works in NVDA 2026.x. I tried it in the beta. Of
course, you need to override incompatibility.
Also, the writer is evidently unaware of how to find documentation for
add-ons by using the add-on store. It is available, if you know how.
Gene
Sean Randall
he's also perfectly entitled to discuss it on his own private blog. Which he's done.
Thanks
Sean
On 22 Feb 2026, at 05:34, Gene Asner <gsa...@gmail.com> wrote:
Of course, I'm pleased the writer switched to NVDA as his main screen-reader but there are certain things that in my opinion, he shouldn't have done in this article.
***
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/ef8f231e-b104-4882-ab49-4292a7bfbe5b%40gmail.com.
Steve Nutt
That was instructive I have to say.
The one area that surprised me is that Darrell didn’t realise that NVDA supports browse mode in Word. Does that mean he didn’t know JAWS does either?
If not, it certainly does.
I don’t know what he uses for Email, but I still maintain that NVDA is a bit inefficient in Outlook, having to press Say All for most messages to be read out after opening them is a pain, but most of this I certainly agree with.
All the best
Steve
--
Computer Room Services
77 Exeter Close, Stevenage, Hertfordshire, SG1 4PW
--
***
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/045e01dca393%24ee31e6c0%24ca95b440%24%40comcast.net.
Andy Baracco
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/126f01dca5ae%24b5b0aee0%2421120ca0%24%40comproom.co.uk.
mrsi...@sasktel.net
N v d a key plus down arrow cursor keys, arrow keys
Monte Single
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/003901dca5b2%242d820650%240b01a8c0%40AndyPC.
Martina Letochová
Martina
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/003901dca5b2%242d820650%240b01a8c0%40AndyPC.
stallio...@gmail.com
When you say “Down arrow” which down arrow are you referring to?
Andy
From: nvda-...@nvaccess.org <nvda-...@nvaccess.org> On Behalf Of Martina Letochová
Sent: Tuesday, February 24, 2026 9:36 AM
To: nvda-...@nvaccess.org
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/1dc31acb-161a-4575-8848-12528a74c33e%40seznam.cz.
Gene Asner
numpad. I find that command so annoying that I use the caps lock as an
NVDA modifier and issue the command, caps lock down arrow.
Gene
On 2/24/2026 2:27 PM, stallio...@gmail.com wrote:
> When you say “Down arrow” which down arrow are you referring to?
>
> Andy
>
> *Martina Letochová
> *Sent:* Tuesday, February 24, 2026 9:36 AM
> *To:* nvda-...@nvaccess.org
> *Subject:* Re: [NVDA] FW: [Tech-VI] From Darrell Shandrow Hilliker: One
>
> NVDA+DownArrow in the desktop layout, NVDA+A in the laptop layout.
> Martina
>
> On 24.02.2026 18:22, Andy Baracco wrote:
>
> What is the "say all" command for NVDA?
>
> Andy
>
> ----- Original Message -----
>
>
> *To:*nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>
>
> *Sent:*Tuesday, February 24, 2026 8:57 AM
>
> *Subject:*RE: [NVDA] FW: [Tech-VI] From Darrell Shandrow
>
> That was instructive I have to say.
>
> The one area that surprised me is that Darrell didn’t realise
> that NVDA supports browse mode in Word. Does that mean he didn’t
> know JAWS does either?
>
> If not, it certainly does.
>
> I don’t know what he uses for Email, but I still maintain that
> NVDA is a bit inefficient in Outlook, having to press Say All
> for most messages to be read out after opening them is a pain,
> but most of this I certainly agree with.
>
> All the best
>
>
> Steve
>
> --
>
> Computer Room Services
>
> 77 Exeter Close, Stevenage, Hertfordshire, SG1 4PW
>
> T: +44(0)1438-742286, M: +44(0)7956-334938
>
> https://www.comproom.co.uk <https://www.comproom.co.uk/>
>
> *From:*'Richard Turner' via NVDA Screen Reader Discussion
> <nvda-...@nvaccess.org> <mailto:nvda-...@nvaccess.org>
> *Sent:* 22 February 2026 00:41
> *To:* nvda-...@nvaccess.org <mailto:nvda-...@nvaccess.org>
> *Subject:* [NVDA] FW: [Tech-VI] From Darrell Shandrow Hilliker:
>
> David Goldfield just posted the below to his Tech-VI list and I
> thought it worth forwarding here.
>
> Original Source
>
> One Week with NVDA: A JAWS User’s Immersion Journey
>
> February 21, 2026by Darrell Shandrow Hilliker
>
> /What started as a seven-day experiment ended with a new primary
> screen reader./
> throughout this article, confirming it is a 32-bit build.
>
> ·NV Access: In-Process, 10th February 2026
> 64-bit release, and discussing the scope of that transition.
>
> ·NV Access: NVDA 2026.1 Beta 3 Available for Testing
> in the Day 4 entry.
>
> ·NVDA 2025.3.3 User Guide
> Mode, Input Gestures, object navigation,
> Punctuation/Pronunciation settings, and the Add-on Store — all
> features discussed throughout the article.
>
> ·N3FJP’s ARRL International DX Contest Log
>
> International DX CW contest referenced in the Day 7 entry.
>
> Categoriesaccessibility
> Amateur Radio
> <https://blindaccessjournal.com/category/amateur-radio/>,
> assistive technology
> <https://blindaccessjournal.com/category/assistive-technology/>,
> JAWS <https://blindaccessjournal.com/category/jaws/>, Nonvisual
> Desktop Access
> <https://blindaccessjournal.com/category/nonvisual-desktop-access/>,
> reviews <https://blindaccessjournal.com/category/reviews/>,
> thought provoker
> <https://blindaccessjournal.com/category/thought-provoker/>,
> Uncategorized
> <https://blindaccessjournal.com/category/uncategorized/>
> David Goldfield,
>
> Blindness Assistive Technology Specialist
>
> Director of Marketing,
>
> Blazie Technologies
>
> Am Yisrael Chai
>
> The Nation of Israel Lives!
>
> <https://www.freedomscientific.com/Training/Certification>
>
> NVDA Certified Expert <https://certification.nvaccess.org/>
> Subscribe to the Tech-VI announcement list to receive blindness
> technology news, events and information.
>
> Email: tech-vi+...@groups.io
> HTH,
>
> Richard, USA,
>
> he only way to make sense out of change is to plunge into it,
> move with it, and join the dance."
>
> -- Alan Watts (1915-1973)
>
> --
> ***
> 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
> https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/045e01dca393%24ee31e6c0%24ca95b440%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
> <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
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/126f01dca5ae%24b5b0aee0%2421120ca0%24%40comproom.co.uk?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
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/003901dca5b2%242d820650%240b01a8c0%40AndyPC?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
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/1dc31acb-161a-4575-8848-12528a74c33e%40seznam.cz?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
> <https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/024901dca5cb%24fbffc620%24f3ff5260%24%40gmail.com?utm_medium=email&utm_source=footer>.
Steve Nutt
Same as JAWS and Narrator I believe.
--
Computer Room Services
77 Exeter Close, Stevenage, Hertfordshire, SG1 4PW
To view this discussion visit https://groups.google.com/a/nvaccess.org/d/msgid/nvda-users/020501dca5b3%24c680c890%24538259b0%24%40sasktel.net.