regrets Alan_Smith

<scribe> scribe: jamesn

<adam_solomon> im gone for 5 minutes

<marcjohlic> http://www.w3.org/WAI/GL/wiki/Using_aria-describedby_to_provide_descriptions_of_objects

<adam_solomon> back

Do we merge ARIA1 & http://www.w3.org/WAI/GL/wiki/Using_aria-describedby_to_provide_descriptions_of_objects

http://www.w3.org/WAI/GL/wiki/Using_aria-describedby_for_link_purpose

<Loretta> http://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks_to_identify_regions_of_a_page

ARIA1 Actions - drop example 2, move examples 2,3 & 4 if applicable from http://www.w3.org/WAI/GL/wiki/Using_aria-describedby_to_provide_descriptions_of_objects to ARIA1

leave http://www.w3.org/WAI/GL/wiki/Using_aria-describedby_to_provide_descriptions_of_objects as one dealing with "long descriptions" of images

change title to "ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls"

<marcjohlic> http://www.w3.org/WAI/GL/wiki/ARIA1:_Using_the_aria-describedby_property_to_provide_a_descriptive_label_for_user_interface_controls

drop 2.4.4 from the applicability

<p> <span class="left" id="fontDesc" >Select the font faces and sizes to be used on this page</span>

<span class="right"><button id="fontB" onclick="doAction('Fonts');" aria-describedby="fontDesc">

Fonts </button></span></p>

<live editing ARIA-1>

Resolutions: move aria1 to be reviewed by WCAG

accept changes to aria3 and move to wcag review

<marcjohlic> "Access a page that contains mandatory form field(s) using the aria-required property "

Note 2: At this time, WAI-ARIA is a Working Draft. This technique is provided as an advisory technique for organizations that wish to experiment with achieving WCAG conformance using WAI-ARIA. When WAI-ARIA becomes a formal specification and is supported in user agents, it is anticipated that this technique will become a sufficient technique.

Note 1: The fact that the element is required is often visually presented (such as a sign or symbol after the control). Using the aria-required property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner. Refer to Supporting ARIA in XHTML and HTML 4.01 for information on how to provide WAI-ARIA States and Properties with XHTML and HTML. WAI-ARI

A States and Properties is compatible with other languages as well; refer to documentation in those languages.

Note 1: The fact that the element is required is often visually presented (such as a sign or symbol after the control). Using the aria-required property in addition to the visual presentation makes it much easier for user agents to pass on this important information to the user in a user agent-specific manner.

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: jamesn
Inferring ScribeNick: jamesn

WARNING: No "Topic:" lines found.

Default Present: Paul_Adam, James_Nurthen, Loretta, Marc_Johlic, Adam_Solomon
Present: Paul_Adam James_Nurthen Loretta Marc_Johlic Adam_Solomon
Got date from IRC log name: 26 Sep 2013
Guessing minutes URL: http://www.w3.org/2013/09/26-html-techs-tf-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report