Skip to content

Comments

Merge with upstream#5

Merged
kabel merged 7 commits intounl:masterfrom
mfairchild365:master
Mar 3, 2015
Merged

Merge with upstream#5
kabel merged 7 commits intounl:masterfrom
mfairchild365:master

Conversation

@mfairchild365
Copy link

No description provided.

Luke Wright and others added 7 commits December 15, 2014 08:35
We should no longer be failing Label attributes for not having a "for"
attribute, now that different methods of association are permitted.
- Allow 1.3.1's label association tests to be re-used. It now has a
  "mute errors" parameter and returns whether (and where) it's found its
  associations.
- 4.1.2's label association test (for accessibility API) now re-uses
  this, if a label association is found in any way then it will not
  throw H91.
The test that flags "for" attributes on labels that don't point to a form control is now a warning, not an error. It is not a fail in itself (especially now explicit labels are not necessary), but often suggests a misused or typoed for attribute and thus should be manually checked.

Also no error will appear if the "for" attribute is empty (for="").
Add an isDisabled method (triggering on disabled IDL attribute or aria-disabled="true") and use that to stop disabled elements (and their children) from being tested for contrast.
Conflicts:
	Standards/WCAG2AAA/Sniffs/Principle1/Guideline1_4/1_4_3_Contrast.js
	Standards/WCAG2AAA/Sniffs/Principle4/Guideline4_1/4_1_2.js
kabel added a commit that referenced this pull request Mar 3, 2015
@kabel kabel merged commit 883a855 into unl:master Mar 3, 2015
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