WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Tabs and focus

for

From: Paul J. Adam
Date: Aug 25, 2016 4:12PM

That's expected behavior for NVDA. VoiceOver and TalkBack don't have that issue with tabs or dialogs.

Yes, pressing right/left arrow keys will actually activate the tabs whereas tabbing to the tabs requires to the user to press spacebar to activate.

No I still don't recommend jumping focus after they click the tabs. I usually only recommend focus management for things like modal dialogs, hamburger menus, and maybe form error validation.

Paul J. Adam
Accessibility Evangelist
www.deque.com

> On Aug 25, 2016, at 2:00 PM, Joseph Sherman < <EMAIL REMOVED> > wrote:
>
> Paul J Adam wrote:
>> In my demo that deviates from the authoring practices I have all the tabs
>> available in the tab order or users can activate the arrow keys to move
>> between tabs.
>
> I looked at the demo using NVDA. Once I'm in the Tabs it goes to forms mode and the arrow key selects the next tab. In order to read the tab panel text I have to manually exit forms mode and arrow down. Is this expected behavior for screen reader users? Also note that the Tab key changes the focus but not the tab panel content, while the arrow keys do both.
>
>> I don't recommend jumping their focus down to the tab panel because they may want to activate a different tab or read all the tabs before actually moving focus into it.
>
> I didn't mean to jump focus on tab focus, but whether it makes sense to jump focus to content onclick.
>
> Thanks.
>
> Joseph
>
>>
>>> On Aug 25, 2016, at 11:57 AM, Joseph Sherman
>> < <EMAIL REMOVED> > wrote:
>>>
>>> Question: When using tabs like five items in a horizontal row each with
>> some text content, is it better to jump focus to the content when the user
>> expands or activates the tab or have the user have to go through the other
>> tabs to get to content?
>>>
>>> Also, the specs (https://www.w3.org/TR/wai-aria-practices-1.1/#tabpanel)
>> say that only the active tab should be in the tab order and users should use
>> arrows to move through tabs. Is this another area when the specs are ahead
>> of user expectations?
>>>
>>> Thanks.
>>>
>>> Joseph
>>>
>>> >>> >>> archives at http://webaim.org/discussion/archives
>>> >>
>> >> >> http://webaim.org/discussion/archives <http://webaim.org/discussion/archives>;
>> > > > >