E-mail List Archives
Re: WCAG Violation for use of tabindex=0 on staticelements.
From: Jonathan Avila
Date: Mar 17, 2016 8:37AM
- Next message: Guy Hickling: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message: Snahendu Bhattacharya: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Next message in Thread: Guy Hickling: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message in Thread: Snahendu Bhattacharya: "Re: WCAG Violation for use of tabindex=0 on static elements."
- View all messages in this Thread
> Will a screen reader user know that this is a link or provides some other interaction
In regards to interactive content, F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control (https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20160317/F59) already covers this situation. My concern was around those rare situations when text needs to be placed in the focus order and is not interactive. It sounds like the default native semantic structure elements would be sufficient absent role of none.
Jonathan
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
<EMAIL REMOVED>
703.637.8957 (Office)
Visit us online: Website | Twitter | Facebook | Linkedin | Blog
Check out our Digital Accessibility Webinars!
- Next message: Guy Hickling: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message: Snahendu Bhattacharya: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Next message in Thread: Guy Hickling: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message in Thread: Snahendu Bhattacharya: "Re: WCAG Violation for use of tabindex=0 on static elements."
- View all messages in this Thread