The Web Content Accessibility Guidelines 2.0

WCAG 2.0 Success Criteria

The Web Content Accessibility Guidelines Success Criteria relevant to coding are:

SCDescription

1.1.1

Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A)

  • Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose.
  • Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
  • Tests: If non-text content is a test, exercise or game that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
  • Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
  • Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.

1.3.1

Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)

1.4.4

Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)

1.4.5

Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA)

  • Customizable: The image of text can be visually customized to the user’s requirements;
  • Essential: A particular presentation of text is essential to the information being conveyed.

Note: Logotypes (text that is part of a logo or brand name) are considered essential.

2.1.1

Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints. (Level A)

Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.

Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

2.1.2

No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)

Note: Since any content that does not meet this success criterion can interfere with a user’s ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

2.2.1

Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A)

  • Turn off: The user is allowed to turn off the time limit before encountering it; or
  • Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
  • Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, “press the space bar”), and the user is allowed to extend the time limit at least ten times; or
  • Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
  • Essential Exception: The time limit is essentialand extending it would invalidate the activity; or
  • 20 Hour Exception: The time limit is longer than 20 hours.

Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

2.2.2

Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)

  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

Note: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

Note: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

2.3.1

Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)

Note: Since any content that does not meet this success criterion can interfere with a user’s ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion.

2.4.3

Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A)

2.4.5

Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA)

2.4.7

Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)

3.1.1

Language of Page: The default human language of each Web page can be programmatically determined. (Level A)

3.2.4

Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)

4.1.1

4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A)

Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

The relevant guidelines are detailed in the website manager factsheet.

WCAG 2.0 Sufficient Techniques

For each of the guidelines and success criteria in WCAG 2.0 there are a wide variety of techniques. The techniques fall into two categories:

Sufficient techniques — techniques or a combination of techniques that are sufficient for meeting the success criteria.

Advisory techniques — techniques that should be considered (where relevant) to make content more accessible. The advisory techniques go beyond what is required by the individual success criteria and are not covered by these factsheets.

SCDescription

1.1.1

Situation A: If a short description can serve the same purpose and present the same information as the non-text content (e.g., a progress meter): Situation B: If a short description can not serve the same purpose and present the same information as the non-text content (e.g., a chart or diagram): Situation C: If non-text content is a control or accepts user input: Situation D: If non-text content is time-based media, a test or exercise that would be invalid if presented in text, or primarily intended to create a specific sensory experience:

1.3.1

Situation A: The technology provides semantic structure to make information and relationships conveyed through presentation programmatically determinable: Situation B: The technology in use does NOT provide the semantic structure to make the information and relationships conveyed through presentation programmatically determinable:

1.4.4

1.4.5

2.1.1

2.1.2

2.2.1

Situation A: If there are session time limits:

Situation B: If a time limit is controlled by a script on the page:

Situation C: If there are time limits on reading:

2.2.2

2.3.1

2.4.3

2.4.5

Using two or more of the following techniques:

2.4.7

3.1.1

  • H57: Using language attributes on the html element (HTML)

3.2.4

4.1.1

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

WCAG 2.0 Common Failures

SC 1.1.1 Non-text Content

The following are common mistakes that are considered failures of Success Criterion 1.1.1 by the WCAG Working Group.

FailureDescription

F30

Failure of Success Criterion 1.1.1 due to using text alternatives that are not alternatives

F20

Failure of Success Criterion 1.1.1 due to not updating text alternatives when changes to non-text content occur

F67

Failure of Success Criterion 1.1.1 due to providing long descriptions for non-text content that does not serve the same purpose or does not present the same information

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 1.3.1 Info and Relationships

The following are common mistakes that are considered failures of Success Criterion 1.3.1 by the WCAG Working Group.

FailureDescription

F2

Failure of Success Criterion 1.3.1 due to using changes in text presentation to convey information without using the appropriate markup or text

F17

Failure of Success Criterion 1.3.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML

F42

Failure of Success Criteria 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable

F43

Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content

F68

Failure of Success Criteria 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 1.4.4 Resize text

(http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html)

The following are common mistakes that are considered failures of Success Criterion 1.4.4 by the WCAG Working Group.

FailureDescription

F69

Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured

F80

Failure of Success Criterion 1.4.4 when text-based form controls do not resize when visually rendered text is resized up to 200%

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 1.4.5 Images of Text

There are no common failures currently documented in WCAG2.0.

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.1.1 Keyboard

The following are common mistakes that are considered failures of Success Criterion 2.1.1 by the WCAG Working Group.

FailureDescription

F54

Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function

F55

Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received

F42

Failure of Success Criterion 1.3.1 and 2.1.1 due to using scripting events to emulate links in a way that is not programmatically determinable

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.1.2 No Keyboard Trap

The following are common mistakes that are considered failures of Success Criterion 2.1.2 by the WCAG Working Group.

FailureDescription

F10

Failure of Success Criterion 2.1.2 and Conformance Requirement 5 due to combining multiple content formats in a way that traps users inside one format type

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.2.1 Timing Adjustable

The following are common mistakes that are considered failures of Success Criterion 2.2.1 by the WCAG Working Group.

FailureDescription

F40

Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit

F41

Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh with a time-out

F58

Failure of Success Criterion 2.2.1 due to using server-side techniques to automatically redirect pages after a time-out

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.2.2 Pause, Stop, Hide

The following are common mistakes that are considered failures of Success Criterion 2.2.2 by the WCAG Working Group.

FailureDescription

F16

Failure of Success Criterion 2.2.2 due to including scrolling content where movement is not essential to the activity without also including a mechanism to pause and restart the content

F47

Failure of Success Criterion 2.2.2 due to using the blink element

F4

Failure of Success Criterion 2.2.2 due to using text-decoration:blink without a mechanism to stop it in less than five seconds

F50

Failure of Success Criterion 2.2.2 due to a script that causes a blink effect without a mechanism to stop the blinking at 5 seconds or less

F7

Failure of Success Criterion 2.2.2 due to an object or applet, such as Java or Flash, that has blinking content without a mechanism to pause the content that blinks for more than five seconds

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.3.1 Three Flashes or Below Threshold

There are no common failures currently documented in WCAG2.0.

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.4.3 Focus Order

The following are common mistakes that are considered failures of Success Criterion 2.4.3 by the WCAG Working Group.

FailureDescription

F44

Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.4.5 Multiple Ways

There are no common failures currently documented in WCAG2.0.

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 2.4.7 Focus Visible

The following are common mistakes that are considered failures of Success Criterion 2.4.7 by the WCAG Working Group.

FailureDescription

F55

Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received

F78

Failure of Success Criterion 2.4.7 due to styling element outlines and borders in a way that removes or renders non-visible the visual focus indicator

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 3.1.1 Language of Page

There are no common failures currently documented in WCAG2.0.

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 3.2.4 Consistent Identification

The following are common mistakes that are considered failures of Success Criterion 3.2.4 by the WCAG Working Group.

FailureDescription

F31

Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

SC 4.1.1 Parsing

The following are common mistakes that are considered failures of Success Criterion 4.1.1 by the WCAG Working Group.

FailureDescription

F70

Failure of Success Criterion 4.1.1 due to incorrect use of start and end tags or attribute markup

F77

Failure of Success Criterion 4.1.1 due to duplicate values of type ID

F17

Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine one-to-one relationships (e.g., between labels with same id) in HTML

F62

Failure of Success Criterion 1.3.1 and 4.1.1 due to insufficient information in DOM to determine specific relationships in XML

© W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]