Reported by mdcurran on 2014-06-26 11:15
A. If you turn on numlock while in input help mode, it is impossible to exit input help mode unless you turn off numlock first. Obviously this makes sense to the advanced user, but for a beginner user, they would be under the assumption that while in input help mode they can press any key or key combinations they like, and still be able to then press NVDA+1 to exit input help mode. But if they happen to tap numlock, this will not be true.
B. Pressing numlock while in input help mode, NVDA only announces "numlock" but not its new state (on or off). Again this leads to the confusion about what the key press actually did.
C. The Windows internal key state seems to get confused if you perform the following actions:
In short, following those steps shows that NVDA is badly screwing up Windows' idea of numlock toggling.
The problem is even worse if you're using Mouse keys. It is impossible to turn off numlock at all while in input help once it is on.
I think the best one would be to simply block numlock from passing to the Operating System while in input help if at all possible. It is possible to assign scripts to keys requiring numlock, so I can see the argument that you may want numlock to work. But based on the above rather serious issues, I think it best that we don't worry about that usecase. Or at least remember that you can turn on numlock first and then turn on input help with extended insert if you really must do that.
Some other options:
Allowing the user to press esape to exit input help. This would give them a fail safe way as numlock would not affect this.
Ensuring that NVDA announces the numlock state when it changes while in input help mode. This will make it more clearer. But as shown above, the state is getting mucked up some how anyway.
The text was updated successfully, but these errors were encountered:
Comment 1 by jteh on 2014-06-26 11:20
Unless there's a specific exception (and I don't think there is), I'm pretty sure we already do block numlock from getting to the OS in input help, as we block everything else. I suspect the keyboard driver (or maybe even the keyboard controller) actually handles numlock specially somehow.
Comment 2 by nvdakor on 2014-06-26 11:21
What about treating numlock and scoll lock the same way as caps lock (with caps lock set as NvDA key): pressing once would announce what the key is, pressing twice quickly would toggle the locks?
Comment 3 by mdcurran (in reply to comment 1) on 2014-06-26 11:34
Replying to jteh:
If that is the case I guess the best option then is to ensure we don't block it at all, and make sure we announce the key state. This would solve a bit of confusion, and I guess the key state and light problem. This would provide the same experience as Jaws.
Comment 4 by briang1 on 2014-06-26 15:46
Also while in this strange mode, using control and nump lock says pause, control and scroll lock and pause both say control break.
Its enough to make you go mad. I assume there is logic here, even if we cannot actually see it. Some bits are not masked correctly somewhere.