[contents]

Web Content Accessibility Guidelines 2.0

Editor's Draft April 2007

This version:
http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20070220/
Latest version:
http://www.w3.org/TR/WCAG20/
Previous version:
http://www.w3.org/TR/2006/WD-WCAG20-20060427/
Editors:
Ben Caldwell, Trace R&D Center, University of Wisconsin-Madison
Michael Cooper, W3C
Loretta Guarino Reid, Google, Inc.
Gregg Vanderheiden, Trace R&D Center, University of Wisconsin-Madison
Previous Editors:
Wendy Chisholm (until July 2006 while at W3C)
John Slatin (until June 2006 while at Accessibility Institute, University of Texas at Austin)
Jason White (until June 2005 while at University of Melbourne)

This document is also available in these non-normative formats:


Abstract

Web Content Accessibility Guidelines 2.0 (WCAG 2.0) covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech difficulties, photosensitivity and combinations of these. Following these guidelines will also make your Web content more accessible to the vast majority of users, including some older users. These guidelines however are not able to address the needs of all people with disabilities.

WCAG 2.0 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies as well as general information about interpreting the success criteria are provided in separate documents. An Overview of Web Content Accessibility Guidelines (WCAG) 2.0 Last Call Documents is also available.

Until WCAG 2.0 advances to W3C Recommendation, the current and referenceable document is Web Content Accessibility Guidelines 1.0 (WCAG 1.0), published as a W3C Recommendation May 1999.

Status of this Document

This document is the internal working draft used by the WCAG WG and is updated continuously and without notice. This document has no formal standing within W3C. Please consult the group's home page and the W3C technical reports index for information about the latest publications by this group.

This draft includes revisions that have been made since the 27 April 2006 Working Draft was published. Please refer to the latest public version of WCAG 2.0 for information about the status of WCAG 2.0 as well as information about submitting comments to the working group.

History of Changes to WCAG 2.0 Working Drafts


Table of Contents

Appendices


Introduction

This section is informative.

You are reading a working draft of the Web Content Accessibility Guidelines (WCAG) version 2.0. This is the central document that defines the requirements for making Web content more accessible to a wide range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech difficulties, and others. Because many people develop vision, hearing, or motion impairments as they age, following these guidelines will make your Web content more usable by many older users. However, even content that completely conforms to WCAG may not be fully accessible to every person with a disability.

WCAG 2.0 covers a wide range of recommendations for making Web content more accessible. The guidelines do not include standard usability recommendations except where they have a significantly greater impact on people with disabilities than on other people.

Although some of the accessibility issues of people with cognitive, language, and learning disabilities are addressed by WCAG 2.0, either directly or through assistive technologies, the WCAG 2.0 guidelines do not address many areas of need for people with these disabilities. There is a need for more research and development in this important area.

The WCAG 2.0 document itself consists of:

Organization of WCAG 2.0

In addition to the Web Content Accessibility Guidelines 2.0 (this document), there are a number of WCAG 2.0 related support documents that provide additional information and examples. These documents are informative only and do not define conformance to WCAG 2.0. Only the normative Web Content Accessibility Guidelines document itself can be used for determining conformance to these guidelines. Readers should consult WCAG 2.0 in order to determine the exact wording of the success criteria and for information about documenting conformance.

The WCAG 2.0 related support documents in this set are provided to help readers understand WCAG 2.0 and how to produce conforming content. These informative documents are written to be used by a diverse audience, including, but not limited to people who create Web content, developers who write code, quality assurance or accessibility evaluators, policy makers, managers, and Web users.

Currently, the WCAG 2.0 related support documents include:

  • people who create Web content,

  • developers who write code,

  • quality assurance or accessibility evaluators,

  • policy makers,

  • managers,

  • users

Currently, these informative documents include:

  • Essential Components of Web Accessibility - Explains how the Web Content Accessibility Guidelines work with the other WAI guidelines (the User Agent Accessibility Guidelines and the Authoring Tool Accessibility Guidelines) and with assistive technologies to provide access to the Web by people with disabilities.

  • Overview of Web Content Accessibility Guidelines (WCAG) 2.0 Documents - Provides an overview of WCAG 2.0 and its various informative support documents.

  • About Baselines for WCAG 2.0 - Provides additional information on baselines.

  • Understanding WCAG 2.0 - Provides information about each success criterion, including:

    • its intent,

    • key terms from the WCAG 2.0 Glossary needed to understand the success criterion,

    • names of and links to techniques that the working group deems sufficient to meet the success criterion, and

    • examples and benefits of the success criterion.

    Note: Each of the "How to meet SC x.x.x" links in WCAG 2.0 links to the relevant section of the Understanding WCAG 2.0 document.

  • Techniques and Failures for WCAG 2.0 - Provide specific details on different techniques, including examples, code, and tests.

    Note: The development of techniques documents is an ongoing process. Developers are encouraged to submit new techniques at any time.

  • Application Notes - Provide detailed application information in different areas. For example, an application note on forms will provide a collection of techniques and strategies for creating accessible forms. It will also summarize the different success criteria that relate to forms.

    Note: Application notes are a future component that will be developed in conjunction with the Education and Outreach Working Group.

  • WCAG 2.0 Quick Reference - A summary of all WCAG 2.0 requirements (success criteria) and techniques sufficient to meet them.

The Working Group plans to publish a number of other technology-specific techniques documents and encourages development of techniques documents that show how to meet WCAG 2.0 using non-W3C technologies. Please visit the Working Group home page for a complete list of these and other informative documents related to WCAG 2.0.

Every attempt has been made to make WCAG 2.0 and the related documents listed above as readable and usable as possible while retaining the accuracy and clarity needed in a technical specification. Sometimes technical terms are needed for clarity or testability. In these cases, the terms are defined in Appendix A: Glossary. To assist readers, there is a How to Meet link beside every success criterion that puts readers one click away from detailed information on that success criterion and two clicks away from the specific technique descriptions related to the success criterion.

The Working Group recognizes that readers who are new to accessibility may need or want additional information. For these readers, the work of the Web Accessibility Initiative and its Education and Outreach Working Group is highly recommended. The articles called Getting Started: Making a Web Site Accessible and How People with Disabilities Use the Web are especially useful.

Authoring tools

A large part of Web content is created using authoring tools. These tools often determine how Web content is implemented, either by making authoring decisions directly or by limiting the choices available to the author. As a result, authoring tools play an important role in creating Web content that conforms to the Web Content Accessibility Guidelines . At the same time, we recommend that all authors become familiar with the Guidelines because this will help in creating accessible content and coverage of the Guidelines may vary between tools.

Developers of authoring tools can make their tools aware of the Web Content Accessibility Guidelines by following the Authoring Tool Accessibility Guidelines. The working group encourages users and purchasers of authoring tools to consider conformance to the Authoring Tool Accessibility Guidelines as a criterion when selecting tools. The current version at WCAG 2.0's release is Authoring Tool Accessibility Guidelines 1.0. However, version 2.0 is nearing completion and it is based on WCAG 2.0. The latest version of the Authoring Tool Accessibility Guidelines 2.0 can be found at http://www.w3.org/TR/ATAG20.

The Role of User Agents

Web content is always rendered by a user agent or combination of user agents, including assistive technologies. A user agent is any software that retrieves and renders Web content for users.

Different user agents, or user agents that support customization, let users customize the rendering of content into a form that best meets their needs. When Web content conforms to WCAG 2.0, the same information can be presented effectively in a variety of forms and modalities.

WCAG 2.0 relies on user agents to present content in a way that meets the needs of users with disabilities. Web content that conforms to WCAG 2.0 is most likely to be accessible to users with disabilities when rendered by user agents that conform to the User Agent Accessibility Guidelines (UAAG). For more information about the relationship between WCAG 2.0 and other WAI accessibility guidelines, see Essential Components of Web Accessibility.

The Four Principles of Accessibility

The WCAG 2.0 Guidelines are organized around the following four principles:

  1. Perceivable - Information and user interface must be perceivable by the user

  2. Operable - User interface components must be operable by the user

  3. Understandable - Information and operation of user interface must be understandable by the user

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

These four principles lay the foundation necessary for anyone to access and use Web content. WCAG 2.0 offers information about how to increase the ability of people with disabilities to perceive, operate and understand Web content. Under each principle there is a list of guidelines that address the principle. Under each guideline there are success criteria used to evaluate conformance to this standard for that guideline. Each success criterion is written as a statement that will be either true or false when specific Web content is tested against it. The success criteria are grouped into three levels of conformance, each representing a higher level of accessibility for that guideline.

The principles, guidelines, and success criteria represent concepts that address accessibility issues and needs, regardless of the technology used. They are not specific to HTML, XML, or any other technology. This approach makes it possible to apply WCAG 2.0 to a variety of situations and technologies.

The principles and guidelines give direction and guidance to Web authors. The success criteria are the basis for determining conformance to WCAG 2.0 and are written as true/false statements. The success criteria define the minimum that needs to be done for the three levels of conformance. Additional advisory techniques are also provided that can allow authors to go further in addressing the guidelines and making pages even more accessible.

For more information, refer to Understanding the Four Principles of Accessibility.

Important New Terms Used in WCAG 2.0

WCAG 2.0 includes several important new terms. These terms are defined in the Glossary (Appendix A: Glossary), and links to the definitions are provided whenever these and other important terms are used in the success criteria. The terms are introduced briefly here to make this new vocabulary easier to understand.

While not an entirely new term, it is important to note that the term "Web page" has evolved to accommodate the increasingly dynamic nature of content. A Web page is a resource that is referenced by a Uniform Resource Identifier (URI) and is not embedded in another resource, plus any other resources that are used in the rendering or intended to be rendered together with it. It includes Web applications, Webcasts, multimedia objects and other types of interactive content to which the word "page" may not typically apply. It is in this evolved sense of the concept that the term is used in WCAG 2.0.

Example: A movie-like interactive shopping environment where the user visually moves about a store dragging products off of the shelves around them into a visual shopping cart in front of them where clicking on a product causes it to be demonstrated with a specification sheet alongside would be considered a "Web page."

The statements that define conformance in WCAG 2.0 are called "success criteria." Each success criterion is written as a testable statement and each is not technology-specific.

Several success criteria require that content (or certain aspects of content) can be "programmatically determined." This means that the content is delivered in such a way that user agents, including assistive technologies, can access it. This lets user agents and assistive technologies transform the content and present it to the user in different sensory modalities or styles of presentation. This is important in order to allow assistive technologies to recognize it and present it to the user, even if the user requires a different sensory modality than the original. For example, some assistive technologies convert text into speech or braille. This will also allow content in the future to be translated into simpler forms for people with cognitive, language, and learning disabilities, or to allow access by other agent based technologies. This can happen only if the content itself can be programmatically determined.

WCAG 2.0 also introduces the term "baseline" which allows WCAG 2.0 to adapt to changing technologies and to the needs of different countries and environments. Baselines are described in more detail in the conformance section and in About Baselines for WCAG 2.0.

WCAG 2.0 Guidelines

This section is normative.

Principle 1: Perceivable - Information and user interface must be perceivable by the user

Guideline 1.1 Provide text alternatives for all non-text content Understanding Guideline 1.1

Level 1 Success Criteria for Guideline 1.1

1.1.1 Non-text Content: All non-text content has a text alternative that presents equivalent information, except for the situations listed below. How to meet 1.1.1

(No level 2 success criteria for Guideline 1.1)

(No level 3 success criteria for Guideline 1.1)

Guideline 1.2 Provide synchronized alternatives for multimedia Understanding Guideline 1.2

Level 1 Success Criteria for Guideline 1.2

1.2.1 Captions (Prerecorded): Captions are provided for prerecorded multimedia, except for multimedia alternatives to text that are clearly labeled as such . How to meet 1.2.1

1.2.2 Audio Description or Full Text Alt.: Audio description of video, or a full text alternative for multimedia including any interaction , is provided for prerecorded multimedia. How to meet 1.2.2

Note: For 1.2.2, 1.2.4, and 1.2.7, if all of the information in the video track is already provided in the audio track, no audio description is necessary.

Level 2 Success Criteria for Guideline 1.2

1.2.3 Captions (Live): Captions are provided for live multimedia. How to meet 1.2.3

Note: If multimedia is completely computer generated, it is not live and is subject to the requirements for pre-recorded multimedia in WCAG 2.0.

1.2.4 Audio Description: Audio description of video is provided for prerecorded multimedia. How to meet 1.2.4

Level 3 Success Criteria for Guideline 1.2

1.2.5 Sign Language: Sign language interpretation is provided for multimedia. How to meet 1.2.5

1.2.6 Audio Description (Extended): Extended audio description of video is provided for prerecorded multimedia. How to meet 1.2.6

1.2.7 Full Text Alternative: A full text alternative for multimedia including any interaction is provided for all prerecorded multimedia . How to meet 1.2.7

Guideline 1.3 Ensure that presentation can be adapted by user agents without loss of information and structure Understanding Guideline 1.3

Level 1 Success Criteria for Guideline 1.3

1.3.1 Info and Relationships: Information and relationships conveyed through presentation can be programmatically determined or are available in text , and notification of changes to these is available to user agents, including assistive technologies. How to meet 1.3.1

1.3.2 Use of Color: Any information that is conveyed by color differences is also visually evident without the color differences. How to meet 1.3.2

1.3.3 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined and sequential navigation of interactive components is consistent with that sequence. How to meet 1.3.3

1.3.4 Size, Shape, Location: Instructions provided for understanding and operating content do not rely on shape, size, visual location, or orientation of components. How to meet 1.3.4

Level 2 Success Criteria for Guideline 1.3

(No level 3 success criteria for Guideline 1.3)

Guideline 1.4 Make it easy to distinguish foreground information from its background Understanding Guideline 1.4

Level 1 Success Criteria for Guideline 1.4

1.4.1 Audio Turnoff: If any audio 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 which can be set independently of the system volume. How to meet 1.4.1

Level 2 Success Criteria for Guideline 1.4

1.4.2 Contrast (Minimum): Text and images of text have a contrast ratio of at least 5:1 with their background. Text or images of text may have a contrast ratio of at least 3:1 where all of the following are true: How to meet 1.4.2

  • Text is at least twice the height of the body text; and

  • the text has a stem width of at least three times the stem width of the body text; and

  • the text is presented over a non-patterned background.

Note: This requirement does not apply to text or images of text that are pure decoration.

1.4.3 Resize text: Visually rendered text can be resized without assistive technology up to 200 percent and down to 50 percent without loss of content or functionality. How to meet 1.4.3

Level 3 Success Criteria for Guideline 1.4

1.4.4 Contrast (Enhanced): Text and images of text have a contrast ratio of at least 10:1 with their background. Text or images of text may have a contrast ratio of at least 7:1 where all of the following are true: How to meet 1.4.4

  • Text is at least twice the height of the body text; and

  • the text has a stem width of at least three times the stem width of the body text; and

  • the text is presented over a non-patterned background.

Note: This requirement does not apply to text or images of text that are pure decoration.

1.4.5 Low or No Background Audio: Audio content does not contain background sounds, background sounds can be turned off, or background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sound effects. How to meet 1.4.5

Note: Background sound that meets this requirement will be approximately one quarter as loud as the foreground speech content.

1.4.6 Resize and Wrap: Visually rendered text can be resized without assistive technology up to 200 percent and down to 50 percent without loss of content or functionality and in a way that does not require the user to scroll horizontally. How to meet 1.4.6

Principle 2: Operable - User interface components must be operable by the user

Guideline 2.1 Make all functionality operable via a keyboard interface Understanding Guideline 2.1

Level 1 Success Criteria for Guideline 2.1

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 task requires time-dependent analog input. How to meet 2.1.1

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

(No level 2 success criteria for Guideline 2.1)

Level 3 Success Criteria for Guideline 2.1

2.1.2 Keyboard (No Exception): All functionality of the content is operable in a non-time-dependent manner through a keyboard interface. How to meet 2.1.2

Guideline 2.2 Allow users to control time limits on their reading or interaction Understanding Guideline 2.2

Level 1 Success Criteria for Guideline 2.2

2.2.1 Timing: For each time limit that is set by the content , at least one of the following is true: How to meet 2.2.1

  • Deactivate: the user is allowed to deactivate 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, "hit any key"), 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 part of an activity where timing is essential (for example, competitive gaming or time-based testing) and time limits can not be extended further without invalidating the activity.

Level 2 Success Criteria for Guideline 2.2

2.2.3 Pausing: Moving, blinking, scrolling, or auto-updating information can be paused by the user unless it is part of an activity where timing or movement is essential. Moving content that is pure decoration can be stopped by the user. How to meet 2.2.3

Level 3 Success Criteria for Guideline 2.2

2.2.4 Timing: Timing is not an essential part of the event or activity presented by the content, except for non-interactive multimedia and real-time events . How to meet 2.2.4

2.2.5 Interruptions: Interruptions, such as updated content, can be postponed or suppressed by the user, except interruptions involving an emergency. How to meet 2.2.5

2.2.6 Re-authenticating: When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. How to meet 2.2.6

Guideline 2.3 Allow users to avoid content that could cause seizures due to photosensitivity Understanding Guideline 2.3

Level 1 Success Criteria for Guideline 2.3

2.3.1 Three Flashes or Below Threshold: Content does contain anything that flashes more than three times in any one second period, or the flash is below the general flash threshold and the red flash threshold . How to meet 2.3.1

(No level 2 success criteria for Guideline 2.3)

Level 3 Success Criteria for Guideline 2.3

2.3.2 Three Flashes: Content does not contain anything that flashes more than three times in any one second period. How to meet 2.3.2

Guideline 2.4 Provide mechanisms to help users find content, orient themselves within it, and navigate through it Understanding Guideline 2.4

Level 1 Success Criteria for Guideline 2.4

Level 2 Success Criteria for Guideline 2.4

Level 3 Success Criteria for Guideline 2.4

Principle 3: Understandable - Information and operation of user interface must be understandable by the user

Guideline 3.1 Make text content readable and understandable Understanding Guideline 3.1

Level 1 Success Criteria for Guideline 3.1

3.1.1 Language of Page: The default human language of each Web page within the content can be programmatically determined. How to meet 3.1.1

Level 2 Success Criteria for Guideline 3.1

3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined . How to meet 3.1.2

Note: This requirement does not apply to individual words. It also does not apply to proper names, to technical terms or to phrases that have become part of the language of the context in which they are used.

Level 3 Success Criteria for Guideline 3.1

3.1.3 Unusual Words: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. How to meet 3.1.3

3.1.4 Abbreviations: A mechanism for finding the expanded form or meaning of abbreviations is available. How to meet 3.1.4

3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level, supplemental content or an alternate version is available that does not require reading ability more advanced than the lower secondary education level. How to meet 3.1.5

3.1.6 Pronunciation: A mechanism is available for identifying specific pronunciation of words where meaning is ambiguous without knowing the pronunciation. How to meet 3.1.6

Guideline 3.2 Make the placement and functionality of content predictable Understanding Guideline 3.2

Level 1 Success Criteria for Guideline 3.2

3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. How to meet 3.2.1

3.2.2 On Input: 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. How to meet 3.2.2

Level 2 Success Criteria for Guideline 3.2

3.2.3 Consistent Navigation: 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. How to meet 3.2.3

3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. How to meet 3.2.4

Level 3 Success Criteria for Guideline 3.2

3.2.5 Change on Request: Changes of context are initiated only by user request. How to meet 3.2.5

Guideline 3.3 Help users avoid mistakes and make it easy to correct mistakes Understanding Guideline 3.3

Level 1 Success Criteria for Guideline 3.3

3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and described to the user in text. How to meet 3.3.1

Level 2 Success Criteria for Guideline 3.3

3.3.2 Error Suggestion: If an input error is 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 . How to meet 3.3.2

3.3.3 Error Prevention (Legal, Financial, Data): For forms that cause legal commitments or financial transactions to occur, that modify or delete user-controllable data in data storage systems, or that submit test responses, at least one of the following is true: How to meet 3.3.3

  1. Reversible: Transactions are reversible.

  2. Checked: Submitted data is checked for input errors before going on to the next step in the process.

  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the transaction.

3.3.4 Cues: Information or cues are provided when content requires user input How to meet 3.3.4

Level 3 Success Criteria for Guideline 3.3

3.3.5 Help: Context-sensitive help is available. How to meet 3.3.5

3.3.6 Error Prevention (All): For forms that require the user to submit information, at least one of the following is true: How to meet 3.3.6

  1. Reversible: Transactions are reversible.

  2. Checked: Submitted data is checked for input errors before going on to the next step in the process.

  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the transaction.

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 Support compatibility with current and future user agents, including assistive technologies Understanding Guideline 4.1

Level 1 Success Criteria for Guideline 4.1

4.1.1 Parsing: Content implemented using markup languages has elements with complete start and end tags, except as allowed by their specifications, and are nested according to their specifications. How to meet 4.1.1

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.

4.1.2 Name, Role, Value: For all user interface components, the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically determined and programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. How to meet 4.1.2

(No level 2 success criteria for Guideline 4.1)

(No level 3 success criteria for Guideline 4.1)

Conformance

This section is normative.

Conformance means that Web content satisfies the success criteria defined in this document. This section outlines the conformance scheme used throughout this document.

WCAG 2.0 success criteria are organized into three levels of conformance.

The word "levels" does not mean that some success criteria are more important than others. Each success criterion in WCAG 2.0 is essential to some users, and the levels build upon each other. However, even content that conforms at AAA (triple-A) may not be fully accessible to every person with a disability.

All WCAG 2.0 success criteria are written to be testable. While some can be tested by computer programs, others require human testers for part or all of the test. When people who understand how people with different types of disabilities use the Web test the same content using the same success criteria, the same results should be obtained with a high level of confidence.

For each success criterion, there is a list of techniques deemed by the Working Group to be sufficient to meet the requirement. For each sufficient technique, there is a test to determine whether the technique has been successfully implemented. If the test(s) for a "sufficient" technique (or combination of techniques) are passed, then that success criterion has been met. Passing all tests for all techniques is not necessary. It is also not necessary to meet a success criterion using one of the sufficient techniques. There may be other techniques which are not documented by the working group that would also meet the success criterion. When using such externally-provided techniques to meet WCAG 2.0 requirements, it is important that they be created by individuals or organizations who are knowledgeable about the requirements of WCAG 2.0 and the needs of people with disabilities.

In addition to the success criteria, which are all testable, there are a number of techniques that may enhance accessibility that are not testable or are not always appropriate. These are listed as "Advisory Techniques" in Understanding WCAG 2.0. Authors are encouraged to use these techniques where appropriate, although using them does not affect conformance. Many of the advisory techniques are particularly helpful for people with cognitive, language and learning disabilities, and use of these techniques will improve the accessibility of the content to people with these disabilities.

User agents, technology-independence and "relied upon" technologies

Technology independence

WCAG 2.0 defines accessibility guidelines (goals) and success criteria (testable criteria for conformance at different levels of accessibility). The guidelines and success criteria are described in a technology-independent way in order to allow conformance using any Web technology that is enabled for accessibility. WCAG 2.0, therefore, does not require or prohibit the use of any specific technology. It is possible to conform to WCAG 2.0 using both W3C and non-W3C technologies, as long as the technologies are supported by user agents, including assistive technologies.

Note: Although assistive technologies are a type of user agent, they depend upon support from host users agents. To reinforce the need to enable assistive technologies, several success criteria that require user agent support explicitly require support for assistive technologies, too.

Choosing Accessibility-supported Content Technologies (AsCT)

In choosing technologies (HTML, scripting, etc.) that will be used when creating content, authors must use "content" technologies that will work with user agents, including assistive technologies, that are available to the users of their content who have disabilities. These content technologies are referred to as accessibility-supported content technologies (AsCT).

Note: It is important that the host user agents themselves also work with assistive technologies in order for access to occur. Those host user agents are referred to as accessibility-supported host user agents in the discussion below.

To make it easier for authors who may not be familiar with assistive technologies, documented lists of accessibility-supported content technologies will be available from WAI and other sources. (See Documented lists of accessibility-supported content technologies in Understanding Conformance).

For authors who choose to create and validate their own list of accessibility-supported content technologies, both of the following must be true:

  1. The content technologies are supported by users' assistive technology (AT).

    This means that at least one of the following is true:

    1. The technology implements accessibility APIs that are supported by users' assistive technology; OR

    2. The technology has been tested for interoperability with users' assistive technology in the human language(s) of the content.

  2. The accessibility-supported host user agents for the technology are available to users.

    This means that at least one of the following is true:

    1. The technology is supported natively in widely-distributed host user agents that are also accessibility-supported. Some examples of such content technologies are: HTML, and CSS; OR

    2. The technology is supported in a widely-distributed plug-in that are also accessibility-supported; OR

    3. The content is available in a closed environment, such as a university or corporate network, where the host user agent required by the technology and used by the organization is also accessibility-supported: OR

    4. The host user agent(s) that support the technology are also accessibility-supported and available for download or purchase in a way that does not disadvantage people with disabilities.

    Note: Using a technology that isn't widely distributed isn't necessarily an accessibility issue as long as the process for getting an accessible plug-in or player for the technology does not disadvantage users with disabilities. For example, if you require users to download a plug-in in order to view content the plug-in would meet this option as long as the download can be completed with assistive technology, the plug-in is as easy to locate as any non-accessibility-supported version, the plug in costs no more than the non-accessibility-supported version, and the plug-in interoperates with assistive technology that users have.

Correct use of non accessibility-supported Content Technologies

Authors may use technologies that are not accessibility-supported content technologies provided that the authors do not rely upon those technologies for conveying any information or functionality. That is, the information and functionality provided through the non-qualifying technology is also provided using accessibility-supported content technologies. In addition, the presence of the non-AsCT must not block the ability of the users to access the content via the accessible technologies. Specifically, the following must be true:

  1. All content and functionality is available using only accessibility-supported content technologies.

  2. Other (non-accessibility-supported) content technologies do not interfere with (break or block access to) the conforming content

    1. when used with user agents that only support the accessibility-supported content technologies

    2. when used with user agents that support both the accessibility-supported content technologies and the non-AsCT

Conformance requirements

All conformance is based on Web page(s). Conformance claims provide a description of the URIs where the conforming pages can be found.

In order to conform to WCAG 2.0 all of the following conformance criteria must be true for each Web page:

1.) Conformance Levels: For each Web page in the conformance claim, all of the success criteria for the level claimed are met or the Web page satisfies conformance criterion 4. Understanding Conformance Criterion 1

2.) Minimum Conformance: At a minimum, all of the Level 1 success criteria have been met. Understanding Conformance Criterion 2

3.) Only AsCT: Only documented accessibility-supported content technologies are relied upon to meet WCAG 2.0 success criteria. Understanding Conformance Criterion 3

4.) Alternate Versions: If a Web page within the scope of a claim does not meet all of the required WCAG 2.0 success criteria at the level claimed, then a mechanism to obtain an alternate version that meets the success criteria can be derived from the nonconforming content or its URI, and that mechanism meets all success criteria at the level claimed. Understanding Conformance Criterion 4

Note 1: The alternate version does not need to be matched page for page with the original (e.g. the alternative to a page may consist of multiple pages).

Note 2: If multiple language versions can be negotiated, then conformant versions are required for each language offered.

5.) Full pages: Conformance is claimed for full Web page(s) only. Understanding Conformance Criterion 5

Note: Conformance can not be achieved if part of a Web page is excluded. For example, conformance can not apply to a set of pages, but exclude a part of the page or a particular type of content (for example, images or scripts) since doing so would allow exclusion of individual success criteria.

6.) Complete processes: If a Web page that is part of a process does not conform at some level, then no conformance claim is made at that level for any Web pages in that process. Understanding Conformance Criterion 6

Example: An online store has a series of pages that are used to select and purchase products. All pages in the series from start to finish (checkout) must conform in order to claim conformance for any page that is part of the sequence.

7.) Non-Interference: Non accessibility-supported content technologies (AsCT) can be used if the information and functionality provided through the non-AsCT is also provided using AsCT. In addition, the presence of the non-AsCT must not block the ability of the users to access the content via the AsCT. Specifically, the following must be true: Understanding Conformance Criterion 7

  1. No Keyboard Trap: If focus can be moved to non-AsCT content using a keyboard interface, then focus can be moved away from that content using only a keyboard interface, and the method for doing so is described before the content is encountered and in a way that meets all Level 1 success criteria.

  2. Three Flashes or Threshold: To minimize the risk of seizures due to photosensitivity, content does contain anything that flashes more than three times in any one second period, or the flash is below the general flash threshold and the red flash threshold (see Success Criterion 2.3.1).

Conformance notes

  1. Dynamic content: Web pages include a wide range of content including dynamic content and even immersive interactive environments that are found at a single URI.

  2. Non-conforming Content: It is recommended that even non-conforming content conform to the extent possible.

  3. Aggregated content: Sometimes, a Web page is assembled ("aggregated") from subcomponents from multiple sources. We encourage providers of such subcomponent pieces to follow the success criteria that apply to their content and report these to aggregators in order to help aggregators choose content that will enable them to conform to the guidelines. However, conformance is the responsibility of the aggregator and the conformance level is based upon the entire Web page after it is assembled. Since aggregated content may be compiled in realtime it may not be possible to check it each time it changes. Policies and periodic checks can be used instead.

  4. Automatic conformance to success criteria: If a success criterion relates to a feature, component or type of content that is not used in the content then that success criterion is satisfied automatically.

    Example: Success Criterion 1.2.1 is satisfied automatically for content which does not contain multimedia because all multimedia (which is none) does have captions. If multimedia is later added, then it would have to be captioned.

  5. Supplemental Information: A conforming alternative to part of a page's content is considered part of the page for the purpose of determining the page's conformance.

Conformance claims

Conformance claims apply to Web pages, and sets of Web pages.

Note: Web pages often take the form of a traditional HTML page, but can also take the form of a fully interactive and immersive environment.

Required components of a conformance claim

Conformance claims are not required. However, if a conformance claim is made, then the conformance claim must include the following assertions:

  1. The date of the claim

  2. The guidelines title/version: "Web Content Accessibility Guidelines 2.0"

  3. The URI of the guidelines: http://www.w3.org/TR/2006/REC-WCAG20-YYYYMMDD/

    Note: The correct date will replace "YYYYMMDD" when WCAG 2.0 is published as a W3C Recommendation.

  4. The conformance level satisfied: (Level A, AA or AAA)

  5. A list of the specific technologies relied upon by the content, or the documented list of accessibility-supported content technologies that includes all of the technologies relied upon.

    Note: This includes markup languages, style sheet languages, scripting/programming languages, image formats, and multimedia formats.

    1. "Relied upon" means that the content would not meet WCAG 2.0 at the claimed level if that technology is turned off or not supported.

    2. All of the technologies that are "relied upon" must be accessibility-supported content technologies.

  6. A description of the URIs that the claim is being made for.

    Note: Be sure to make it clear whether subdomains are included in the claim.

Optional components of a conformance claim

  1. A list of additional success criteria that have been satisfied beyond a standard claim, optimally provided in a form that consumers can use.

  2. A list of the specific technologies that are "used but not relied upon."

    • If a technology is "used but not relied upon," the content would still meet WCAG 2.0 at the stated conformance level even if that technology is turned off or not supported.

  3. A list of user agents, including assistive technologies, that the content has been tested on.

  4. Information about audience assumptions or target audience. This could include language, geographic information, or other pertinent information about the intended audience.

  5. Information about any additional steps taken that go beyond the success criteria to enhance accessibility.

  6. The list of specific technologies that are relied upon, in machine-readable metadata.

Note 1: If pages can not conform (for example, conformance test pages or example pages) they would not be included in the conformance claim.

Note 2: Refer to Examples of Conformance Claims in Understanding Conformance for examples.

Statement of partial conformance

Sometimes, Web pages are created that will later have additional content added to them. For example, an email program, a blog, or an article that allows users to add comments to the bottom. Another example would be a company or individual who compiles a page from multiple sources. Sometimes, the content from the other sources is automatically inserted into the page over time.

In both of these cases, it is not possible to know at the time of original posting what the content of the pages will be. Two options are available:

  1. A conformance claim is made based on best knowledge. If a page of this type is monitored and kept conformant (non-conforming content is immediately removed or made conforming) then a conformance claim can be made since, except for error periods, the page is conformant. No conformance claim should be made if it is not possible to monitor or correct non-conforming content.

  2. A "statement of partial conformance" is made. A statement that the page does not conform, but could conform if certain parts were removed can be made. The form of that statement would be, "This page would conform to WCAG 2.0 at level X if the following parts from uncontrolled sources were removed."

    1. This "statement of partial conformance" cannot be used for content that is under the author's control.

    2. The "following parts" of the page that would need to be removed would be described in terms that users can understand. (e.g. they can't be described as "all parts that we do not have control of" unless they are clearly marked as such.)

Content that conforms to WCAG 1.0

The Web Content Accessibility Guidelines Working Group is working to ensure that organizations and individuals who are currently using WCAG 1.0 (which remains stable and normative at this time) will be able to smoothly transition to WCAG 2.0. For more information about transitioning from WCAG 1.0 to 2.0, please refer to "Transitioning from WCAG 1.0 to 2.0".

Editorial Note: The transition document is being developed by the EOWG WCAG 2.0 Materials Support Task Force. It is not yet available.

Appendix A: Glossary

This section is normative.

abbreviation

shortened form of a word, phrase, or name

Note: Includes initialisms and acronyms.

acronym

abbreviated form made from the initial letters or parts of other words (in a name or phrase) which may be pronounced as a word

Example: NOAA is an acronym made from the initial letters of the National Oceanic and Atmospheric Administration in the United States.

activity where timing is essential

activity where timing is part of the design of the activity and removal of the time dependency would change the functionality of the content

alternate version

version that provides all of the same information and functionality in the same human language and is as up to date as the non-conformant content

Application Programming Interface (API)

definitions of how communication may take place between applications

Note 1: Implementing APIs that are independent of a particular operating environment (as are the W3C DOM Level 2 specifications) may reduce implementation costs for multi-platform user agents and promote the development of multi-platform assistive technologies. Implementing conventional APIs for a particular operating environment may reduce implementation costs for assistive technology developers who wish to interoperate with more than one piece of software running on that operating environment.

Note 2: A "device API" defines how communication may take place with an input or output device such as a keyboard, mouse, or video card.

Note 3: In this document, an "input/output API" defines how applications or devices communicate with a user agent. As used in this document, input and output APIs include, but are not limited to, device APIs. Input and output APIs also include more abstract communication interfaces than those specified by device APIs. A "conventional input/output API" is one that is expected to be implemented by software running on a particular operating environment. For example, the conventional input APIs of the user agent are for the mouse and keyboard. For touch screen devices or mobile devices, conventional input APIs may include stylus, buttons, and voice. The graphical display and sound card are considered conventional output devices for a graphical desktop computer environment, and each has an associated API.

Note 4: This definition is based on User Agent Accessibility Guidelines 1.0 Glossary.

ASCII art

picture created by a spatial arrangement of characters or glyphs (typically from the 95 printable characters defined by ASCII).

Assistive technology (as used in this document )

a user agent that both:

  1. provides services beyond those offered by the host user agents to meet the requirements of users with disabilities. Such services include alternative renderings (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation mechanisms, and content transformations (e.g., to make tables more accessible), and

  2. relies on services (such as retrieving Web content and parsing markup) provided by one or more other "host" user agents. Assistive technologies communicate data and messages with host user agents by using and monitoring APIs

Note 1: In this definition, the host user agents are user agents in the general sense of the term. That is, any software that retrieves and renders Web content for users. The host user agent may provide important services to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles.

Note 2: Host user agents may also provide services directly that meet the requirements of users with disabilities.

Note 3: This definition is based on User Agent Accessibility Guidelines 1.0 Glossary.

Example: Examples of assistive technologies that are important in the context of this document include the following:

  • screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc in order improve the visual readability of rendered text and images;

  • screen readers, which are used by people who are blind to read textual information through synthesized speech or braille;

  • text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech;

  • voice recognition software, which may be used by people who have some physical disabilities;

  • alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard;

  • alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations.

audio description

narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone

Note 1: Audio description of video provides information about actions, characters, scene changes, on-screen text, and other visual content.

Note 2: In standard audio description, narration is added during existing pauses in dialogue. (See also extended audio description.)

blink

turn on and off between 0.5 and 3 times per second

Note: The slower blink is in contrast with flashing, which refers to rapid changes in brightness which can cause seizures. See general flash threshold and red flash threshold.

body text

the base font used for text in a paragraph

captions

text presented and synchronized with multimedia to provide not only the speech, but also non-speech information conveyed through sound, including meaningful sound effects and identification of speakers

Note: In some countries, the term "subtitle" is used to refer to dialogue only and "captions" is used as the term for dialogue plus sounds and speaker identification. In other countries, subtitle (or its translation) is used to refer to both.

changes of context

change of :

  1. user agent;

  2. viewport;

  3. focus;

  4. content that changes the meaning of the Web page.

Note: A change of content is not always a change of context. Small changes in content, such as an expanding outline or dynamic menu, do not change the context.

conformance

satisfying all the requirements of a given standard, guideline or specification

content (Web content)

information and sensory experience to be communicated to the user by means of a user agent, as well as code or markup that define the structure, presentation, and interactions associated with those elements

Note:

context-sensitive help

help text that provides information related to the function currently being performed

contrast ratio

(L1 + 0.05) / (L2 + 0.05), where L1 is the relative luminance of the lighter of the foreground or background colors, and L2 is the relative luminance of the darker of the foreground or background colors.

Note 1: The relative luminance of an sRGB color is defined as 0.2126 * R + 0.7152 * G + 0.0722 * B where R, G and B are defined as:

  • if RsRGB <= 0.03928 then R = RsRGB/12.92 else R = ((RsRGB+0.055)/1.055) ^ 2.4

  • if GsRGB <= 0.03928 then G = GsRGB/12.92 else G = ((GsRGB+0.055)/1.055) ^ 2.4

  • if BsRGB <= 0.03928 then B = BsRGB/12.92 else B = ((BsRGB+0.055)/1.055) ^ 2.4

The "^" character is the exponentiation operator. Refer to [sRGB] and [IEC-4WD] for conversion from nonlinear to linear RGB values.

Note 2: Relative luminance values can range from 0 (black) to 1 (white), and contrast ratios can range from 1 to 21 (commonly written 1:1 to 21:1).

Note 3: For dithered colors, use average values of the colors used (average R, average G, and average B).

Note 4: Text can be evaluated with anti-aliasing turned off.

Note 5: For text displayed over gradients and background images, authors should ensure that sufficient contrast exists for each character in the content.

Note 6: A MathML version of the contrast ratio definition is available.

emergency

a sudden, unexpected situation or occurrence that requires immediate action to preserve health, safety, or property

extended audio description

audio description that is added to an audiovisual presentation by pausing the video so that there is time to add additional description

Note: This technique is only used when the sense of the video would be lost without the additional audio description.

full text alternative for multimedia including any interaction

document including correctly sequenced descriptions of all visual settings, actions, and non-speech sounds combined with descriptive transcripts of all dialogue and a means of achieving any outcomes that are achieved using interaction during the multimedia

Note: A screenplay used to create the multimedia content would meet this definition only if it was corrected to accurately represent the final multimedia after editing.

functionality

processes and outcomes achievable through user action

general flash threshold
  • A sequence of flashes or rapidly changing image sequences where all four of the following occur:

    1. there are more than three flashes within any one-second period; and

    2. the flashing is below 50 Hz; and

    3. the brightness of the darker image is below .80 of full scale white brightness; and

    4. the combined area of flashes occurring concurrently and contiguously occupies more than a total of .006 steradians (or one quarter of any 10 degree visual field on the screen ).

Note 1: For the general flash threshold, a flash is defined as a pair of opposing changes in brightness of 10% or more of full scale white brightness.

Note 2: Brightness is calculated as 0.2126 * ((R / FS) ^ 2.2) + 0.7152 * ((G / FS) ^ 2.2) + 0.0722 * ((B / FS) ^ 2.2). R, G, and B are the red, green, and blue RGB values of the color; FS is the maximum possible full scale RGB value for R, G, and B (255 for eight bit color channels); and the "^" character is the exponentiation operator.

Note 3: An "opposing change" is an increase followed by a decrease, or a decrease followed by an increase.

Note 4: For general Web content, using a 341 x 256 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 x 768 pixels will provide a good estimate of a 10 degree visual field of standard screen sizes and viewing distances.

human language

language that is spoken, written or signed (visually or tactilely) by humans to communicate with one another

Note: See also sign language.

idiom

phrase whose meaning cannot be deduced from the meaning of the individual words and the specific words cannot be changed without losing the meaning

Example 1: In English, "kicking the bucket" means "dying," but the phrase cannot be changed to "kicking the buckets" or "kicking the tub" or "booting the bucket" or "knocking over the bucket" without losing its meaning.

Example 2: In English, "spilling the beans" means "revealing a secret." However, "knocking over the beans" or "spilling the vegetables" does not mean the same thing.

Example 3: In Japanese, the phrase "さじを投げる " literally translates into "he throws a spoon," but it means that there is nothing he can do and finally he gives up.

Example 4: In Dutch, "Hij ging met de kippen op stok" literally translates into "He went to roost with the chickens," but it means that he went to bed early.

information that is conveyed by color differences

information presented in a manner that depends entirely on the ability to perceive color

informative

for information purposes and not required for conformance

Note: Content required for conformance is referred to as "normative."

initialism

shortened form of a name or phrase made from the initial letters of words or syllables contained in that name or phrase

Note: Not defined in all languages.

Example 1: SNCF is a French initialism that contains the initial letters of the Sociétè Nationale des Chemins de Fer, the French national railroad.

Example 2: ESP is an initialism for extrasensory perception.

input error

information provided by the user that is not accepted

Note: This includes:

  1. Information that is required by the Web page but omitted by the user

  2. Information that is provided by the user but that falls outside the required data format or values

jargon

words used in a particular way by people in a particular field

Example: The word StickyKeys is jargon from the field of assistive technology/accessibility.

keyboard interface

interface used by software to obtain keystroke input

Note 1: Allows users to provide keystroke input to programs even if the native technology does not contain a keyboard.

Example: A touch screen PDA has a keyboard interface built into its operating system as well as a connector for external keyboards. Applications on the PDA can use the interface to obtain keyboard input either from an external keyboard or from other applications that provide simulated keyboard output, such as handwriting interpreters or speech-to-text applications with "keyboard emulation" functionality.

Note 2: Operation of the application (or parts of the application) through a keyboard-operated mouse emulator, such as MouseKeys, does not qualify as operation through a keyboard interface because operation of the program is through its pointing device interface, not through its keyboard interface.

label

text or other component with a text alternative that is presented to a user to identify a component within Web content

Note: See also name.

legal committments

transactions where the person incurs a legally binding obligation or benefit

Example: A marriage license, a stock trade (financial and legal), a will, a loan, adoption, signing up for the army, a contract of any type, etc.

live audio-only

A time-based live presentation that contains only audio (no video and no interaction)

live video-only

A time-based live presentation that contains only video (no audio and no interaction)

lower secondary education level

the two or three year period of education that begins after completion of six years of school and ends nine years after the beginning of primary education.

Note: This definition is based on [UNESCO].

mechanism

process or technique for achieving a result

Note 1: The mechanism may be explicitly provided in the content, or may be relied on to be provided by either the platform or by user agents, including assistive technologies.

Note 2: The mechanism must meet all success criteria for the conformance level claimed.

multimedia

audio or video synchronized with another format for presenting information and/or with time-based interactive components

multimedia alternatives to text

multimedia that presents no more information than is already presented in text (directly or via text alternatives)

Note: Multimedia alternatives to text are provided for those who benefit from alternate representations of text.

must be presented in non-text format

would be invalid if presented in text

Example: Color blindness test, hearing test, vision exercise, spelling test.

name

text by which software can identify a component within Web content to the user

Note: The name may be hidden and only exposed by assistive technology, whereas a label is presented even without assistive technology. In many (but not all) cases, the label is a display of the name.

navigated sequentially

navigated in the order defined for advancing focus from one element to the next with the keyboard

non-text content

content that is not represented by a Unicode character or sequence of Unicode characters when rendered in a user agent according to the formal specification of the content type

Note: This includes ASCII Art, which is a pattern of characters and leetspeak, which is character substitution. .

normative

required for conformance

Note 1: One may conform in a variety of well-defined ways to this document.

Note 2: Content identified as "informative" or "non-normative" is never required for conformance.

paused

stopped by user request and not restarted until requested by user

presentation

rendering of the content in a form to be perceived by users

primary education level

six year time period that begins between the ages of five and seven, possibly without any previous education

Note: This definition is based on [UNESCO].

process

series of user actions where each action is required in order to complete an activity

Example 1: A series of Web pages on a shopping site requires users to view alternative products and prices, select products, submit an order, provide shipping information and provide payment information.

Example 2: An account registration page requires successful completion of a Turing test before the registration form can be accessed.

programmatically determined

determined by software from author-supplied data provided in a way that different user agents, including assistive technologies, can extract and present this information to users in different modalities

Example: Determined in a mark-up language from elements and attributes that are accessed directly by commonly available assistive technology.

Example: Determined from technology-specific data structures in a non-mark-up language and exposed to assistive technology via an accessibility API that is supported by commonly available assitive technology.

programmatically determined link context
  1. Additional information that can be programmatically determined from relationships with a link; and

  2. can be extracted, combined with the link text, and presented to users in different modalities.

Example 1: Screen readers provide commands to read the current sentence when focus is on a link.

Example 2: Examples of information that can be extracted, combined with link text, and presented to users in different modalities include text that is in the same sentence, paragraph, list, or table cell as the link or in a table header cell that is associated with the table cell that contains the link.

programmatically set

set by software using methods that are supported by user agents, including assistive technologies

pure decoration

serving only an aesthetic purpose, providing no information, and having no functionality.

real-time event

event that a) occurs at the same time as the viewing, b) is not completely generated by the content, and c) is not pre-recorded

Example 1: A Webcast of a live performance (occurs at the same time as the viewing and is not pre-recorded).

Example 2: An on-line auction with people bidding (occurs at the same time as the viewing).

Example 3: Live humans interacting in a fantasy world using avatars (is not completely generated by the content and occurs at the same time as the viewing) .

red flash threshold
  • transition to or from a saturated red where all three of the following occur:

    1. there are more than three flashes within any one-second period; and

    2. the flashing is below 50 Hz; and

    3. the combined area of flashing occurring concurrently and contiguously occupies more than a total of .006 steradians (or one quarter of any 10 degree visual field on the screen).

Note: For general Web content, using a 341 x 256 pixel rectangle anywhere on the displayed screen area when the content is viewed at 1024 x 768 pixels will provide a good estimate of a 10 degree visual field of standard screen sizes and viewing distances.

relationships

meaningful associations between distinct pieces of content

role

text or a number by which software can identify the function of a component within Web content

Example: A number that indicates whether an image functions as a hyperlink, command button, or check box.

same functionality

same result when used

Example: A submit "search" button on one Web page and a "find" button on another Web page may both have a field to enter a term and list topics in the Web site related to the term submitted. In this case, they would have the same functionality but would not be labeled consistently.

same relative order

same position relative to other items

Note: Items are considered to be in the same relative order even if other items are inserted or removed from the original order. For example, expanding navigation menus may insert an additional level of detail or a secondary navigation section may be inserted into the reading order.

set of Web pages

collection of Web pages that have a specific relationship to each other and that are created as a body of work by an author, group or organization

Note: Different language versions would be considered different bodies of work.

Example: A set of Web pages that make up a report, a test, an exercise, a catalog, or an application.

sign language

a visual language using combinations of movements of the hands and arms, facial expressions, and body positions to convey meaning

sign language interpretation

translation of one language, generally a spoken language, into a sign language

Note: True sign languages are independent languages that are unrelated to the spoken language(s) of the same country or region.

specific sensory experience

a sensory experience that is not purely decorative and does not primarily convey important information or perform a function

Example: Examples include a performance of a flute solo, works of visual art etc.

stem width

the width of the dominant stem of the font

Note: This is usually the width of the vertical stroke of the letter "T" in a Latin font (e.g. English).

structure
  1. The way the parts of a Web page are organized in relation to each other; and

  2. The way a collection of Web pages is organized

supplemental content

additional content that illustrates or clarifies the primary content

Example 1: An audio version of a Web page.

Example 2: An illustration of a complex process.

Example 3: A paragraph describing the major outcomes and recommendations made in a research study.

technology

markup language, programming language, style sheet, data format, or API

text

sequence of characters

Note 1: This definition does not place requirements on the specific encoding of characters. For advice about appropriate character encodings, refer to [I18N-CHAR-ENC].

Note 2: Characters are those included in the Unicode/ISO/IEC 106464 repertoire.

text alternative

programmatically determined text that is used in place of non-text content, or text that is used in addition to non-text content and referred to from the programmatically determined text

time-dependent analog input

input whose result is different depending on the rate of the analog movement (such as when line width varies with pen speed or pressure)

Note: Most actions carried out by a pointing device can also be done from the keyboard (for example, clicking, selecting, moving, sizing). However, there is a small class of input that is done with a pointing device that cannot be done from the keyboard in any known fashion. This type of input can be best characterized by the fact that the outcome can only be achieved by moving the pointer in a smooth fashion at a certain rate. For example, in a watercolor program stroke width and transparency may depend on the rate of movement (and/or pressure) of a "brush." Another example would be a real-time helicopter flight simulator.

Unicode

universal character set that defines all the characters needed for writing the majority of living languages in use on computers

Note: For more information, refer to [UNICODE] or [I18N-CHAR-ENC].

used in an unusual or restricted way

words used in such a way that users must know exactly which definition to apply in order to understand the content correctly

Example: The term "gig" means something different if it occurs in a discussion of music concerts than it does in article about computer hard drive space, but the appropriate definition can be determined from context. By contrast, the word "text" is used in a very specific way in WCAG 2.0, so a definition is supplied in the glossary.

user agent

any software that retrieves and renders Web content for users

Example: Web browsers, media players, plug-ins, and other programs — including assistive technologies — that help in retrieving, rendering, and interacting with Web content.

user-controllable

data that is intended to be accessed by users

Note: This does not refer such things as internet logs and search engine monitoring data.

Example: Name and address fields for a user’s account.

video

the technology of moving pictures or images

Note: Video can be made up of animated or photographic images, or both.

viewport

object in which the user agent renders content

Note 1: The user agent renders content through one or more viewports. Viewports include windows, frames, loudspeakers, and virtual magnifying glasses. A viewport may contain another viewport (e.g., nested frames). User agent user interface controls such as prompts, menus, and alerts are not viewports.

Note 2: This definition is based on User Agent Accessibility Guidelines 1.0 Glossary.

Web page

a resource that is referenced by a URI and is not embedded in another resource, plus any other resources that are used in the rendering or intended to be rendered together with it

Note: Although any "other resources" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other.

Example 1: A movie-like interactive shopping environment where the user visually moves about a store dragging products off of the shelves around them into a visual shopping cart in front of them. Clicking on a product causes it to be demonstrated with a specification sheet alongside.

Example 2: A Web resource including all embedded images and media.

Appendix B: Acknowledgments

This section is informative.

This publication has been funded in part with Federal funds from the U.S. Department of Education under contract number ED05CO0039. The content of this publication does not necessarily reflect the views or policies of the U.S. Department of Education, nor does mention of trade names, commercial products, or organizations imply endorsement by the U.S. Government.

Additional information about participation in the Web Content Accessibility Guidelines Working Group (WCAG WG) can be found on the Working Group home page.

Participants active in the WCAG WG at the time of publication

  • Bruce Bailey (US Access-Board)

  • Frederick Boland (NIST)

  • Judy Brewer (W3C/MIT)

  • Ben Caldwell (Trace R&D Center, University of Wisconsin-Madison)

  • Sofia Celic (The National Information and Library Service)

  • Wendy Chisholm (W3C)

  • Michael Cooper (Watchfire)

  • Roberto Ellero (International Webmasters Association / HTML Writers Guild)

  • Bengt Farre (Femtio Procent Data)

  • Becky Gibson (IBM)

  • Kerstin Goldsmith (Oracle)

  • Loretta Guarino Reid (Adobe)

  • Katie Haritos-Shea

  • Gez Lemon (International Webmasters Association / HTML Writers Guild)

  • Alex Li (SAP AG)

  • Yvette Hoitink (Heritas)

  • Luca Mascaro (International Webmasters Association / HTML Writers Guild)

  • Sorcha Moore (Segala)

  • David MacDonald (E-Ramp Inc.)

  • Roberto Scano (International Webmasters Association / HTML Writers Guild)

  • Cynthia Shelley (Microsoft)

  • John Slatin (Accessibility Institute, University of Texas at Austin)

  • Andi Snow-Weaver (IBM)

  • Christophe Strobbe (DoArch, K.U.Leuven)

  • Makoto Ueki (Infoaxia)

  • Gregg Vanderheiden (Trace R&D Center, University of Wisconsin)

Other previously active WCAG WG participants and other contributors to WCAG 2.0

Jenae Andershonis, Avi Arditti, Sandy Bartell, Kynn Bartlett, Marco Bertoni, Harvey Bingham, Paul Bohman, Dick Brown, Doyle Burnett, Roberto Castaldo, Jonathan Chetwynd, David M Clark, Joe Clark, Tom Croucher, Nir Dagan, Daniel Dardailler, Geoff Deering, Don Evans, Alan J. Flavell, Al Gilman, Jon Gunderson, Emmanuelle Gutiérrez y Restrepo, Donovan Hipke, Bjoern Hoehrmann, Ian Jacobs, Phill Jenkins, Leonard R. Kasday, Andrew Kirkpatrick, Marja-Riitta Koivunen, Scott Luebking, Tim Lacy, Jim Ley, William Loughborough, Greg Lowney ,Mathew J Mirabella, Charles McCathieNevile , Matt May, Marti McCuller, Charles F. Munat, Robert Neff, Bruno von Niman, Tim Noonan, Sebastiano Nutarelli, Graham Oliver, Sean B. Palmer, Sailesh Panchang, Anne Pemberton, David Poehlman, Adam Victor Reed, Chris Ridpath, Lee Roberts, Gregory J. Rosmaita, Lisa Seeman, Justin Thorp, Gian Sampson-Wild, Joel Sanda, Jim Thatcher, Takayuki Watanabe, Jason White.

Appendix C: How to refer to WCAG 2.0 from other documents

This section is informative.

Information references

When referencing WCAG 2.0 in an informational fashion, the following format can be used.

Web Content Accessibility Guidelines 2.0, W3C World Wide Web Consortium Recommendation XX Month Year (http://www.w3.org/TR/200X/REC-WCAG20-YYYYMMDD/, Latest version at http://www.w3.org/TR/WCAG20/)

When referring to WCAG 2.0 from another standard with a "should" statement

When referencing WCAG 2.0 from within a should statement in a standard (or advisory statement in a regulation), then the full WCAG 2.0 should be referenced. This would mean that all three levels of WCAG 2.0 should be considered but that none are required. The format for referencing WCAG 2.0 from a "should" statement therefore, is:

Web Content Accessibility Guidelines 2.0, W3C World Wide Web Consortium Recommendation XX Month Year. (http://www.w3.org/TR/200X/REC-WCAG20-YYYYMMDD/)

When referring to WCAG 2.0 from another standard with a "shall" statement

When citing WCAG 2.0 as part of a requirement (e.g., a shall statement in a standard or regulation), the reference must include the specific parts of WCAG 2.0 that are intended to be required . When referencing WCAG 2.0 in this manner, the following rules apply:

  1. Conformance at any level of WCAG 2.0 requires that all of the Level 1 success criteria be met. References to WCAG 2.0 conformance can not be for any subset of Level 1.

  2. Beyond Level 1, a "shall" reference may include any subset of provisions in Levels 2 and 3. That is, it is possible to require "all of Level 1 and [some specific list of success criteria in Level 2 and Level 3]" be met.

  3. If Double-A conformance to WCAG 2.0 is specified, then all Level 1 and all Level 2 success criteria must be met.

  4. If Triple-A conformance to WCAG 2.0 is specified, then all Level 1, all Level 2, and all Level 3 success criteria must be met.

Examples

To cite only the Level 1 success criteria (Single-A conformance):

Web Content Accessibility Guidelines 2.0, W3C World Wide Web Consortium Recommendation XX Month Year, Level 1 success criteria. (http://www.w3.org/TR/200X/REC-WCAG20-YYYYMMDD/)

To cite the Levels 1 and 2 success criteria (Double-A conformance):

Web Content Accessibility Guidelines 2.0, W3C World Wide Web Consortium Recommendation XX Month Year, Level 1 & Level 2 success criteria. (http://www.w3.org/TR/200X/REC-WCAG20-YYYYMMDD/)

To cite Level 1 success criteria and selected success criteria from Level 2 and Level 3:

Web Content Accessibility Guidelines 2.0, W3C World Wide Web Consortium Recommendation XX Month Year, Level 1 success criteria plus Success Criteria 1.x.x, 2.y.y, … 3.z.z. (http://www.w3.org/TR/200X/REC-WCAG20-YYYYMMDD/)

Note: It is not recommended that Triple-A conformance ever be required for entire sites as a general policy because it is not possible to satisfy all Level 3 success criteria for some content.

Example of use of a WCAG reference in a "shall" statement.

All Web content on publicly available Web sites shall conform to Web Content Accessibility Guidelines 2.0, W3C World Wide Web Consortium Recommendation XX Month Year, Level 1 success criteria plus Success Criteria 1.3.3, 1.4.2, 2.4.2-6, 3.1.6 (http://www.w3.org/TR/200X/REC-WCAG20-YYYYMMDD/)

Referring to content from WCAG support documents

Techniques, which are listed in Understanding WCAG 2.0 and described in other supporting documents, are not part of the normative WCAG 2.0 Recommendation and should not be cited using the citation for the WCAG 2.0 Recommendation itself. References to techniques in support documents should be cited separately.

Techniques can be cited based on the individual Technique document or on the master WCAG 2.0 Techniques document. For example, the technique "Using alt attributes on img elements" could be cited as

"Using alt attributes on img elements", W3C World Wide Web Consortium Note. (URL: http://www.w3.org/TR/NOTE-WCAG20-TECHS/UsingAltOnImg.html/)

or

W3C World Wide Web Consortium (200x): WCAG2.0 HTML Techniques (URL: http://www.w3.org/TR/NOTE-WCAG20-TECHS/HTMLTechs.html)

Note: Techniques are not designed to be referenced as "required" from any standard or regulation.

Appendix D: References

This section is informative.

I18N-CHAR-ENC
"Tutorial: Character sets & encodings in XHTML, HTML and CSS," R. Ishida, ed., This tutorial is available at http://www.w3.org/International/tutorials/tutorial-char-enc/.
IEC-4WD
IEC/4WD 61966-2-1: Colour Measurement and Management in Multimedia Systems and Equipment - Part 2.1: Default Colour Space - sRGB. May 5, 1998.
sRGB
"A Standard Default Color Space for the Internet - sRGB," M. Stokes, M. Anderson, S. Chandrasekar, R. Motta, eds., Version 1.10, November 5, 1996. A copy of this paper is available at http://www.w3.org/Graphics/Color/sRGB.html.
UAAG10
"User Agent Accessibility Guidelines 1.0," I. Jacobs, J. Gunderson, E. Hansen, eds., W3C Recommendation 17 December 2002. The latest version of UAAG 1.0 is available at http://www.w3.org/TR/UAAG10/
UNESCO
International Standard Classification of Education, 1997. A copy of the standard is available at http://www.unesco.org/education/information/nfsunesco/doc/isced_1997.htm.
UNICODE
The Unicode Consortium. The Unicode Standard, Version 4.0.1, defined by: The Unicode Standard, Version 4.0 (Reading, MA, Addison-Wesley, 2003. ISBN 0-321-18578-1), as amended by Unicode 4.0.1 (http://www.unicode.org/versions/Unicode4.0.1/).