Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify F68 is applicable for controls that use visible labels #40

Closed
wants to merge 2 commits into from

Conversation

takenspc
Copy link
Contributor

@takenspc takenspc commented Aug 9, 2014

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

@awkawk
Copy link
Member

awkawk commented Aug 11, 2014

Thanks for the work - can you please this pull request and the others you submitted be to marge with the Working-Branch-for-Fall-2014 branch? Pull requests need to go to the current working branch.

@awkawk
Copy link
Member

awkawk commented Dec 17, 2014

This was very helpful. We intended to merge your version and make further edits as discussed by the group, but once the changes started rolling it was very difficult to re-connect with your code changes. You can see our changes here: c9e1068

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants