WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Partial Tabindex Behavior

for

From: David Ashleydale
Date: Jul 21, 2014 10:11AM

Perfectly stated, Whitney.

David

On Monday, July 21, 2014, Whitney Quesenbery < <EMAIL REMOVED> > wrote:

> Would be unfair to say that TabIndex was a bandaid.
>
> And that it can cause as much harm as good.
>
> And that getting back to good design is a better solution -- in this case,
> designing for a logical keyboard sequence.
>
> This seems to me a perfect example of why piling on solutions is such a bad
> strategy.
>
> Much better to go back to first principles and design carefully. Just
> harder to do, because it requires both questioning assumptions and thinking
> hard about users (and devices) and their goals.
>
>
> On Sat, Jul 19, 2014 at 4:26 PM, Patrick H. Lauke < <EMAIL REMOVED>
> <javascript:;>>
> wrote:
>
> > On 19/07/2014 19:51, Birkir R. Gunnarsson wrote:
> >
> >> Whenever you see positive tabindex being used, I would recommend
> >> calling that out as a potential user issue and recommend that it be
> >> avoided at all cost.
> >>
> >
> > Tiny sidenote that, from my very cursory testing in iOS/Safari at least,
> > mobile/tablet browsers ignore tabindex > 0 when you navigate with AT
> and/or
> > keyboard...so if tabindex is used to try and force a certain sensible
> order
> > due to underlying HTML / source order of focusable elements being wrong,
> > then note that on these platforms that won't have the desired effect and
> > the wrong tab cycle will still be there for users.
> >
> > 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
> >
> > > > > > > >
> > > >