E-mail List Archives
Re: WCAG Violation for use of tabindex=0 on static elements.
From: Sailesh Panchang
Date: Mar 17, 2016 7:21AM
- Next message: Birkir R. Gunnarsson: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message: Chaals McCathie Nevile: "Re: excess accesskeysWCAG Violation for use of tabindex=0 on static elements."
- Next message in Thread: Birkir R. Gunnarsson: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message in Thread: Chaals McCathie Nevile: "Re: excess accesskeysWCAG Violation for use of tabindex=0 on static elements."
- View all messages in this Thread
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
>
>
- Next message: Birkir R. Gunnarsson: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message: Chaals McCathie Nevile: "Re: excess accesskeysWCAG Violation for use of tabindex=0 on static elements."
- Next message in Thread: Birkir R. Gunnarsson: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message in Thread: Chaals McCathie Nevile: "Re: excess accesskeysWCAG Violation for use of tabindex=0 on static elements."
- View all messages in this Thread