E-mail List Archives
Thread: Object Navigation by a screen reader
Number of posts in this thread: 4 (In chronological order)
From: mhysnm1964
Date: Sun, Nov 04 2018 12:03AM
Subject: Object Navigation by a screen reader
No previous message | Next message →
All,
I saw a post here a while ago on a new train of thought for screen readers
to navigate the web page by objects similar to what Voice-Over does. Does
anyone have any information on this that I can read to see how or why this
is the new thinking?
As I have some concerns and want to read up before sharing to ensure I am on
the right thinking.
Sean
From: Patrick H. Lauke
Date: Sun, Nov 04 2018 3:16AM
Subject: Re: Object Navigation by a screen reader
← Previous message | Next message →
On 04/11/2018 06:03, = EMAIL ADDRESS REMOVED = wrote:
> All,
>
>
>
> I saw a post here a while ago on a new train of thought for screen readers
> to navigate the web page by objects similar to what Voice-Over does. Does
> anyone have any information on this that I can read to see how or why this
> is the new thinking?
>
>
>
> As I have some concerns and want to read up before sharing to ensure I am on
> the right thinking.
To clarify: most screenreaders have had different ways to navigate
content (using reading keys, jumping to headings, lists, blocks, etc)
for ages. This is nothing new. The discussion thread here recently was,
if I remember correctly, mostly about breaking the myth that SR users
navigate just using TAB/SHIFT+TAB the same way sighted/non-AT keyboard
users would (and even those users wouldn't exclusively navigate this way
either).
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
From: Jonathan Avila
Date: Sun, Nov 04 2018 2:58PM
Subject: Re: Object Navigation by a screen reader
← Previous message | Next message →
Hi Sean, there was a discussion about this maybe a year or so ago with talk of Edge and slowness of the browse/virtual cursor and talk about the end of these methods of access in browsers generally. I expressed my concern about the virtual/browse cursor going away -- I believe it is a very efficient way of navigating and it provides some things and ease of use that can't be done with object navigation. For example, moving from word, letter, line in one object into another, etc. without having to worry about switching objects. I haven't heard much about this lately so I hope the issues or concerns have been addressed.
Jonathan
From: mhysnm1964
Date: Sun, Nov 04 2018 11:18PM
Subject: Re: Object Navigation by a screen reader
← Previous message | No next message
Jonathan
Thanks for this, I will do a search on WebAim again to see if I can find it.
I do see pro's and con's for it. The windows model doesn't require you to
interact with the object to move down the underlying tree structure. While
Mac you have too. Performance in moving around the screen can be slower as
you can see duplicated information on the windows platform. I do not see
this as Much on the Mac. You still do not get relationship information such
as this object is at the top of the screen left side. This concept can be
done easily enough as the information is in the accessibility tree. It is
helpful in my view for someone who uses a screen reader, but is going to be
for a small group of users.
ChromeVox seemed to have a hybrid between a virtual buffer and object
navigation which again is good and bad.
Cheers
Sean