E-mail List Archives
Re: WCAG Violation for use of tabindex=0 on staticelements.
From: Jonathan Avila
Date: Mar 16, 2016 6:30PM
- Next message: Chaals McCathie Nevile: "Re: excess accesskeysWCAG Violation for use of tabindex=0 on static elements."
- Previous message: James Nurthen: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Next message in Thread: Chaals McCathie Nevile: "Re: excess accesskeysWCAG Violation for use of tabindex=0 on static elements."
- Previous message in Thread: James Nurthen: "Re: WCAG Violation for use of tabindex=0 on static elements."
- View all messages in this Thread
> 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: Chaals McCathie Nevile: "Re: excess accesskeysWCAG Violation for use of tabindex=0 on static elements."
- Previous message: James Nurthen: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Next message in Thread: Chaals McCathie Nevile: "Re: excess accesskeysWCAG Violation for use of tabindex=0 on static elements."
- Previous message in Thread: James Nurthen: "Re: WCAG Violation for use of tabindex=0 on static elements."
- View all messages in this Thread