WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Maxability Accessibility for all
Date: Mar 22, 2016 6:14AM

I agree with you Kliff.
Hi Joe,

If the focus is moved to the modal container, I was wondering screen reader
may read the content of the entire modal or if it restrict to the content
called by aria-describedby.
The other problem I observe commonly is the screen reader moves to forms
mode when role dialog is used. This means screen reader user should switch
to browse mode and then read the content on the modal.


On Mon, Mar 21, 2016 at 4:58 PM, Joe Chidzik < <EMAIL REMOVED> >
wrote:

> 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
>
> >