Re: Mouse Navigation with NVDA - Do you use it? Do you like it?
I use many of the NVDA navigation commands when using the review mode. I use the mouse only if the navigation commands will not do the task. With the NVDA review commands and the mouse capabilities, I can access software that I never could with JAWS. Some examples are the Avira screen, the Twitter app in win10, the entire screen of VLC media player, Calender app in win10, and on and on. I could never use these apps with JAWS. Have a great one.
Sent: Wednesday, March 9, 2016 2:02 PM
Subject: Re: [nvda] Mouse Navigation with NVDA - Do you use it? Do you like it?
Yes, you won't see them if you are not taught to work with the web page and rely on artificial structures. I very strongly believe that teaching the Internet well is done by teaching how to work directly with web pages and not with artificial structures such as links lists. Blind people should know that you can tab or use commands provided by screen-readers, to move from link to link. They should also know that you often have to use the arrow keys to see if there is text or other controls between links. It depends on context. But using the mouse is not the answer. Learning to browse effectively as a blind person is the answer to effective web page navigation.
Blind people generally have a lot of problems browsing web pages because they don't know how to use existing methods effectively.
I work with a recording program where the time elapsed in a playing file can be seen using the NVDA screen review commands. Using a mouse may provide the same access, I haven't used the feature you are discussing so I don't know. But that is an example, the content is not accessible by using standard methods such as the arrow keys, to find and read it where other techniques are necessary. I am not convinced that the NVDA screen review commands don't give as good or better access in terms of efficiency to such content in many cases. There are times when moving a physical mouse using the feature you are discussing may provide the ability to do something. But it would be important to hear specific examples from people and to know whether those people know and use the commands provided by NVDA as well.
----- Original Message -----
----- Original Message -----
Believe me, I know that using the mouse without being able to see it is hard. It is, however, within screen readers that support it a very easy way to give a quick listen to what's on the screen that you might never see if you're doing things like listing all links and traversing the list or all headers and traversing that list, etc. I've also found it interesting that on most sites there are hidden links specifically for those using accessibility software that the rest of the world never sees.
I'm not so much interested (though I am interested, don't get me wrong) in whether someone uses the mouse as a pointing and activating device so much as whether they use it to get a sense of what might be on a screen just by running it around.
It's also nice that at least some laptops allow you to configure the mouse such that it will not go outside the physical screen boundary. That's under the "Momentum" settings for my Synaptics touch pad under "Enable bounce off screen edge". While that would drive me crazy, as I often want the mouse to disappear, it would be incredibly useful for someone doing screen review via mouse movement. This may be possible with certain mice on desktop machines, too, but I've never had one with that configuration option in that hardware environment.
It was also interesting for me to see what I consider the weird difference in accessibility in PDF-XChange Viewer when using the conventional menu keyboard shortcuts and arrow key traversal, which gives you no feedback at all, but when you hover over the same menus with the mouse and draw the mouse pointer down the menu, each and every thing, including the menu title, is announced (this is all with NVDA 2016.1). Why that would be is a mystery, since if there were nothing that NVDA could access somehow for announcing things then there should be no accessibility feedback in either method.