10.2: Document success criteria

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:

• Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to WCAG 2.0 Guideline 4.1 [4] for additional requirements for controls and content that accepts user input.)
• 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 WCAG 2.0 Guideline 1.2 [4] for additional requirements for media.)
• Test: If non-text content is a test or exercise 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.
• CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
• 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.

NOTE 1: CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance is accurate.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.1.1 Non-text content with the words

For pre-recorded audio-only and pre-recorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as such:

• Pre-recorded Audio-only: An alternative for time-based media is provided that presents equivalent information for pre-recorded audio-only content.
• Pre-recorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for pre-recorded video-only content.

NOTE 1: The alternative can be provided directly in the document - or provided in an alternate version that meets the success criterion.

NOTE 2: This success criterion is identical to the WCAG 2.0

For pre-recorded audio-only and pre-recorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as such:

• Pre-recorded Audio-only: An alternative for time-based media is provided that presents equivalent information for pre-recorded audio-only content.
• Pre-recorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for pre-recorded video-only content.

NOTE 1: The alternative can be provided directly in the document - or provided in an alternate version that meets the success criterion.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.1 Audio-only and Video-only (Pre-recorded) with the addition of note 1 above.

An alternative for time-based media or audio description of the pre-recorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

NOTE 1: The WCAG 2.0 definition of "audio description" says that "audio description" is "Also called 'video description' and 'descriptive narration'".

NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.3 Audio Description or Media Alternative (Pre-recorded) with the addition of notes 1 and 2 above.

Captions are provided for all live audio content in synchronized media.

NOTE 1: The WCAG 2.0 definition of "captions" notes that "in some countries, captions are called subtitles". They are also sometimes referred to as "subtitles for the hearing impaired". Per the definition in WCAG 2.0, to meet this success criterion, whether called captions or subtitles, they would have to provide "synchronized visual and / or text alternative for both speech and non-speech audio information needed to understand the media content" where non-speech information includes "sound effects, music, laughter, speaker identification and location".

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.4 Captions (Live) with the addition of note 1 above.

Audio description is provided for all pre-recorded video content in synchronized media.

NOTE 1: The WCAG 2.0 definition of "audio description" says that audio description is "Also called 'video description' and 'descriptive narration'".

NOTE 2: Secondary or alternate audio tracks are commonly used for this purpose.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.2.5 Audio Description (Pre-recorded) (Level AA) with the addition of note 1 above.

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.2 Meaningful Sequence.

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

NOTE 1: For requirements related to colour, refer to WCAG 2.0 Guideline 1.4 [4].

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.3.3 Sensory Characteristics with the words "WCAG 2.0" added before the word "Guideline" in note 1 above.

Colour is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

NOTE 1: This success criterion addresses colour perception specifically. Other forms of perception are covered in WCAG 2.0 Guideline 1.3 [4] including programmatic access to colour and other visual presentation coding.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.1 Use of Color with the words "WCAG 2.0" added before the word "Guideline" in note 1 above.

If any audio in a document plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.

NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, all content in the document (whether or not it is used to meet other success criteria) shall meet this success criterion.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.2 Audio Control replacing "on a Web page" with "in a document", "any content" with "any part of a document", "whole page" with "whole document", "on the Web page" with "in the document", removing "See Conformance Requirement 5: Non-Interference" and adding note 1.

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:

• Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1.
• Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
• Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

NOTE 1: Content for which there are software players, viewers or editors with a 200 percent zoom feature would automatically meet this success criterion when used with such players, unless the content will not work with zoom.

NOTE 2: This success criterion is about the ability to allow users to enlarge the text on screen at least up to 200 % without needing to use assistive technologies. This means that the application provides some means for enlarging the text 200 % (zoom or otherwise) without loss of content or functionality or that the application works with the platform features that meet this requirement.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.4 Resize text with the addition of notes 1 and 2 above.

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:

• 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 1: Logotypes (text that is part of a logo or brand name) are considered essential.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 1.4.5 Images of Text.

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.

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.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 2.1.1 Keyboard.

If keyboard focus can be moved to a component of the document 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.

NOTE 1: Since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document, all content in the document (whether or not it is used to meet other success criteria) must meet this success criterion.

NOTE 2: Standard exit methods may vary by platform. For example, on many desktop platforms, the Escape key is a standard method for exiting.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 2.1.2 No Keyboard Trap replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" and with the addition of note 1 above.

For each time limit that is set by the document, at least one of the following is true:

• 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 essential and extending it would invalidate the activity; or
• 20 Hour Exception: The time limit is longer than 20 hours.

NOTE 1: 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 WCAG 2.0 Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.2.1 Timing Adjustable replacing "the content" with "documents" and with the words "WCAG 2.0" added before the word "Success Criterion" in note 1 above.

For moving, blinking, scrolling, or auto-updating information, all of the following are true:

• 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 1: For requirements related to flickering or flashing content, refer to WCAG 2.0 Guideline 2.3.

NOTE 2: This success criteria is applicable to all content in the document (whether or not there is an alternate accessible version of the document) since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document (including a link to the alternate version).

NOTE 3: 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 4: 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.

NOTE 5: This is to be applied to all content. Any content, whether informative or decorative, that is updated automatically, blinks, or moves may create an accessibility barrier.

NOTE 6: This success criterion is identical to the WCAG 2.0 Success Criterion 2.2.2 Pause, Stop, Hide replacing "page" and "Web page" with "document", removing "See Conformance Requirement 5: Non-Interference" in note 2 of the success criterion, with the words "WCAG 2.0" added before the word "Guideline" in note 1 above and with note 2 above re-drafted to avoid the use of the word "must".

Documents 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.

NOTE 1: This success criterion is applicable to all content in the document (whether or not there is an alternate accessible version of the document) since any part of a document that does not meet this success criterion can interfere with a user's ability to use the whole document (including a link to the alternate version).

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.3.1 Three Flashes or Below Threshold replacing "Web pages" with "documents", "the whole page" with "the whole document", "the Web page" with "the document" and removing "See Conformance Requirement 5: Non-Interference" and with note 2 above re-drafted to avoid the use of the word "must".

Documents have titles that describe topic or purpose.

NOTE 1: The name of a document (e.g. document, media file) is a sufficient title if it describes the topic or purpose.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.2 Page Titled replacing "Web pages" with "documents", "Page" with "Document" and with the addition of note 1 above.

If a document can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.3 Focus Order replacing "Web page" with "document".

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

NOTE: This success criterion is identical to the WCAG 2.0 Success Criterion 2.4.4 Link Purpose (In Context).

NOTE 1: Some compound documents and their user agents are designed to provide significantly different viewing and editing functionality depending upon what portion of the compound document is being interacted with (e.g. a presentation that contains an embedded spreadsheet, where the menus and toolbars of the user agent change depending upon whether the user is interacting with the presentation content, or the embedded spreadsheet content). If the user uses a mechanism other than putting focus on that portion of the compound document with which they mean to interact (e.g. by a menu choice or special keyboard gesture), any resulting change of context would not be subject to this success criterion because it was not caused by a change of focus.

NOTE 2: This success criterion is identical to the WCAG 2.0 Success Criterion 3.2.1 On Focus with the addition of note 1.

For documents that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true:

1. Reversible: Submissions are reversible.
2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

NOTE 1: This success criterion is primarily for software developers who develop or use custom user interface components. Standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification.

NOTE 2: For document formats that support interoperability with assistive technology, standard user interface components often meet this success criterion when used according to the general design and accessibility guidance for the document format.

NOTE 3: This success criterion is identical to the WCAG 2.0 Success Criterion 4.1.2 Name, Role, Value replacing the original WCAG 2.0 note with: "This success criterion is primarily for software developers who develop or use custom user interface components. For example, standard user interface components on most accessibility-supported platforms already meet this success criterion when used according to specification." and with the addition of note 2 above.