WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Voice over focus v/s Keyboard focus

for

From: Jonathan Cohn
Date: Jan 8, 2018 2:12PM

Well, this does depend a little on the version of MacOS. 10.13 better known
as High Sierra removed one of the tracking options available in the
Navigation pane of VoiceOver utility.

In High Sierra there is only the "Synchronize VoiceOver and Keyboard Focus"
in older versions there are two separate check boxes but it is possible
Especially in LinkedIn and a few other sites that open menus or panels
onFocus to get in a loop where the user gets into a focus trap situation.

For these sites, I have encouraged Blind Users to turn off both Mouse
Follows VoiceOver cursor and Keyboard focus follows VoiceOver Cursor.

Let me know if I can be of further help,

Jonathan


On Mon, Jan 8, 2018 at 7:25 AM Tim Harshbarger <
<EMAIL REMOVED> > wrote:

> The reason for this is because the screen reader focus (Voiceover in this
> case) and keyboard focus are not the same thing. If you were to use keys
> like tab or shift+tab that move the keyboard focus to the next or previous
> control in the tab order, the screen reader focus would follow it. The
> reverse is not typically true.
>
> The reason for this is so someone using a screen reader can navigate and
> read all the user interface elements--not just those that can be reached by
> keyboard.
>
> Most screen readers do include a feature that allows the user to move the
> keyboard focus to the screen reader focus. I expect it is not a feature
> used much by those who use screen readers. I know I have rarely had reason
> to use it.
>
> That is also why screen reader testing and keyboard testing should
> normally be 2 different tests--screen reader focus can go places that
> keyboard focus can't. In fact, once in a while it is possible to use a
> screen reader to access and interact with a part of the user interface with
> which a keyboard cannot either interact or reach.
>
> Thanks,
> Tim
>
>