New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pressing numlock while in input help mode may confuse beginner users #4226
Comments
Comment 1 by jteh on 2014-06-26 11:20 |
Comment 2 by nvdakor on 2014-06-26 11:21 |
Comment 3 by mdcurran (in reply to comment 1) on 2014-06-26 11:34 |
Comment 4 by briang1 on 2014-06-26 15:46 |
Comment 5 by jteh on 2014-06-26 23:54
|
Comment 6 by Michael Curran <mick@... on 2014-06-27 05:04
Changes:
|
Comment 7 by Michael Curran <mick@... on 2014-07-11 23:39
Changes:
|
Comment 8 by mdcurran on 2014-07-11 23:39 |
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:
sighted person reports that the numlock light does not come on
says numlock+numpad6
says 6
says numlock on
says 6
says numlock off
announces the next word
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.
Possible solutions:
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:
The text was updated successfully, but these errors were encountered: