Edit comment LC-2954 for Accessibility Guidelines Working Group

Previous: LC-2953 Next: LC-2963

Comment LC-2954: Comment Shortname:; Commenter:; 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:
https://github.com/w3c/wcag/pull/40

F68 is applicable for controls that use visible labels.

Applicability

HTML and XHTML controls that use visible labels
F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determined
http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140724/F68.html

Thus we should remove unrelated example, related techniques and check conditions.

Example 3 is the same example of H65 which is a technique for controls that cannot use visible labels. So this pull request removed Example 3.

H65: Using the title attribute to identify form controls when the label element cannot be used
http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140724/H65.html

The aria-label and title are techniques for controls that cannot use visible labels. Thus this pull request removed related techniques and check conditions. As the aria-labelledby can be used for controls that use visible labels such as controls in the data table, this pull request doesn't modify that.

Additional changes are

Updated first sentence of test procedures to match notes of description (applicable input type is not limited to radio, checkbox, text, file or password)
Replaced "input element" to "control element" in test procedure to match "For all input elements ... and all textarea and select elements"
Make sure that ids in aria-labelledby are ids of the text label element instead of the control control; Related issues: (space separated ids); WG Notes: seemingly (not sure) 1.3.1 does in fact only apply to visible labels and commenter is correct that use of title or aria-label would not suffice, as opposed to 4.1.2 where they would suffice. Maybe that's why aria-label technique doesn't appear in the sufficient techniques for 1.3.1 We should then have separate failures for 4.1.2 and 1.3.1, the current failure being slightly rewritten for 4.1.2 and a new failure excluding use of title and aria-label for 1.3.1; Resolution: Thank you for your comment. As F68 does in fact apply to criterion 1.3.1 which would apply only to situations where a visible label is present, example 3 should be removed. Also, the presence of title and aria-label should not appear in the test procedure, and the specific mention of input in the test procedure should be amended as per your request. The test procedure would then read: 'For all control elements (input elements of type "radio", "checkbox", "text", "file" or "password", and all textarea and select elements) in the Web page: Check that the visual design uses a text label that identifies the purpose of the control Check that the control element has a programmatically determined label associated in one of the following ways: the text label is contained in a label element that is correctly associated to the respective control element via the label's for attribute (the id given as value in the for attribute matches the id of the input element). the control is contained within a label element that contains the text label. the text label is correctly programmatically associated with the control element via the aria-labelledby attribute (the id given as value in the aria-labelledby attribute matches the id of the element containing the text label)." Furthermore, we may add an additional failure which would apply only to 4.1.2, and would include "title" and "aria-label" in the test procedure, since they are sufficient for 4.1.2; (Please make sure the resolution is adapted for public consumption)