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

Two related ERRORS from WCAG 2.0 that should be fixed (Notes on 1.3.3 and 1.4.1) #267

Closed
michael-n-cooper opened this issue Apr 4, 2017 · 3 comments
Assignees

Comments

@michael-n-cooper
Copy link
Member

WCAG 2.1 Comment 280 is a WCAG 2.0 comment, so filing this issue here.

@awkawk
Copy link
Member

awkawk commented Apr 5, 2017

The note in 1.3.3 isn't incorrect, but I agree that it is confused by the lack of color in the list of visual properties in SC 1.3.3 and further by the lack of a failure that addresses this.

Perhaps we should create a failure with a "click the red button to proceed to the next step" instruction and a red button with the text "next step"?

The note on 1.4.1 is genuinely confusing.
current:
Note: This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.

I agree that removing this note will reduce confusion, especially if there was a good failure of 1.3.1 that highlighted how color conveys relationships that need to be expressed.

@awkawk
Copy link
Member

awkawk commented May 17, 2017

This would be the fix -
w3c/wcag21#295 (this is in the WCAG 2.1 repo)

@awkawk
Copy link
Member

awkawk commented May 24, 2017

This was addressed and is integrated into the WCAG 2.0 errata: https://www.w3.org/WAI/WCAG20/errata/

@awkawk awkawk closed this as completed May 24, 2017
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

No branches or pull requests

3 participants