Edit comment LC-2785 for Accessibility Guidelines Working Group

Previous: LC-2784 Next: LC-2811

Comment LC-2785: Comment Shortname:; Commenter: Jonathan Avila <jon.avila@ssbbartgroup.com> on behalf of SSB BART Group; 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:
*Labels or Instructions*:
Understanding SC 3.3.2

[begin add]

*Note: *If labels are provided, the label relationship to the object
labeled must be programmatically determined or described in text per
*Understanding
Success Criterion 1.3.1 Info and
Relationships<http://www.w3.org/WAI/GL/2013/WD-UNDERSTANDING-WCAG20-20130711/complete-diff.html#content-structure-separation-programmatic>
*.

[end add]

Comment: This addition implies that the label must be programmatically
associated when a label is used. It is possible that a visual label might
be present in addition to a title attribute or use of aria-label thus
removing the need for an explicitly associated label. The problematic text
“the label relationship to the object labeled must be programmatically
determined” should be changed to say “a label with the same text must be
programmatically determinable”.; Related issues: (space separated ids); WG Notes: [DONE] Note on http://www.w3.org/WAI/GL/2013/WD-UNDERSTANDING-WCAG20-20130711/minimize-error-cues.html Change to text provided below.; Resolution: Thank you for the comment. We recognize the issue you are referring to and will modify the note as follows: Change to: When labels are provided for input objects, the input object's relationship to the label (or to redundant text serving as the label) must be programmatically determinable or available in text per Understanding SC 1.3.1; (Please make sure the resolution is adapted for public consumption)