Re: NVDA say all command not working.
toggle quoted messageShow quoted text
Is your client using any NVDA add-ons at the moment? If yes, it might be possible that a recent add-on update may have contributed to this problem. If it turns out add-ons might be to blame, have your client follow Gene’s advice of restarting NVDA with add-ons disabled and see if that makes a difference.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Eric Hofman
Sent: Wednesday, January 9, 2019 6:12 PM
Subject: Re: [nvda] NVDA say all command not working.
Thank you so much the warm welcome and for taking the time to assist with this issue.
I confirmed they are using a desktop keyboard and believe that their NVDA config is set to desktop keyboard but I will contact and confirm this and relay your message.
Thank you again for your time and assistance with this issue.
First, welcome to NVDA users list.
If you don’t mind, can you pass on the following message to your client please:
This is Joseph Lee, one of the developers of NVDA screen reader.
I heard from a person you work with that say all command (NVDA+down arrow) isn’t working for you all the way. This might be caused by one or more of the following:
Hope this helps.
I have a client who is using the latest version of NVDA on a Windows 10 Laptop with Office 2016.
The client is reasonably proficient with using NVDA and reports that when attempting to use the “SAY ALL” ( INSERT+DOWN ARROW ) in word, Outlook, notepad various other programs, that the command fails to read to the end of the Page or Document from the currently focused point. The client states it will usually read to the end of the line, sentence, or paragraph and that repeating the command will prompt NVDA to continue reading but again not to the end as expected.
This issue is reported to me as having been occurring for approximately 4 to 6 weeks, So has survived several system reboots. I have ensured via phone that the client is using the latest version and currently there are no updates available for the client.
I have been unable to reproduce this issue on a test system or my work system with the latest version or the previous versions of NVDA. Reset to factory defaults would be the next obvious step but I would like to know if this is a known issue or if there is some way of resolving this without a reset to defaults.
Any advice or assistance is greatly appreciated.