E-mail List Archives
Re: WCAG Violation for use of tabindex=0 on staticelements.
From: Joe Chidzik
Date: Mar 21, 2016 5:28AM
- Next message: Kelly Lupo: "Usability vs. Accessibility"
- Previous message: Jeevan Reddy: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Next message in Thread: Maxability Accessibility for all: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message in Thread: Jeevan Reddy: "Re: WCAG Violation for use of tabindex=0 on static elements."
- View all messages in this Thread
In this case though, the developer should probably use tabindex="-1" which restricts the focus to only being placed onto an element programmatically, rather than the element appearing in the focus order with tabindex="0".
As an aside, I would probably place the focus onto the actual dialog container itself (with role=dialog), rather than the heading, with the title of this container picked up from the dialog heading via aria-describedby or similar.
Joe
>
- Next message: Kelly Lupo: "Usability vs. Accessibility"
- Previous message: Jeevan Reddy: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Next message in Thread: Maxability Accessibility for all: "Re: WCAG Violation for use of tabindex=0 on static elements."
- Previous message in Thread: Jeevan Reddy: "Re: WCAG Violation for use of tabindex=0 on static elements."
- View all messages in this Thread