Quick View



***************NOTICE************************************************ 
                                                                                                       
  This work space is being phased out and is no longer kept        
  updated with the latest task force agreements. Please refer to  
  the most recent WCAG2ICT public draft at                                 
  http://www.w3.org/TR/wcag2ict/                                                  
                                                                                                       
************************************************************************* 


Based on Editors Draft on February 12, 2013

Principle 1: Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

Guideline 1.1: Text Alternatives

From Guideline 1.1:

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

Additional guidance when applying Guideline 1.1 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 1.1.

Success Criterion 1.1.1: Non-text Content (Level A)

From Success Criterion 1.1.1:

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 Guideline 4.1 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 Guideline 1.2 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.

  • CAPTCHAIf 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 byassistive technology.

Additional guidance when applying Success Criterion 1.1.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note 1: CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance is accurate. If they do not appear then the success criterion would be met automatically, as with any situation where a success criterion talks about something that is not present.

Note 2: See also the discussion on Closed Functionality in the Introduction.

Guideline 1.2: Time-based Media

From Guideline 1.2:

Provide alternatives for time-based media.

Additional guidance when applying Guideline 1.2 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 1.2.

Success Criterion 1.2.1: Audio-only and Video-only (Prerecorded) (Level A)

From Success Criterion 1.2.1:

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

  • Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.

  • Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.

Additional guidance when applying Success Criterion 1.2.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note 1: The alternative can be provided directly in the non-web document or software – or provided in a conforming alternate version.

Note 2: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 1.2.2: Captions (Prerecorded) (Level A)

From Success Criterion 1.2.2:

Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.

Additional guidance when applying Success Criterion 1.2.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note: 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”.

Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded) (Level A)

From Success Criterion 1.2.3:

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

Additional guidance when applying Success Criterion 1.2.3 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

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: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 1.2.4: Captions (Live) (Level AA)

From Success Criterion 1.2.4:

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

Additional guidance when applying Success Criterion 1.2.4 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note: 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”.

Success Criterion 1.2.5: Audio Description (Prerecorded) (Level AA)

From Success Criterion 1.2.5:

Audio description is provided for all prerecorded video content in synchronized media.

Additional guidance when applying Success Criterion 1.2.5 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note1: The WCAG 2.0 definition of “audio description” says that audio description is “Also called ‘video description’ and ‘descriptive narration’”.

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

Guideline 1.3: Adaptable

From Guideline 1.3:

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Additional guidance when applying Guideline 1.3 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 1.3.

Success Criterion 1.3.1: Info and Relationships (Level A)

From Success Criterion 1.3.1:

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Additional guidance when applying Success Criterion 1.3.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note 1: In software, programmatic determinability is best achieved through the use of accessibility services provided by platform software to enable interoperability between software and assistive technologies.

Note 2: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 1.3.2: Meaningful Sequence (Level A)

From Success Criterion 1.3.2:

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

Additional guidance when applying Success Criterion 1.3.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 1.3.3: Sensory Characteristics (Level A)

From Success Criterion 1.3.3:

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: For requirements related to color, refer to Guideline 1.4.

Additional guidance when applying Success Criterion 1.3.3 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Guideline 1.4: Distinguishable

From Guideline 1.4:

Make it easier for users to see and hear content including separating foreground from background.

Additional guidance when applying Guideline 1.4 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 1.4.

Success Criterion 1.4.1: Use of Color (Level A)

From Success Criterion 1.4.1:

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

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.

Additional guidance when applying Success Criterion 1.4.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Success Criterion 1.4.2: Audio Control (Level A)

From Success Criterion 1.4.2:

If any audio on a Web page 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: 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 or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Additional guidance when applying Success Criterion 1.4.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “on a Web page” with “in a non-web document or software”, “any content” with “any part of a non-web document or software”, “whole page” with “whole document or software”, and “on the Web page” with “in the document or software”.

With these substitutions, it would read:

1.4.2 Audio Control: If any audio in a non-web document or software 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. (Level A)

Note: Since any part of a non-web document or software that does not meet this success criterion can interfere with a user's ability to use the whole document orsoftware, all content in the document or software (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Success Criterion 1.4.3: Contrast (Minimum) (Level AA)

From Success Criterion 1.4.3:

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.

Additional guidance when applying Success Criterion 1.4.3 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Success Criterion 1.4.4: Resize text (Level AA)

From Success Criterion 1.4.4:

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

Additional guidance when applying Success Criterion 1.4.4 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

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: The INTENT refers to 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: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 1.4.5: Images of Text (Level AA)

From Success Criterion 1.4.5:

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

Additional guidance when applying Success Criterion 1.4.5 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note: See also the discussion on Closed Functionality in the Introduction.

Principle 2: Operable

User interface components and navigation must be operable.

Guideline 2.1: Keyboard Accessible

From Guideline 2.1:

Make all functionality available from a keyboard.

Additional guidance when applying Guideline 2.1 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 2.1.

Success Criterion 2.1.1: Keyboard (Level A)

From Success Criterion 2.1.1:

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.

Additional guidance when applying Success Criterion 2.1.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note 1: This does not imply that software must directly support a keyboard or “keyboard interface”. Nor does it imply that software must provide a soft keyboard. Underlying platform software may provide device independent input services to applications that enable operation via a keyboard. Software that supports operation via such platform device independent services would be operable by a keyboard and would comply.

Note 2: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 2.1.2: No Keyboard Trap (Level A)

From Success Criterion 2.1.2:

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.

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.

Additional guidance when applying Success Criterion 2.1.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

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

Guideline 2.2: Enough Time

From Guideline 2.2:

Provide users enough time to read and use content.

Additional guidance when applying Guideline 2.2 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 2.2.

Success Criterion 2.2.1: Timing Adjustable (Level A)

From Success Criterion 2.2.1:

For each time limit that is set by the content, 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: 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.

Additional guidance when applying Success Criterion 2.2.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Success Criterion 2.2.2: Pause, Stop, Hide (Level A)

From Success Criterion 2.2.2:

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 Guideline 2.3.

Note 2: 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.

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.

Additional guidance when applying Success Criterion 2.2.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note: While the success criteria uses the term “information”, the WCAG 2.0 INTENT section makes it clear that 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.

Guideline 2.3: Seizures

From Guideline 2.3:

Do not design content in a way that is known to cause seizures.

Additional guidance when applying Guideline 2.3 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 2.3.

Success Criterion 2.3.1: Three Flashes or Below Threshold (Level A)

From Success Criterion 2.3.1:

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.

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.

Additional guidance when applying Success Criterion 2.3.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above), replacing “Web pages” with “non-web documents or software” , “the whole page” with “the whole non-web document or software” and “the Web page” with “the non-web document or software”.

With these substitutions, it would read:

2.3.1 Three Flashes or Below Threshold: non-web documents or software 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 non-Web document or software, all content on the non-web document or software (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Guideline 2.4: Navigable

From Guideline 2.4:

Provide ways to help users navigate, find content, and determine where they are.

Additional guidance when applying Guideline 2.4 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 2.4.

Success Criterion 2.4.1: Bypass Blocks (Level A)

From Success Criterion 2.4.1:

mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

Additional guidance when applying Success Criterion 2.4.1 to Non-Web Documents and Software:

For Documents:

This applies as written and described in INTENT of Understanding WCAG 2.0 (above), replacing “Web pages” with “documents within a set of non-web documents”. 

With these substitutions, it would read:

2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple documents within a set of non-web documents.

For Software: 

The WCAG2ICT Task Force has not yet produced additional guidance for software for Success Criterion 2.4.1.

Success Criterion 2.4.2: Page Titled (Level A)

From Success Criterion 2.4.2:

Web pages have titles that describe topic or purpose.

Additional guidance when applying Success Criterion 2.4.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “Web pages”  with “non-web documents or software”.

With these substitutions, it would read:

2.4.2 Page Titled: Non-web documents or software have titles that describe topic or purpose. (Level A)

Note 1: As described in the WCAG intent (above), the name of a software application or non-web document (e.g. document, media file, etc.) is a sufficient title.

Note 2: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 2.4.3: Focus Order (Level A)

From Success Criterion 2.4.3:

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.

Additional guidance when applying Success Criterion 2.4.3 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “Web pages”  with “non-web documents or software”.

With these substitutions, it would read:

2.4.3 Focus Order: If non-web documents or software 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)

Success Criterion 2.4.4: Link Purpose (In Context) (Level A)

From Success Criterion 2.4.4:

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.

Additional guidance when applying Success Criterion 2.4.4 to Non-Web Documents and Software:

This applies directly as written and as described in INTENT from Understanding WCAG 2.0 (above), replacing both “Web page” and “page” with “non-web documents and software” in the INTENT.

Note: In software, a “link” is any text string or image in the user interface outside a user interface control that behaves like a hypertext link. This does not include general user interface controls or buttons. (An OK button, for example, would not be a link.)

Success Criterion 2.4.5: Multiple Ways (Level AA)

From Success Criterion 2.4.5:

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.

Additional guidance when applying Success Criterion 2.4.5 to Non-Web Documents and Software:

For Documents:

This applies as written and described in INTENT of Understanding WCAG 2.0 (above), replacing “Web pages” with “documents” and “set of Web pages” with “set of non-web documents”.

With these substitutions, it would read:

2.4.5 Multiple Ways: More than one way is available to locate a document within a set of non-web documents except where the document is the result of, or a step in, a process.

Note 1: Authors should assume that an infrastructure exists to allow a user to locate documents in the set; for example, by selecting links within a member of the set, browsing through the files that make up the set, or by searching within members of the set for the names of the other members.

Note 2: A file directory would be the equivalent of a site map for documents in that it provides a link to each of the documents in the set of documents. The directory also acts as the HOME for the set.

Note 3: A search function in a file system (that finds documents) would be equivalent to a Web search function for Web pages.

Note 4: Authors can assume that the non-Web documents will be stored and accessed on a major operating system with browse and search abilities unless they have specific information to the contrary.

For Software: 

The WCAG2ICT Task Force has not yet produced additional guidance for software for Success Criterion 2.4.5.

Success Criterion 2.4.6: Headings and Labels (Level AA)

From Success Criterion 2.4.6:

Headings and labels describe topic or purpose.

Additional guidance when applying Success Criterion 2.4.6 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note: Note that in software, headings and labels are used to describe sections of content and controls respectively. In some cases it may be unclear whether a piece of static text is a heading or a label. But whether treated as a label or a heading, the requirement is the same: that if they are present they describe the topic or purpose of the item(s) they are associated with.

Success Criterion 2.4.7: Focus Visible (Level AA)

From Success Criterion 2.4.7:

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

Additional guidance when applying Success Criterion 2.4.7 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Principle 3: Understandable

Information and the operation of user interface must be understandable.

Guideline 3.1: Readable

From Guideline 3.1:

Make text content readable and understandable.

Additional guidance when applying Guideline 3.1 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 3.1.

Success Criterion 3.1.1: Language of Page (Level A)

From Success Criterion 3.1.1:

The default human language of each Web page can be programmatically determined.

Additional guidance when applying Success Criterion 3.1.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “each Web page”  with non-web documents or software.

With these substitutions, it would read:

3.1.1 Language of Page: The default human language of non-web documents or software can be programmatically determined. (Level A) 

Note 1: Where software platforms provide a “locale/language” setting, applications that use that setting and render their interface in that “locale/language” would comply with this success criterion. Applications that do not use the platform “locale/language setting” but instead use an accessibility supported method for exposing the human language of thesoftware would also comply with this success criterion. Applications implemented in technologies where assistive technologies cannot determine the human language and that do not support the platform “locale/language” setting may not be able to meet this success criterion in that locale/language.

Note 2: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 3.1.2: Language of Parts (Level AA)

From Success Criterion 3.1.2:

The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.

Additional guidance when applying Success Criterion 3.1.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “content”  with “the non-web document or software”.

With these substitutions, it would read:

3.1.2 Language of Parts: The human language of each passage or phrase in the non-web document or software can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA)

Note 1: There are some software and non-web document technologies where there is no assistive technology supported method for marking the language for the different passages or phrases in the non-web document or software, and it would not be possible to meet this success criterion with those technologies.

Note 2: See also the discussion on Closed Functionality in the Introduction.

Guideline 3.2: Predictable

From Guideline 3.2:

Make Web pages appear and operate in predictable ways.

Additional guidance when applying Guideline 3.2 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 3.2.

Success Criterion 3.2.1: On Focus (Level A)

From Success Criterion 3.2.1:

When any component receives focus, it does not initiate a change of context.

Additional guidance when applying Success Criterion 3.2.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Success Criterion 3.2.2: On Input (Level A)

From Success Criterion 3.2.2:

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

Additional guidance when applying Success Criterion 3.2.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Success Criterion 3.2.3: Consistent Navigation (Level AA)

From Success Criterion 3.2.3:

Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.

]Additional guidance when applying Success Criterion 3.2.3 to Non-Web Documents and Software:

For Documents:

This applies as written and described in INTENT of Understanding WCAG 2.0 (above), replacing “Web pages” with “documents” and “set of Web pages” with “set of non-web documents”.

With these substitutions, it would read:

3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple documents within a  set of non-web documents occur in the same relative order each time they are repeated, unless a change is initiated by the user.

For Software: 

The WCAG2ICT Task Force has not yet produced additional guidance for software for Success Criterion 3.2.3.

Success Criterion 3.2.4: Consistent Identification (Level AA)

From Success Criterion 3.2.4:

Components that have the same functionality within a set of Web pages are identified consistently.

Additional guidance when applying Success Criterion 3.2.4 to Non-Web Documents and Software:

For Documents:

This applies as written and described in INTENT of Understanding WCAG 2.0 (above), replacing “set of Web pages” with “set of non-web documents”.

With these substitutions, it would read:

3.2.4: Consistent Identification: Components that have the same functionality within a set of non-web documents are identified consistently. (Level AA)

For Software: 

The WCAG2ICT Task Force has not yet produced additional guidance for software for Success Criterion 3.2.4.

Guideline 3.3: Input Assistance

From Guideline 3.3:

Help users avoid and correct mistakes.

Additional guidance when applying Guideline 3.3 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 3.3.

Success Criterion 3.3.1: Error Identification (Level A)

From Success Criterion 3.3.1:

If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.

Additional guidance when applying Success Criterion 3.3.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 3.3.2: Labels or Instructions (Level A)

From Success Criterion 3.3.2:

Labels or instructions are provided when content requires user input.

Additional guidance when applying Success Criterion 3.3.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Success Criterion 3.3.3: Error Suggestion (Level AA)

From Success Criterion 3.3.3:

If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.

Additional guidance when applying Success Criterion 3.3.3 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Success Criterion 3.3.4: Error Prevention (Legal, Financial, Data) (Level AA)

From Success Criterion 3.3.4:

For Web pages 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: mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

Additional guidance when applying Success Criterion 3.3.4 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “a set of Web pages” with “a non-web document or software”.

With these substitutions, it would read:

3.3.4 Error Prevention (Legal, Financial, Data): For a non-web document or software 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: (Level AA)

  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: mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.

Principle 4: Robust

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

Guideline 4.1: Compatible

From Guideline 4.1:

Maximize compatibility with current and future user agents, including assistive technologies.

Additional guidance when applying Guideline 4.1 to Non-Web Documents and Software:

The WCAG2ICT Task Force has not yet reviewed at the Guideline level; see success criteria below for guidance on Guideline 4.1.

Success Criterion 4.1.1: Parsing (Level A)

From Success Criterion 4.1.1:

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.

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.

Additional guidance when applying Success Criterion 4.1.1 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “In content implemented using markup languages” with “For non-Web documents or software that use markup languages, in such a way that the markup is separately exposed and available to assistive technology or to a user-selectable user agent”.

With these substitutions, it would read:

4.1.1 Parsing:  For non-Web documents or software that use markup languages, in such a way that the markup is separately exposed and available to assistive technology or to a user-selectable user agent, 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.

Note: Markup is not always available to assistive technology or to user selectable user agents such as browsers.  Software sometimes uses markup languages internally for persistence of the software user interface, in ways where it is never available to assistive technology (either directly or through a document object model (DOM)), or to a user agent (such as a browser). In such cases, conformance to this provision would have no impact on accessibility as it can for Web Content where it is exposed.

Examples of markup that is separately exposed and available to assistive technology and to user agents include: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by assistive technologies which may directly open the document, (b) by assistive technologies using DOM APIs of user agents for these document formats.

Examples of markup used internally for persistence of the software user interface that are never exposed to assistive technology include: XUL, GladeXML, and FXML. In these examples assistive technology only interacts with the user interface of generated software.

Note: See also the discussion on Closed Functionality in the Introduction.

Success Criterion 4.1.2: Name, Role, Value (Level A)

From Success Criterion 4.1.2:

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.

Additional guidance when applying Success Criterion 4.1.2 to Non-Web Documents and Software:

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note 1: For conforming to this success criterion, it is usually best practice for software user interfaces to use the accessibility services provided by platform software. These accessibility services enable interoperability between software user interfaces and assistive technologies in standardised ways. Most platform accessibility services go beyond programmatic exposure of name and role, and programmatic setting of states, properties and values (and notification of same), and specify additional information that could or should be exposed and/or set (for instance, a list of the available actions for a given user interface component, and a means to programmatically execute one of the listed actions).

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: See also the discussion on Closed Functionality in the Introduction.



OLD QUICKVIEW 


Work space for comparing our guidance text to ensure consistency of wording and to spot editorial issues.  Only Single A Success Criteria are addressed in the 27 July 2012 Working Draft.

Background color highlighting is used to supplement data cells in the second column as follows:

  • If the only paragraph of the data cell in the second column reads The WCAG2ICT Task Force has not yet produced additional guidance for Success Criterion X.Y.Z., then the cell has a light yellow background.
  • The phrase This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) has a light green background. Several data cells have this sentence as their only contents.
  • The word document, the phrase electronic document, and plural forms (documents, electronic documents) are strongly emphasized and have a purple background.
  • The word content and any modifier (i.e., all content, any content, electronic content, media content, and Web content) are strongly emphasized and have a magenta (pink) background.
  • The phrases Web page, Web pages, and set of Web pages are strongly emphasized and have a red background.
  • The word software and the phrases platform software, software user interface, user interface, user interface component, user interface control, and any plural forms, are strongly emphasized and have a light blue (cyan) background.

 

Principle 1: Perceivable — Information and user interface components must be presentable to users in ways they can perceive.
Perceivable Success Criteria Task Force Guidance
1.1 Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.1.1 Non-text Content

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note 1: CAPTCHAs do not currently appear outside of the Web. However, if they do appear, this guidance is accurate. If they do not appear then the success criterion would be met automatically, as with any situation where a success criterion talks about something that is not present.
Note 2: See also the discussion on Closed Functionality in the Introduction.
1.2 Provide alternatives for time-based media
1.2.1 Audio-only and Video-only (Prerecorded)

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

The alternative can be provided directly in the electronic document or software – or provided in a conforming alternate version.

1.2.2 Captions (Prerecorded)

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note:  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.
1.2.3 Audio Description or Media Alternative (Prerecorded)

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

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.

1.2.4 Captions (Live)

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note:  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.

1.2.5 Audio Description (Prerecorded)

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note1:  The WCAG 2.0 definition of audio description says that audio description is Also called video description and descriptive narration.

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

1.3 Create content that can be presented in different ways
1.3.1 Info and Relationships

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note:  In software, programmatic determinability is best achieved through the use of accessibility services provided by platform software to enable interoperability between software and assistive technologies.

1.3.2 Meaningful Sequence

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) where content is interpreted to mean information and sensory experience to be communicated to the user by means of ICT.

1.3.3 Sensory Characteristics

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

1.4 Make it easier for users to see and hear content
1.4.1 Use of Color

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing Web content with electronic documents and software in the INTENT.

1.4.2 Audio Control

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing a Web page with an electronic document or a software user interface and any content with any part of an electronic document or software user interface.

1.4.3 Contrast (Minimum)

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

1.4.4 Resize text

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

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.

The INTENT refers to 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.

1.4.5 Images of Text

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

 

Principle 2:  Operable — User interface components and navigation must be operable.
Operable Success Criteria Task force Guidance
2.1 Make all functionality available from a keyboard
2.1.1 Keyboard

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note:  This does not imply that software must directly support a keyboard or keyboard interface.  Nor does it imply that software must provide a soft keyboard.  Underlying platform software may provide device independent input services to applications that enable operation via a keyboard.  Software that supports operation via such platform device independent services would be operable by a keyboard and would comply.

2.1.2 No Keyboard Trap

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

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

2.2 Provide users enough time to read and user content
2.2.1 Timing Adjustable

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above), replacing content with electronic documents and software.

2.2.2 Pause, Stop, Hide

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note:  While the success criteria uses the term information, the WCAG 2.0 INTENT section makes it clear that this is to be applied to all contentAny content, whether informative or decorative, that is updated automatically, blinks, or moves may create an accessibility barrier.

2.3 Do not design content in a way that is known to cause seizures
2.3.1 Three Flashes or Below Threshold This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above), replacing Web pages with electronic documents and software.
2.4 Provide users ways to navigate, find content, and determine where they are
2.4.1 Bypass Blocks

The WCAG2ICT Task Force has not yet produced additional guidance for Success Criterion 2.4.1.

2.4.2 Page Titled

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “Web pages” with “non-embedded content or software”.

Note:  As described in the WCAG intent (above), the name of a software application or non-embedded content (e.g. document, media file, etc.) is a sufficient title.

2.4.3 Focus Order

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing a Web page with an electronic document or a software user interface.

2.4.4 Link Purpose (in context) This applies directly as written and as described in INTENT from Understanding WCAG 2.0 (above), replacing Web page with electronic documents and software in the INTENT.  In software, a link is any text string or image in the user interface outside a user interface control that behaves like a hypertext link.  This does not include general user interface controls or buttons.  (An OK button, for example, would not be a link.)
2.4.5 Multiple Ways

This applies to documents directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing "web pages" with "documents" and replacing "set of web pages" with "set of documents". A set of documents is a group of documents that are 1) published together, and 2) labeled as a set within at least one member document. Republishing previously published documents as a collection does not constitute a set of documents.

NOTE: Authors should assume that the set is not broken apart, and that an infrastructure exists to allow a user to locate documents in the set; for example, by selecting links within a member document, browsing through the files that make up the set, or by searching the documents' contents or the names of the member documents.

<The WCAG2ICT TF has not yet produced additional guidance on 2.4.5 for software.>

2.4.6 Headings and Labels

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

Note that in software user interfaces, headings and labels are used to describe controls and sections of content respectively. In some cases it may be unclear whether a piece of static text is a heading or a label. But whether treated as a label or a heading, the requirement is the same: that if they are present they describe the topic or purpose of the item(s) they are associated with.

2.4.7 Focus Visible

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

 

Principle 3: Understandable — Information and the operation of user interface must be understandable.
Understandable Success Criteria Task force Guidance
3.1 Make text readable and understandable
3.1.1 Language of Page

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0  (above) replacing "each Web page" with "the electronic document or software".

Note: Where software platforms provide a "locale/language" setting, applications that use that setting and render their interface in that "locale/language" would comply with this success criterion. Applications that do not use the platform "locale/language setting" but instead use an accessibility supported method for exposing the human language of the software user interface would also comply with this success criterion. Applications implemented in technologies where assistive technologies cannot determine the human language and that do not support the platform "locale/language" setting may not be able to meet this success criterion in that locale/language.
3.1.2 Language of Parts

"This applies directly as written, and as described in INTENT from Understanding WCAG 2.0  (above) replacing "content" with "electronic document or software"

Note: There are some software and document technologies where there is no assistive technology supported method for marking the language for the different passages or phrases in the document or software, and it would not be possible to meet this success criterion with those technologies.
3.2 Make web pages appear and operate in predictable ways
3.2.1 On Focus

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

3.2.2 On Input

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

3.2.3 Consistent Navigation

The WCAG2ICT Task Force has not yet produced additional guidance for Success Criterion 3.2.3.

3.2.4 Consistent Identification This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing a set of Web pages with an electronic document or a software user interface.
3.3 Help users avoid and correct mistakes
3.3.1 Error Identification

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

3.3.2 Labels or Instructions

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above)

3.3.3 Error Suggestion

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above)

3.3.4 Error Prevention (Legal, Financial, Data)

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above)

 

Principle 4: Robust — Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Robust Success Criteria Task force Guidance
4.1 Maximize compatibility with current and future user agents
4.1.1 Parsing

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above) replacing “In content implemented using markup languages”  with  “For software and non-embedded content that use markup languages, in such a way that the markup is separately exposed and available to assistive technology (AT) or to a user-selectable user agent".

Note: Markup is not always available to AT or to user selectable user agents such as browsers.  Software sometimes uses markup languages internally for persistence of the software user interface, in ways where it is never available to AT (either directly or through a document object model (DOM)), or to a user agent (such as a browser). In such cases, conformance to this provision would have no impact on accessibility as it can for Web Content where it is exposed.

Examples of markup that is separately exposed and available to AT and to user agents include: documents encoded in HTML, ODF, and OOXML. In these examples, the markup can be parsed entirely in two ways: (a) by AT which may directly open the document, (b) by AT using DOM APIs of user agents for these document formats.

Examples of markup used internally for persistence of the software user interface that are never exposed to AT include: XUL, GladeXML, and FXML. In these examples AT only interacts with the user interface of generated software.

4.1.2 Name, Role, Value

This applies directly as written, and as described in INTENT from Understanding WCAG 2.0 (above).

For conforming to this success criterion, it is usually best practice for software user interfaces to use the accessibility services provided by platform software.  These accessibility services enable interoperability between software user interfaces and assistive technologies in standardised ways.  Most platform accessibility services go beyond programmatic exposure of name and role, and programmatic setting of states, properties and values (and notification of same), and specify additional information that could or should be exposed and/or set (for instance, a list of the available actions for a given user interface component, and a means to programmatically execute one of the listed actions).

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