Hi Joseph and list

On Friday I was able to re-contact my client to continue troubleshooting this issue. At that time I was able to use team viewer to remote into his system. During this contact and access to his system I was able to;

1 Establish that he is in fact using a laptop keyboard that has a Numpad.

2 NVDA setting show that desktop keyboard layout was selected now altered  to reflect Laptop keyboard.

3 He has no add-ons installed according to the add-on manager in NVDA

4 He is using Windows One core synth with Microsoft David voice.

5 Restarting NVDA with add-ons  disabled does indeed resolve the problem.

6 Resetting to NVDA to factory defaults had no impact in the issue when running NVDA normally

At this point the remote connection with team viewer became very laggy and un-usable and my client had to attend to other matters. So we had to abandon and will continue on Monday or Tuesday at which time I endeavour to verify NVDA and Windows version and build details.

I thanks everyone for their assistance an contribution to this issue thus far offer my thanks and appreciation.

Kind regards

Eric Hofman

Hi Eric,

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.

Cheers,

Joseph

Hi Joseph

Thank you so much the warm welcome and for taking the time to assist with this issue.

• I have confirmed with the client that they were using the “Down arrow key” as opposed to the NUMPAD “down arrow”. Unfortunately I neglected to state this in my original message, please accept my apologies for that oversight.

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.

Kind regards

Eric Hofman

Hello Eric,

First, welcome to NVDA users list.

If you don’t mind, can you pass on the following message to your client please:

Hi,

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:

• Which key you are pressing: many desktop keyboards (and some laptops) come with two arrow keys: the regular arrow keys, and the set as part of the Numpad. I’m thinking that you might be pressing the Numpad down arrow key with NVDA key, which performs a completely different action. Unless otherwise stated, when NvDA people talk about arrow keys, we usually refer to regular arrow keys.
• Keyboard layout: NVDA comes with two keyboard layouts to suit the needs of desktop and laptop keyboard users. I’m thinking that somehow you may have switched to laptop keyboard layout. To confirm this, press Control+NVDA+K, then see what the keyboard layout is (the first combo box from keyboard settings).

Hope this helps.

Cheers,

Joseph

Hi All

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.

Regards

Eric Hofman