WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Voice over focus v/s Keyboard focus

for

From: Tim Harshbarger
Date: Jan 8, 2018 5:25AM

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

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Ajay Sharma
Sent: Sunday, January 7, 2018 11:37 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [WebAIM] Voice over focus v/s Keyboard focus

Hi,

We have a situation on MAC OS X, where default key board focus is not
in sync with VO focus while using VO keys (Ctrl + Opt + Arrow Keys)
for navigation.
For instance, Suppose the current focus is at "button 1", navigating
with VO keys a couple of times will take the user to "Button 3" but
default keyboard focus stays at "Button "1". However, while navigating
with TAB key, focus works fine.

Any help on this would be greatly appreciated.

Best Regards,
Ajay