Re: Giving the right amount of feedback
I agree with you, and it's not just state transitions.toggle quoted messageShow quoted text
NVDA really doesn't focus on user experience, and it shows. I can count some things off the top of my head.
1. The focus issues. There are threads about this on this list. I seem to remember there being code in NVDA which will drop focus events if too many of them come in.
2. If you have NVDA going through a specific audio device and you switch your default, NVDA will simply stop speaking, or switch to another audio device.
3. NVDA uses a keyboard hook to intercept all keys. Sometimes it gets into a state where it doesn't pass the keys anywhere.
the result of this is your keyboard no longer works, except for win+l and ctrl+alt+delete. If you press ctrl+alt+delete, you might think you can launch task manager.
As soon as you do, you're back on your normal desktop with NVDA still capturing the keyboard.
The only thing you can do is sign out, losing some or all of your work, or figure out how to kill NVDA either with a second account or with a non-keyboard-based solution.
4. NVDA has a review cursor. In consoles and edit fields, if I press NVDA+backspace, NVDA moves my navigator to the focus, where I can use that review cursor to review my text again if I moved it.
This is useful for, say, finding the top of a function in my editor without moving the system cursor.
However, what happens if you do this same thing in browse mode? Your navigator gets moved to the focus, but you then can't move the review cursor around like you could when you first entered the browser. IIRC this is by design.
5. If a program stops responding, NVDA goes with it. Take Event Viewer.
View one event's details with enter. From there, press escape and be prepared to figure out how to get NVDA back, because it's most likely going to stop speaking.
6. We know that in notepad, WordPad, Microsoft Word, and other applications, we can press ctrl+f to find things.
However, in browsers, we need to use ctrl+NVDA+f. Why? Because NVDA doesn't want to override the inaccessible browser find dialog.
I'm sure I'm missing a few things. But IMO, none of this is good user experience.
On Mon, Jul 22, 2019 at 12:49 AM, Perry Simm wrote: