W3C home > Mailing lists > Public > public-pfwg@w3.org > October 2014

ACTION-1346: Propose edit to dialog role to clarify issue that leads to bad implementation

From: Matthew King <mattking@us.ibm.com>
Date: Mon, 6 Oct 2014 11:31:35 -0700
To: WAI Protocols & Formats <public-pfwg@w3.org>
Message-ID: <OFFB460815.19241E04-ON88257D69.0061F835-88257D69.0065C5CB@us.ibm.com>
Proposed ARIA 1.1 text:

--------------------------------------------------
dialog (role)

A dialog is a child window of the primary window of a web application. For 
HTML pages, the primary application window is the entire web document, 
i.e., the body element.

Dialogs are most often used to prompt the user to enter or respond to 
information. A dialog that is designed to interrupt workflow is usually 
modal (see related alertdialog).

Authors SHOULD provide a dialog label, which can be done with the 
aria-label or aria-labelledby attribute.

Authors SHOULD ensure that each active dialog has a focusable descendant 
element with focus and that focus is trapped inside the dialog. If the 
dialog is modeless, authors SHOULD ensure there is a keyboard mechanism 
for moving focus between the modeless dialog and other application 
windows.

Note: In the description of this role, the term "application" does not 
refer to the application role, which specifies specific assistive 
technology behaviors.
--------------------------------------------------

In addition, add the following note to the window role:

Note: In the description of this role, the term "application" does not 
refer to the application role, which specifies specific assistive 
technology behaviors.

For your reference: the ARIA 1.0 text is:

--------------------------------------------------
dialog (role)

A dialog is an application window that is designed to interrupt the 
current processing of an application in order to prompt the user to enter 
information or require a response. See related alertdialog.

Authors SHOULD provide a dialog label. Labels may be provided with the 
aria-label or aria-labelledby attribute if other mechanisms are not 
available. Authors SHOULD ensure each active dialog has a focused 
descendant element that has keyboard focus.
--------------------------------------------------

Matt King
IBM Senior Technical Staff Member
I/T Chief Accessibility Strategist
IBM BT/CIO - Global Workforce and Web Process Enablement 
Phone: (503) 578-2329, Tie line: 731-7398
mattking@us.ibm.com
Received on Monday, 6 October 2014 18:33:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:09 UTC