WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Dialog semantics and aria?

for

From: Jesse Hausler
Date: Apr 29, 2014 3:16PM

Thanks everyone for this helpful discussion.

Any thoughts on why the ARIA Authoring practices guide suggests tabindex=0
on the document content area of an alertdialog? If there is nothing to
interact with, why set tabindex to 0?

http://www.w3.org/TR/wai-aria-practices/#alertdialog

It's in the WAI-ARIA Roles, States, and Properties cell.

Thanks again,
Jesse


On Mon, Apr 28, 2014 at 7:42 AM, Bryan Garaventa <
<EMAIL REMOVED> > wrote:

> No worries, I didn't say that role=dialog should never be used, just that
> there are keyboard interaction and feedback differences to be aware of,
> since this often catches screen reader users off guard.
>
> I recommended role=region because it is supposed to provide beginning and
> ending boundary text information feedback for screen reader users, though I
> agree, this currently isn't working for NVDA, which there is an open bug
> about.
>
> Regardless whether you use either method, it's the content that needs to be
> accessible, and the method of rendering that is important here, so when the
> dialog is rendered, the background content should be hidden properly, focus
> should be set appropriately for keyboard users, the content must all be
> accessible in an intuitive manner, the dialog must be closable from the
> keyboard, and focus should return to the triggering element after it closes
> if a triggering element is present.
>
> The rest is just semantics.
>
>