Edit comment LC-654 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1308 Next: LC-791

Comment LC-654: Comment Shortname:; Commenter: Johannes Koch <koch@w3development.de> on behalf of Evaluation tool developer; 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:
Part of Item: Common Failures
Comment Type: TE
Comment (including rationale for proposed change):

While there are two HTML techniques about labeling form controls--\"H44 (Using label elements to associate text labels with form controls)\" and \"H65 (Using the title attribute to identify form controls when the label element cannot be used)\"--there is no common failure about _not_ labeling form controls. This also applies to 4.1.2.

Proposed Change:

Add a common failure about not labeling form controls.; Related issues: 587
(space separated ids); WG Notes: [TEAMC] DONE change test procedure in H44 to: For all input elements of type text, file or password, for all textareas and for all select elements in the Web unit: 1. check that there is a label element that identifies the purpose of the control before the input element; 2. check that the for attribute of the label element matches the id of the input element. For all input elements of type checkbox or radio in the Web unit: 1. check that there is a label element that identifies the purpose of the control after the input element; 2. check that the for attribute of the label element matches the id of the input element. Discussed in the 20 July 2006 telecon: Resolution: Accept proposal for LC-654 as ammended to reference SC 1.3.1. http://www.w3.org/2006/07/20-wai-wcag-minutes.html DONE (28 July 2006) add "Failure of SC 1.3.1 and 4.1.2 due to omitting labels for form controls for item selection or text input" Proposed technique is available at http://lists.w3.org/Archives/Public/public-wcag-teamc/2006Jul/0018.html <previous resolution> Thank you for pointing out the missing failure. We will add a "Failure of SC 1.3.1 due to omitting labels for form controls for item selection or text input". </previous resolution> Discussed in the 29 March 2007 telecon: Loretta to write advisory technique for 1.3.1 and 2.4.5 that reads:"provide labels for all user interface controls except xxx", and write response to 654 that says:"names required in 4.1.2 and labels are recommended in 1.3.1 and 2.4.5" http://www.w3.org/WAI/GL/2007/03/29-wai-wcag-minutes.html Discussed in the 05 April 2007 telecon: resolution: accept proposals LC-587 and LC-654 on labels and forms as amended http://www.w3.org/WAI/GL/2007/04/05-wai-wcag-minutes.html {partial accept} DONE Change failure of HTM 1.3.1 from: Failure of 1.3.1 and 4.1.2 due to omitting labels for form controls for item selection or text input to: DONE Failure of 1.3.1 and 1.4.2 due to the association of label and user interface controls not being programmatically determinable DONE Add draft failure (F68): http://trace.wisc.edu/wcag_wiki/index.php?title=Failure_of_1.3.1_and_1.4.2_due_to_the_association_of_label_and_user_interface_controls_not_being_programmatically_determinable DONE Advisory technique to SC 1.3.1, 4.1.2: Providing labels for all form controls that do not have implicit labels DONE Change "Providing labels for text input or item selection form controls" to "Providing labels for all form controls that do not have implicit labels" in advisory techniques for SC 1.3.1, 4.1.2 Internal WD updated 06 April 2007; Resolution: SC 4.1.2 and SC 1.1.1 require that form controls have names. The name may be provided in a way that is not a (visible) label. SC 1.3.1 requires that if a form control has a label, then the association between the label and the form control can be programmatically determined. To encourage the use of labels when appropriate, we have added an advisory technique to SC 1.3.1 and SC 4.1.2: Providing labels for all form controls that do not have implicit labels (future link); (Please make sure the resolution is adapted for public consumption)