Re: Anyone having issues with NVDA+F6 in Creators Update?
|
Rui Fontes
It can be caused by the browser is not yet ready, so NVDA is not yet in browse mode, and in that case, only F7 is sent to the application, and that command is for activating the mouse mode...
toggle quoted message
Show quoted text
Rui -----Mensagem Original----- De: Gene Data: 29 de abril de 2017 01:05 Para: nvda@nvda.groups.io Assunto: Re: [nvda] Anyone having issues with NVDA+F6 in Creators Update? It sounds as though this may not be an NVDA problem. Are you using the same version of Windows as the student? If so, perhaps a Windows update has caused problems. It's unlikely that the insert key would work intermittently on two different screen-readers unless it actually isn't working properly for some other reason. Gene ----- Original Message -----
From: Brian Vogel Sent: Friday, April 28, 2017 6:00 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Anyone having issues with NVDA+F6 in Creators Update? Actually, this was a typo, but I will admit that I was trying both F6 and F7 along with the NVDA key. I'm back at home now but at least 50% of the time or more if I do NVDA+F7 I get the dialog box about turning Caret Browsing on or off, which I do not ever recall as happening before. I was also getting some very weird misbehavior out of JAWS 18 with regard to its interaction with the use of WinKey and typing to search. I think the latest dot update fixed that, but more testing will be required. |
|
|