WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Tabs and focus

for

From: _mallory
Date: Aug 28, 2016 4:46AM

On Thu, Aug 25, 2016 at 04:47:47PM -0400, Birkir R. Gunnarsson wrote:
> But sometimes making the tabpanel element focusable (with
> tabindex="0") would make sense (it would get screen readers out of
> forms mode), and I think when you have 2 or 3 tabs in a tablist, that
> keeping individual tabs focusable is ok as longas the currently
> selected one is indicated with aria-selected="true".

Having the panels focusable also helps those of us using keyboard and
we use arrow keys to scroll down. If we can focus (out of the tabs)
to the panel, our arrow keys are returned to us and we can scroll the
page again. This is super-duper-mega-important for those of us who
don't have ginormous cinema-style screens some developers seem to think
everyone has.

Of course if there's a first item in the panel who is normally focusable
then leave it.

_mallory
>
>
>
> On 8/25/16, 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
> >> > > >>
> >> > >> > >> at
> >> http://webaim.org/discussion/archives
> >> > > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > >