Edit comment LC-630 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-573 Next: LC-631

Comment LC-630: Comment Shortname:; Commenter: Lisa Seeman 2 <lisa@ubaccess.com> on behalf of Invited expert at W3C, UB access; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
http://lists.w3.org/Archives/Public/public-comments-wcag20/2006May/0137.html
http://lists.w3.org/Archives/Public/public-comments-wcag20/2006May/att-0137/wcagform_ch2_.html

Comment (including rationale for any proposed change):

2.5.2 If an input error is detected and suggestions for correction are known and can be provided without jeopardizing the security or purpose of the content, the suggestions are provided to the user.

With things like role attribute you can assign a functional role to an element, and other important information such as allowable range. That means that the assistive technology can themselves perform validation.
Makes it all a user agent thing...

Proposed Change:

2.5.2 If an input error is detected and suggestions for correction are known and can be provided without jeopardizing the security or purpose of the content, the suggestions are provided to the user or can be progmaticly determined; Related issues: (space separated ids); WG Notes: [TEAMC] Relates to LC-629 LC-631 LC-632 Proposal to the team C list at http://lists.w3.org/Archives/Public/public-wcag-teamc/2006Jun/0011.html. Discussed at June 5, 2006 Team C meeting. -- Discussed on the 22 June 2006 teleconference Group agrees in principle with the response to not update the SC text. Update response text "suggestions for error correct" with "suggetions for error correction", Leave open and assign to Loretta to work out final language for HTM doc. http://www.w3.org/WAI/GL/2006/06/22-wai-wcag-minutes.html {partial accept} @@ Loretta: clarify in the understanding document that there could be technology specific SC that do this RESPOND WITH: The current success criterion does not prevent use of Dynamic Web Content Accessibility, XForms or other technologies to add information that will allow assistive technologies to provide suggestions for error correction. We do not feel we need to specifically add "programmatically determined" to the success criterion in order to support this additional data. If role and validation information is programmatically provided in the markup and testing demonstrates that suggestions for error correction are provided to the user via the user agent or assistive technology, this success criterion has been satisfied. When assistive technology is available which supports this level of validation and correction, the working group will add an advisory technique for this success criterion. When this is generally supported by all AT then it could be added as a sufficient technique. --- @@See action from 22 June 2006 meeting <http://www.w3.org/WAI/GL/2006/06/22-wai-wcag-minutes.html#item08> 10 Jan 07, LGR: added additional information to How To Meet document. Does this need to go to survey again? Discussed in the 25 January 2007 telecon: accepted by unanimous consent http://www.w3.org/WAI/GL/2007/01/25-wai-wcag-minutes.html {partial accept} DONE Add to the intent Section: The content author may provide the description of the error, or the user agent may provide the description of the error based on technology-specific, programmatically determined information. DONE add "pending completion of ARIA" to techniques, add "pending completion of ARIA" to response, and add UA notes Discussed in the 19 April 2007 telecon: resolution: accept as amended http://www.w3.org/WAI/GL/2007/04/19-wai-wcag-minutes.html DONE Add the following advisory techniques to SC 3.3.2: DONE drafts in wiki: Identifying required fields with the "required" property http://tinyurl.com/2ll5bo DONE Identifying valid range information with the "valuemin" and "valuemax" properties http://trace.wisc.edu/wcag_wiki/index.php?title=Identifying_valid_range_information_with_the_%22valuemin%22_and_%22valuemax%22_properties Internal WD updated 20 April 2007; Resolution: The current success criterion does not prevent use of Dynamic Web Content Accessibility, XForms or other technologies to provide information that will allow user agents and assistive technologies to provide suggestions for error correction. We do not feel we need to specifically add "programmatically determined" to the success criterion, but such technology-specific techniques could be added as sufficient as user-agent support for them improves. If role and validation information is programmatically provided in the markup for a technology and testing demonstrates that suggestions for error correction are provided to the user via the user agent or assistive technology, this success criterion has been satisfied. The technology-specific techniques should be provided for such technologies. We have provided some advisory techniques for the use of WAI-ARIA and will promote them and will promote them as they qualify as accessibility supported in some environments.; (Please make sure the resolution is adapted for public consumption)