ISSUE-64: Most text within an element with 'application' role is explanatory, use @labelledby and @describedby to say how

text in application

State:: CLOSED
Product:: ARIA 1.0 Authoring Practices
Raised by:: Aaron Leventhal
Opened on:: 2008-07-14
Description:: Original comment (quote from for example http://lists.w3.org/Archives/Member/w3c-wai-pf/2008JulSep/0007.html ):

describedby
Examples would be helpful.
It's often the case that a description applies to an entire
group, such as fieldset.
In role="application" or role="dialog" all static text content
that is not a label, and isn't in a separate document, is
probably a description and thus should be associated with a
widget or group of widgets.

in the 7 July 2008 ARIA working session, we resolved to bring this comment to the Best Practices Guide

http://www.w3.org/2008/07/07-pf-minutes.html#item07

The point is that most text in applications has a function of explaining the application and/or the constituent widgets in it. Authors will overlook this explanatory functionality unless we push them by means of the BPG
Related Actions Items:: No related actions
Related emails:: No related emails

Cynthia Shelly to look at this with action item for providing text to indicate that an application must also provide an focused object.

Richard Schwerdtfeger, 4 Sep 2008, 18:49:02

Close issue 64 per action 361 - February 6, 2009 aria caucus meeting

Richard Schwerdtfeger, 6 Feb 2009, 17:10:01