Web Content Accessibility Guidelines (WCAG) 2.0 Errata

1 Substantive Errata

No substantive errata recorded at present.

2 Editorial Errata

1. In the definition of relative luminance, the red threshold was updated from 0.03928 to 0.04045.
2. Success Criterion 1.1.1 point "Controls, Input" has a reference to Guideline 4.1 for additional requirements for controls and content that accepts user input. It would be more accurate and clear if the note referred to Success Criterion 4.1.2. Success Criterion 4.1.2 requires that user interface components have a name, role, state, property and value. This is closely related to the requirements that SC 1.1.1 places on user interface controls to have a name that describes its purpose.
3. Success Criterion 1.4.3 and Success Criterion 1.4.6 point "Logotypes" states "Text that is part of a logo or brand name has no minimum contrast requirement." The word "minimum", not used in the other points, implies a difference in meaning that is not intended. For clarity and consistency, remove the word "minimum" from this point in both Success Criteria.
4. The definition of idiom includes the Dutch phrase "Hij ging met de kippen op stok". This phrase was incorrectly marked with the language code "ne"; it should have been marked with the language code "nl".
5. The definition of idiom includes the Japanese phrase "さじを投げる". This phrase was incorrectly marked with the language code "jp"; it should have been marked with the language code "ja".
6. In WCAG 2.0 Layers of Guidance the sentence "Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive language and learning areas" lacked commas to clarify that cognitive, language, and learning were separate areas. It should read "Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability, particularly in the cognitive, language, and learning areas".
7. In the definition for video-only the cross reference for audio linked to the definition for video instead of the proper link to audio.
8. In Success Criterion 3.2.1 the word "component" should be replaced by the term "user interface component" and linked to the definition of that term, to clarify that this is meant to be consistent with other success criteria that use that term.
9. The definition for the term "user interface component" should have the following note to clarify its meaning: "Note: What is meant by 'component' or 'user interface component' here is also sometimes called 'user interface element'."
10. Success Criterion 3.2.4 referred to a "set of Web pages" and linked the part "Web pages" to the definition for that term. Instead the entire phrase should have been linked to the separate definition for "set of Web pages".
11. The definition for the term "live" should use the word "cue" instead of "queue" because it refers to the process of cuing media.
12. Success Criteria 1.3.3 and 1.4.1 each refer to color and the language of the notes confuses the Working Group’s intent. Removing the notes for both and adding color to the list of sensory characteristics in 1.3.3 clarifies the success criteria and preserves the original intent.

13. The following notes were added to 4.1.1 Parsing:

    Success Criterion 4.1.1 was originally adopted to address problems that assistive technology had directly parsing HTML. Since this criterion was written, the HTML Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs.

    Although the HTML Standard treats some of these cases as non-conforming for authors, it is considered to "allow these features" for the purposes of this Success Criterion because the specification requires that user agents support handling these cases consistently. In practice, this criterion no longer provides any benefit to people with disabilities in itself.

    Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different Success Criteria and should be reported under those criteria rather than as issues with 4.1.1.

    This criterion should be considered as always satisfied for any content using HTML or XML.