Re: Golden Cursor question
|
Steve Nutt
Hi Travis,
I totally agree with you. UIA causes screen readers to interpret more than they used to as well.
For example, NVDA will read the whole details of a file in File Explorer, even if it is not on the screen.
The other one that really gets me is web browsing with a sighted person. Maybe Brian Vogel can comment on this, but I hate it when I’m asking my assistant about something on the web, and my screen reader is focused somewhere else entirely.
Neither JAWS nor NVDA really let the sighted person know where the focus is at any given moment. So screen readers are really interpreters.
NVDA has a great feature in this regard though, where you can turn it on to read the screen layout, but the sighted person still doesn’t always know where it is focused.
All the best
All the best
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Travis Siegel
Sent: 21 February 2019 16:39 To: nvda@nvda.groups.io Subject: Re: [nvda] Golden Cursor question
It's always been my opinion that it's a screen reader's job to read the screen, it's my job to interpret what the screen reader tells me is there. That means, if there's a graphic, the screen reader should tell me it's there, if there's an icon, the screen reader should tell me it's there. The screen reader should read exactly what's there, and nothing else. I can't tell you how many hours of productivity time I've lost from stupid little things like my screen reader telling me something was on the screen, when it wasn't actually there. For example, the voiceover screen reader (and I think NVDA does as well) says volume, regardless of whether the entire word is there or not. You know, sometimes, vol by itself does not mean volume. This is of course a minor example of the screen reader saying something that isn't there, but you get the idea. If the screen says v o l, then the screen reader should say v o l, not volume. I understand that most folks do not agree with me on this, but it irks the hell out of me when screen readers say things that aren't there, especially when trying to find sorted file lists, One time I had magazine issues that were named differently from the publisher, depending on what year it was published. I spent a good 10 minutes once trying to figure out why volume 2 issue 1 was out of order, and it turns out the reason was because the screen reader was reading vol as volume, but the publisher didn't spell out volume, only put the 3 letters vol, which changed the sorting order of that particular issue, since the rest of them had volume actually spelled out. Odd, but there it is. That was 10 minutes that didn't need to be wasted, because if the screen reader had just read what was on the screen, it would have been immediately apparent what the problem was, and it could have been easily corrected. This is the kind of thing I mean when I say I've lost hours of productivity due to stupid little things that the screen reader read that didn't exist. Although I reported it, and it (eventually) got fixed, at one point, when beta testing voiceover on the mac, the screen reader said the dinosaur Stegosaurus as Saint Ego Soars. Again, a case of not reading what's on the screen, and one that should not have even occurred based on pronunciation rules built in to the screen reader, but these are the kinds of things that happen when your screen readers try to interpret things for you. I don't like it, and I think it's a waste of time. It wastes the user's time, and it wastes the developer's time, because they have to put in all the rules that create the speaking rules. Just leave it alone, and let the damned thing read what's present, let me interpret what it all means. On 2/20/2019 7:44 AM, Gene wrote:
|
||
|
|
