WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Info widgets with role="dialog"

for

From: Steve Faulkner
Date: Jan 20, 2015 2:58AM

this article by gez is useful
http://juicystudio.com/article/custom-built_dialogs.php

I suggest in the case of dialogs with lots of text content you nest an
element with role=document , this indicates to the AT that they should
switch to reading mode.


--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>;

On 20 January 2015 at 09:50, Detlev Fischer < <EMAIL REMOVED> >
wrote:

>
> Hi,
>
> I wonder whether there is consensus in the community, especially among
> screen reader users, whether modal pop-ups that contain non-form elements
> such as tab panels, data tables with information etc. should be marked up
> as dialog.
>
> My understanding is that the dialog role pushes screen readers into a
> quasi-forms mode which means that content that is not focusable may not be
> read without the user manually switching back to reader mode.
> This means that a widget that may be predominantly a form (e.g. with
> several text inputs, selects, checkboxes etc.) but ALSO contains some other
> elements (e.g. a text "Assign owner: [current owner]" followed by a link
> "change") may be missed when the widget is traversed in the default mode
> triggered by opening a widget with role=dialog. (Or here, "change" may be
> read but the context is not clear). I understand that the aria-labelledby
> and aria-describedby attributes do not work reliably on links so they
> cannot be used to render non-focusable content in a way that it will be
> read by default.
>
> My three questions are:
>
> 1. When calling up a dialog, will screen reader users generally know /
> expect that they (may) have to switch to a reader mode to reach
> non-focusable content?
> 2. If 1 is answered in the negative, should info-widgets better NOT be
> given role=dialog unless all content can be tied to the element containing
> the dialog role or to focusable elements within the dialog via
> aria-labelledby or aria-describedby (or via accessibly hidden extra link
> text)?
> 3. Is adding tabindex=0 to ensure that usually non-focusable content is
> read a good practice to solve this particular problem?
>
> Best,
> Detlev
> -
> Detlev Fischer
> testkreis c/o feld.wald.wiese
> Thedestr. 2, 22767 Hamburg
>
> Mobil +49 (0)1577 170 73 84
> Tel +49 (0)40 439 10 68-3
> Fax +49 (0)40 439 10 68-5
>
> http://www.testkreis.de
> Beratung, Tests und Schulungen für barrierefreie Websites
> > > >