Re: Questions and suggestions
For years, the only way blind people could get to the system tray was with the screen-reader dialog. It became so well entrenched and so expected a way to reach it that it should be included in screen-readers. Whether it is duplicative or not, at times in this and other contexts, technology related or not, a practice is so well entrenched that it may be desirable to continue it whether it is duplicative or not.
Sighted people have constant and unnecessary instructions on how to do things. How many obvious buttons on machines, for example, have something completely unnecessary written as a prompt such as push. What else are you going to do with a button on a machine? Why is there so much opposition to, not as a general practice, but in this one instance, making things a gbit easier for a lot of NVDA users while doing no harm?
And at very rare times, I have found it necessary to have the dialog available. As I said yesterday, I've seen very rare instances where you can't work with an icon except in the screen-reader provided system tray dialog.
Furthermore, to work with the Windows implementation, you need to know commands most blind computer users don't know. Enter equals left double click in the system tray. Space bar equals left single click. The context menu key equals right click. Since even a lot of experienced computer users don't know such commands implementing a system tray dialog will eliminate frustration and problems that will occur without knowing them. And, unless this has been changed, these commands are not covered in the NVDA users' guide. And how many people read manuals with any thoroughness? And finally, when using the system tray directly, you don't up and down arrow through icons. You right or left arrow. The commands I've given and the difference in movement commands can easily be explained. But most users are not on lists such as this, probably don't read the user Guide with the kind of thoroughness that would allow them to discover such commands and, as I said, unless this has changed, these things aren't discussed in the users Guide. The Windows command is given at some point, but I don't think any of what I have discussed other than that is provided.
----- Original Message -----
From: Travis Siegel
Sent: Friday, February 24, 2017 9:35 PM
Subject: Re: [nvda] Questions and suggestions
This argument is silly.
The windows-b key gives you access, what's the issue? Windows-b works regardless of screen reader, windows version, or desktop/laptop keyboard layout. I see no problem here, and arguing that other screen readers provide another keystroke for the same function is a spurious argument. Other windows screen readers aren't open source either, but I don't see anyone pushing to have this fixed. Other windows screen readers also tend to be larger, and take up more system resources (on average) but I don't see anyone complaining about this either. Just because other screen readers have something doesn't automatically make it something NVDA *must* have. Windows provides the keystroke windows-b for a reason, and there's no reason to duplicate the effort by building access to the same function just because you can.
Good lord, if folks wanted every single windows function duplicated, just
imagine how much bloat screen readers would have. Nothing wrong with
leaving windows keystrokes alone, and just pointing them out when someone
asks. No need to needlessly duplicate existing functionality. Should
NVDA provide another keystroke to switch between programs when alt-tab does the
job just fine?
Give it a rest already.
On 2/24/2017 5:34 PM, Kwork wrote: