Edit comment LC-938 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1077 Next: LC-1078

Comment LC-938: Comment Shortname:; Commenter: Andi Snow-Weaver <andisnow@us.ibm.com> on behalf of IBM; 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:
Users who are filling out forms need a mechanism to indicate whether form elements are required. This is addressed in XForms and Dynamic Web Accessibility by indicating if a form field is required or invalid. If the user does not know a field is required form submissions will fail and the user must repeat the process.

Proposed Change:

Add an XHTML technique to How to meet 1.3.1 that demonstrates using Dynamic Web Content Accessibility attribute of required=""true"".

Such a technique could also be useful in meeting GL 2.5 but there is no success criteria to relate it to. It could be an advisory technique under ""Understanding guideline 2.5"" or listed as a related technique under the GL 2.5 success criteria.; Related issues: (space separated ids); WG Notes: [TEAMC] I have drafted a technique about using required="true" - see: http://trace.wisc.edu/wcag_wiki/index.php?title=Using_Dynamic_Web_Content_Accessibility_to_programmatically_identify_form_fields_as_required Open issue: can this also be a technique for GL 2.5? Discussed in the 14 September 2006 telecon: Resolution: accept 938 as ammended. http://www.w3.org/WAI/GL/2006/09/14-wai-wcag-minutes.html DONE incorporate new technique for 1.3.1 in draft: http://trace.wisc.edu/wcag_wiki/index.php?title=Using_Dynamic_Web_Content_Accessibility_to_programmatically_identify_form_fields_as_required Updated Internal WD 25 September 2006. BBC: Updated resolution to match 1013. Response: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0080.html; Resolution: Thank you for the suggestion. We have created an advisory technique for SC 1.3.1 on how to use the Dynamic Web Content Accessibility 'required' attribute to programmatically mark a form field as required. This is an advisory technique until the Dynamic Web Content Accessibility specification reaches recommendation status.; (Please make sure the resolution is adapted for public consumption)