Re: Interesting but I’m not sure I get how this is different FW: A Set of Eyes Helps You Engage with Your Computer Screen
I’m not sure why this sentence is read before my message begins in the message body. it isn’t part of my message. The sentence is:
A Set of Eyes Helps You Engage with Your Computer Screen
Sent: Thursday, May 06, 2021 12:29 PM
Subject: Re: [TechTalk] Interesting but I’m not sure I get how this is different FW: A Set of Eyes Helps You Engage with Your Computer Screen
I haven’t checked but I expect you can set JAWS to display things as they appear on screen to the extent other screen-readers do. But System Access displays one link per line and NVDA can be set to display one link per line as well.
And I don’t know of any screen-reader that displays things as they appear on web pages in most ways. Any screen-reader I’ve used displays navigation links at the top of the page, then other text, then below that text, a clustr of other links, somewhat like the navigation links on top. This is not how a web page appears to sighted users. To sighted users, navigation links run down the left side of the page. Other text appears more in the middle, then the cluster of links screen-readers show on the bottom appear on the right side of the screen.
I haven’t read the article yet, but my point is that blind people aren’t shown web pages as sighted people see them. If a sighted person says this link is on the right, that means it is in the cluster of links at the bottom of the page. Rather than worry about such descriptions, if I know the name of the link, I use my screen-reader’s find command to find it.
It is useful to know what I’ve described and it is informative to know how a sighted person sees web pages. If I were telling a sighted person where to find a link, such knowledge might be useful in that way.
From: John Holcomb II
Sent: Thursday, May 06, 2021 11:47 AM
Subject: [TechTalk] Interesting but I’m not sure I get how this is different FW: A Set of Eyes Helps You Engage with Your Computer Screen
So I read this and even the story (at least to me) doesn’t give enough info on how this is different than other screen readers.
Like doesn’t NVDA and narrator provide things as they appear on the webpage, where as JAWS doesn’t?
Also, what about the rest of the interactions that appear outside of the browser?
Would different engines behave differently?
From: Mike Calvo