WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG Violation for use of tabindex=0 on static elements.

for

From: Birkir R. Gunnarsson
Date: Mar 17, 2016 7:49AM

off-otpic
Coincidence?
I doubt it.
I have had the privellege to work with and receive training from some
pretty awesome accessibility people.

Sailesh is one of the Deque folks who taught me the most about accessibility.
So did many people ouside of Deque such as Bryan Garaventa, Denis
Boudreau, the WebAIM folks, and a lot of people on this list (if I
started naming all the names it would end up being a long email and
awfully off-topic).
But I must take a moment to say thank you to everyone on this list who
help me, from the moment I first heard about web accessibility 7 or 8
years ago, to where I am today.
And big thanks to Jared and the WebAIM folks who have kept this list
going for almost a decade.

I hope to help pass the knowledge on to others so we can all help make
the web an equal opportunity universe.
end-of-off-topic.
Cheers
-B



On 3/17/16, Sailesh Panchang < <EMAIL REMOVED> > wrote:
> Birkir beat me to it and in fact took the words out of my mouth!
> It is a fail under all the 3 SCs he listed.
> Thanks,
> Sailesh
>
>
>
>
> On 3/16/16, Jonathan Avila < <EMAIL REMOVED> > wrote:
>>> Adding tabindex=0 makes it a User Interface Component so 4.1.2 now
>>> applies
>>> to these traditionally non-widget components
>>
>> This brings up a question I have always wondered -- what role can you
>> apply
>> to text? None? Presentation? There are some rare situations where you
>> may
>> want to place text in the focus order and if you do -- what role would you
>> be required to use in order for it to meet SC 4.1.2?
>>
>> Jonathan
>>
>>