E-mail List Archives
Re: ARIA modal dialogs only read out focusable items (formsand links)
From: Steve Faulkner
Date: Jan 5, 2013 7:47AM
- Next message: Birkir R. Gunnarsson: "Re: testing for color contrast as a totally blind tester"
- Previous message: Bryan Garaventa: "Re: testing for color contrast as a totally blind tester"
- Next message in Thread: Bryan Garaventa: "Re: ARIA modal dialogs only read out focusable items (formsand links)"
- Previous message in Thread: Jared Smith: "Re: ARIA modal dialogs only read out focusable items (formsand links)"
- View all messages in this Thread
Hi all,
if the dialog is like a standard desktop dialog with only form controls use
<div role="dialog">
...
</div>
if it also contains text and other stuff use
<div role="dialog">
...
<div role=document tabindex=0>
...
</div>
</div>
On 4 January 2013 20:03, Jared Smith < <EMAIL REMOVED> > wrote:
> On Fri, Jan 4, 2013 at 12:50 PM, Sailesh Panchang wrote:
>
> > Joseph's email above refers to content that is not focusable but
> > should be available to AT. Aria-hidden will not help there, right?
>
> It will if you do not set use an ARIA role to trigger application mode
> on the dialog. In other words, aria-hidden would hide everything from
> AT except for the dialog box, which could then be navigated as
> standard web content.
>
> A difficulty with this approach is that the dialog must generally be
> in the DOM or markup at the very beginning or very end of the
> document. It cannot be somewhere within the content that has
> aria-hidden applied to it - you can't unhide content within hidden
> content (i.e., aria-hiddenĂșlse doesn't work inside
> aria-hidden=true).
>
> > Also, with reference to Jared's note:
> >>> All content within a modal dialog is to be keyboard focusable, at
> least as far as ARIA is
> >>>concerned.
> > Is this a practical and realistic assumption?
>
> I think this thread is highlighting that it is not always practical.
> It requires hacks and/or ignoring this aspect of the specification.
> Remember, however, that ARIA is intended for *applications*, in which
> it would generally be uncommon for a dialog to contain anything other
> than focusable controls. It is our applying the dialog role to
> non-application dialogs that is causing these issues.
>
> Jared
> > > >
--
with regards
Steve Faulkner
Technical Director - TPG
www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
- Next message: Birkir R. Gunnarsson: "Re: testing for color contrast as a totally blind tester"
- Previous message: Bryan Garaventa: "Re: testing for color contrast as a totally blind tester"
- Next message in Thread: Bryan Garaventa: "Re: ARIA modal dialogs only read out focusable items (formsand links)"
- Previous message in Thread: Jared Smith: "Re: ARIA modal dialogs only read out focusable items (formsand links)"
- View all messages in this Thread