This document is a draft, and is designed to show changes from a previous version. It is presently showing added text,changed text,deleted text,[start]/[end] markers,and Issue Numbers.

Hide All Edits   |   Toggle Deletions  |   Toggle Issue Numbers   |   Toggle [start]/[end] Markers   |   Show All Edits

Changes are displayed as follows:

[contents]

W3C

Web Content Accessibility Guidelines 2.0

W3C Working Draft 11 December 2007 -- Review Version

This version:
http://www.w3.org/TR/2007/WD-WCAG20-20071211/
Latest version:
http://www.w3.org/TR/WCAG20/
Previous version:
http://www.w3.org/TR/2007/WD-WCAG20-20070517/
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 [begin add]often[end add] make your Web content more [begin change]usable[end change] to [begin change]users in general[end change]. [begin delete]These guidelines often make Web content more generally usable.[end delete]

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 [WCAG10], published as a W3C Recommendation May 1999.

Status of this Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

This second Last Call Working Draft from the Web Content Accessibility Guidelines Working Group integrates changes to the "Web Content Accessibility Guidelines 2.0" (WCAG 2.0) in response to comments received on the 17 May 2007 Working Draft. That draft, in turn, incorporated responses to comments received on the 27 April 2006 Last Call Working Draft. The Working Group received 1,500 comments on those two drafts, which comprise a significant community contribution to the guidelines, and believes the draft is now mature enough to re-issue a second Last Call for comments and proceed to the next stages.

Much of the Working Group's response to these comments took the form of additional clarifications and techniques in the associated non-normative documents, Understanding WCAG 2.0 and Techniques for WCAG 2.0. Although those documents do not have the formal status that WCAG 2.0 itself has, they provide information essential to understanding and implementing WCAG. The Working Group requests that reviewers consider the information in those documents in context of any review of WCAG 2.0.

Publication as a Last Call Working Draft indicates that the WCAG WG believes it has addressed all substantive issues and that the document is stable. The first public Working Draft of WCAG 2.0 was published 25 January 2001. Since then, the WCAG WG has published eleven Working Drafts, addressed more than 2,500 issues, and developed a variety of support information for the guidelines. See How WAI Develops Accessibility Guidelines through the W3C Process for more background on document maturity levels.

A summary of changes to the previous draft based on comments received and responses made is available. Also available is a version of WCAG 2.0 with changes marked inline .

The Working Group seeks feedback on the following points for this draft:

Comments on this working draft are due on or before 1 February 2008. The Working Group requests that comments be made using the provided online or downloadable comment form. If this is not possible, comments can also be sent to public-comments-wcag20@w3.org. The archives for the public comments list are publicly available. Archives of the WCAG WG mailing list discussions are also publicly available.

This document has been produced as part of the W3C Web Accessibility Initiative (WAI). The goals of the WCAG Working Group are discussed in the WCAG Working Group charter. The WCAG Working Group is part of the WAI Technical Activity.

Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.


Table of Contents

Appendices


Introduction

This section is informative.

[begin add]

Web Content Accessibility Guidelines (WCAG) 2.0 defines how to make Web content more accessible to people with disabilities[begin delete], and older people with changing abilities due to aging[end delete]. Accessibility involves a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. [begin add]These guidelines also often make content more usable in general. [2011] [end add] Although these guidelines cover a wide range of issues, they are not able to address the needs of people with all types, degrees and combinations of disabilities.[begin add] This document also makes Web content more usable by older individuals with changing abilities due to aging. [end add]

[end add]
[begin add]

WCAG 2.0 is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a shared standard for Web content accessibility that meets the needs of individuals, organizations, and governments internationally. WCAG 2.0 builds on WCAG 1.0 [WCAG10] and is designed to apply broadly to different Web technologies now and in the future, and to be testable with a combination of automated testing and human evaluation. For an introduction to WCAG, see the Web Content Accessibility Guidelines (WCAG) Overview.

[end add]
[begin add]

Web accessibility depends not only on accessible content, but also on accessible Web browsers and other user agents. Authoring tools also have an important role in Web accessibility. For an overview of how these components of Web development and interaction work together, see:

[end add]
[begin delete]

This is a Working Draft of the Web Content Accessibility Guidelines (WCAG) version 2.0. WCAG is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of providing a single shared standard for Web accessibility that meets the needs of individuals, organizations, and governments internationally.

[end delete]
[begin delete]

WCAG 2.0 builds upon the work of WCAG 1.0 [WCAG10] with provisions that are more testable and that extend to a broader range of technologies including many that are new and evolving. WCAG 2.0 has been created to be technology independent. That is, the guidelines and Success Criteria in WCAG 2.0 can be applied across a wide range of existing and emerging Web technologies. Rather than specifying what technologies to use, WCAG 2.0 lays out general guidelines for using technologies along with specific testable Success Criteria for guiding and evaluating the use of the technologies.

[end delete]
[begin delete]

WCAG 2.0 provides requirements for making content (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 disabilities, and others. Because many people develop vision, hearing, cognitive or motion impairments as they age, following these guidelines will make your Web content more usable by many older users. These guidelines also often make Web content more accessible to the general public as well. However, even content that completely conforms to WCAG may not be fully accessible to every person with a disability.

[end delete]
[begin delete]

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.

[end delete]
[begin delete]

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.

[end delete]
[begin delete]

Components of Web Accessibility

It is important to note that Web content is just one aspect of accessibility. Just as important as accessible Web content is the availability of accessible browsers (and other user agents) that can adapt and present the content in the best form for the user. Accessible Web technologies and accessible tools for creating Web content are also important. For an overview of the different components of accessibility and how they work together see:

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

  • User Agent Accessibility Guidelines (UAAG) Overview - Introduces guidelines on the design of accessible Browsers and other user agents.

  • Authoring Tool Accessibility Guidelines (ATAG) Overview - Introduces guidelines on the design of authoring and evaluation tools.

[end delete]
[begin add]

WCAG 2.0 Layers of Guidance

The individuals and organizations that use WCAG vary widely and include Webmasters, policy makers, purchasing agents, teachers, and students. In order to meet the varying needs several layers of guidance are provided including overall principles, general guidelines, testable Success Criteria and a rich collection of sufficient techniques, advisory techniques and documented failures with examples, resource links and code.

  • Principles - At the top are four principles that provide the foundation for Web accessibility: perceivable, operable, understandable, and robust. See also Understanding the Four Principles of Accessibility.

  • Guidelines - Under the principles are guidelines. The 12 guidelines provide the basic goals that authors should work toward in order to make content more accessible to users with different disabilities. These guidelines are not testable but provide the framework and overall objectives to help authors understand the Success Criteria and better implement the techniques.

  • Success Criteria - For each guideline, testable Success Criteria are provided to allow WCAG 2.0 to be used [begin delete]in design specification, purchasing, regulation, contractual agreements, etc. [end delete]where requirements and [begin change]conformance testing[end change] are necessary[begin add] such as in design specification, purchasing, regulation, and contractual agreements[end add]. In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, AAA (highest). (Additional information on WCAG levels can be found in Understanding Levels of Conformance.)

  • Sufficient and Advisory Techniques - For each of the guidelines and Success Criteria in the WCAG 2.0 document itself, the working group has also documented a wide variety of techniques. The techniques [begin add]are informative and [end add]fall into two categories: those that are sufficient for meeting the Success Criteria and those that are “advisory" and go beyond what is required by the individual Success Criteria and allow authors to better address the guidelines. See also Sufficient and Advisory Techniques in Understanding WCAG 2.0.

All of these layers of guidance (guidelines, Success Criteria, and sufficient and advisory techniques) work together to provide guidance on how to make content more accessible. Authors are encouraged to view and apply all layers that they are able to, including the advisory techniques, in order to best address the needs of the widest possible range of users.

Note that even content that conforms at the highest level (AAA) will not be accessible to individuals with all types, degrees, or combinations of disability particularly in the cognitive language and learning areas. Authors are encouraged to consider the full range of techniques, including the advisory techniques, as well as to seek relevant advice about current best practice to ensure that Web content is accessible, as far as possible, to this community. [2004] Metadata may assist users in finding content most suitable for their needs. [1957]

[end add]

WCAG 2.0 Supporting Documents

[begin add]

The WCAG 2.0 document [begin delete]itself[end delete] is designed to meet the needs of those who need a stable, referenceable technical standard. [begin delete]For different needs and different types of users, W3C WAI provides additional material. These include:[end delete] [begin add]Other documents, called supporting documents, are based on the WCAG 2.0 document and address other important purposes. Supporting document include:[end add]

[end add]
[begin delete]

WCAG 2.0 itself is a technical standard designed primarily for Web developers and designers, authoring tool developers, evaluation tool developers, and others who need a technical standard for Web accessibility. Due to the technical and technology-independent nature of the guidelines and Success Criteria, and because they say what needs to be done rather than how to do it, it may sometimes be difficult to use the guidelines or Success Criteria for specific advice for a particular technology (e.g. HTML, XHTML, JavaScript etc).

[end delete]
[begin delete]

In order to provide more concrete examples as well as specific techniques for meeting each of the Success Criteria, three support documents or collections have been developed by the working group to accompany the guidelines. These documents provide very specific guidance that can be used directly to meet the WCAG 2.0 guidelines.

[end delete]
[begin delete]

The overall set of documents from the working group consists of:

[end delete]
  1. [begin delete]

    The WCAG 2.0 Guidelines - (this document) - This document provides the guidelines, Success Criteria, conformance specifications as well as the definitions of terms used in the guidelines. The actual guidelines (including Success Criteria) are only 9 pages long.

    [end delete]
  2. [begin change]

    WCAG 2.0 Quick Reference - A concise list that includes all of the guidelines, Success Criteria, and techniques for authors to use as they are developing and evaluating Web content.

    [end change]
  3. [begin change]

    Understanding WCAG 2.0 - A guide to understanding and implementing WCAG 2.0. There is a short "Understanding" document for each guideline and Success Criterion in WCAG 2.0 as well as key topics.

    [end change]
  4. [begin change]

    Techniques for WCAG 2.0 - A collection of techniques and known failures, each in a separate document, that includes a description, examples, code and tests.

    [end change]
[begin add]

See Overview of WCAG 2.0 Documents for a description of the WCAG 2.0 supporting material, including education resources related to WCAG 2.0.

[end add]
[begin delete]

Additional Resource Documents on WCAG 2.0 and Web Accessibility

In addition to WCAG and its primary reference documents prepared by the WCAG Working group, there are a number of additional resource documents available on WCAG 2.0 and its relationship to Web accessibility. This set of documents will continue to grow even after the WCAG 2.0 is released. Documents available at the time of this document's release include:

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

  • WCAG 2 FAQ - Provides key information on the most commonly asked questions around WCAG 2.0.

  • WAI Resources on Introducing Web Accessibility - Provides basic information for people who are new to Web accessibility.

Other documents under development include:

  • Transitioning from WCAG 1.0 to 2.0 - Information to facilitate transitioning from use of WCAG 1.0 to WCAG 2.0.

  • Application Notes - Provides detailed application information in different areas such as "Designing Accessible Web Forms," or "Creating Basic HTML Web Pages that are Accessible."

[end delete]
[begin delete]

Organization of the WCAG 2.0 Document

The Four Principles

The guidelines and Success Criteria are organized around the following four principles. These four principles lay the foundation necessary for anyone to access and use Web content. Anyone who wants to use the Web must have content that is:

  1. Perceivable - Information and user interface components must be perceivable by users;

  2. Operable - User interface components must be operable by users;

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

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

The Guidelines

Under each principle there is a list of guidelines that address the principle. There are a total of 12 guidelines. A convenient list of just the guidelines can be found in the table of contents.

Success Criteria

Under each guideline there are Success Criteria that describe specifically what must be achieved in order to conformance [begin delete] to this standard [2184] [end delete]. They are similar to the "checkpoints" in WCAG 1.0. Each Success Criterion is written as a statement that will be either true or false when specific Web content is tested against it.

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. The same results should be obtained with a high level of confidence when [begin change]the content is tested by those who understand how people with different types of disabilities use the Web [2321] [end change].

Each Success Criterion for a guideline has a link to the section of the Quick Reference document that provides:

  • sufficient techniques for meeting the Success Criterion,

  • optional advisory techniques, and

  • [begin change]

    links to descriptions of the intent of the Success Criteria (including benefits) and examples. [2186]

    [end change]

Three levels of conformance

WCAG 2.0 Success Criteria are organized into three levels of conformance.

  • "Level A" conformance: all Level A Success Criteria must be satisfied in order to achieve Level A conformance.

  • "Level AA" conformance: all Level A and Level AA Success Criteria must be satisfied in order to achieve Level AA conformance.

  • "Level AAA" conformance: all Level A, AA, and AAA must be satisfied in order to achieve Level AAA 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 Level AAA may not be fully accessible to every person with a disability or combination of disabilities, especially certain types of severe disabilities.

  • In general, Level A Success Criteria achieve accessibility by supporting assistive technology while putting the fewest possible limits on presentation. Thus people with a wide range of disabilities using a wide range of assistive technologies, from voice input and eye-tracking devices to screen readers and screen magnifiers, are able to access content in different ways. In other words, Level A Success Criteria support the ability of both mainstream and specialized user agents to adapt content to formats that meet their users' needs.

  • The Success Criteria in Level AA provide additional support for assistive technology. At the same time, they also support direct access to content by the many people who use conventional user agents without assistive technology. In general, Level AA Success Criteria place more limits on visual presentation and other aspects of content than the Success Criteria in Level A.

  • Level AAA Success Criteria increase both direct access and access through assistive technology. They place tighter limits on both presentation and content, which means that some types of content may not be able to satisfy this level of conformance.

It is recommended that even if content does not conform at a specific level, that it conform to the extent possible.

[end delete]

Important Terms in WCAG 2.0

[begin change]WCAG 2.0 includes three important terms that are different from WCAG 1.0.[end change] [begin delete] In some cases, these terms are just clarifications of concepts that have been in use but have not been clearly defined in the past. In other cases, they are terms that match new concepts that have been [begin add]developed to allow for new technologies, potential accessibility issues that result from their use, and strategies that emerge to address these issues[end add] developed to cope with the new technologies that are continually emerging and with the accessibility issues and strategies that are emerging to address them. [2189] [end delete] [begin add]Each of these is introduced briefly below and defined more fully in the glossary.[end add]

Sufficient Techniques
[begin delete]

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

[end delete]
[begin delete]

Passing all tests for all sufficient techniques is not necessary. Most Success Criteria have multiple "sufficient techniques" listed. Any of the listed "sufficient techniques" can be used to meet the Success Criterion.

[end delete]
[begin delete]

Note that it is not necessary to meet a Success Criterion using one of the sufficient techniques that have been documented by the WCAG working group. There may be other techniques which are not documented by the working group that would also meet the Success Criterion. The working group went through the effort to document these "sufficient techniques" in order to make it easy for authors to identify techniques that meet each Success Criterion and to have confidence (and evidence) that the techniques meet the Success Criterion. When using other 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. The working group will continue to add new "sufficient techniques" as they are identified, developed, or made effective by advances in user agents including assistive technologies.

[end delete]
Advisory Techniques
[begin delete]

In addition to the sufficient techniques, there are a number of techniques that may enhance accessibility, but did not qualify as sufficient techniques because they are not testable, are not sufficient to meet the full requirements of the Success Criteria, and/or are good and effective techniques in some circumstances but not effective (and therefore sufficient) in others. These are listed as "Advisory Techniques." Authors are encouraged to use these techniques where appropriate. Although using them does not affect conformance, it can enhance accessibility for some users. 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.

[end delete]
Web Page
[begin add]

It is important to note that, in this standard, the term "Web page" includes much more than static HTML pages. It also includes the increasingly dynamic Web pages that are emerging on the Web, including "pages" that can present entire virtual interactive communities. For example, the term "Web page" includes an immersive interactive movie-like experience that you find at a single URL. For more information, see Understanding "Web Page".

[end add]
[begin delete]

While not an entirely new term, it is important to note that, in this standard, the term "Web page" includes much more than static HTML pages. It also includes the increasingly dynamic Web pages that are emerging on the Web, including "pages" that can present entire virtual interactive communities. Technically a Web page, as defined in the glossary, is "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." What this means is that a Web page is whatever you find at the end of a Web address that you visit. It includes Web applications, Webcasts, synchronized media 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.

[end delete]
[begin delete]

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

[end delete]
Programmatically Determined

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 [begin add]extract and present this information to users in different modalities. For more information, see Understanding Programmatically Determined.[end add] [begin delete] access the information. A critical element in having anything be "programmatically determined" is that assistive technologies are able to retrieve and use the information. This lets user agents, including assistive technologies, transform the content and present it to the user in different sensory modalities (e.g. vision, hearing) or styles of presentation. If assistive technologies cannot do this, then the information cannot be said to be programmatically determined. [end delete]

[begin delete]

The term was created in order to allow the working group to clearly identify those places where information had to be accessible to assistive technologies (and other user agents acting as accessibility aids) without specifying exactly how this needed to be done. This is important because of the continually changing nature of the technologies. It is important neither to declare things as accessible because they might be in the future (when they aren't now) nor to declare things as inaccessible in a permanent way when they may very well become accessible in the future.

[end delete]
[begin delete]

The use of the term allows the guidelines to identify what needs to be "programmatically determined" in order to meet the guidelines, and then have separate [begin add]documents (the Quick Reference, Understanding, and Technique documents) to list techniques and technologies that meet the requirements, which can be updated over time based on user agent and assistive technology support.[end add] [begin delete], updateable documents (the Quick Reference, Understanding, and Technique documents) list those techniques and technologies that meet the requirements over time. [end delete] [2196]

[end delete]
Accessibility Supported
[begin add]

An accessibility supported technology is a [begin delete]Web[end delete] technology (HTML, CSS, etc.) that will work with assistive technologies (AT) and the accessibility features of browsers and other user agents. Only [begin delete]Web[end delete] technologies ([begin change]including[end change] features of the technologies), that are "accessibility supported" can be used to conform to WCAG 2.0 Success Criteria. [begin add]Only "accessibility supported" technologies can be used to conform to WCAG 2.0 Success Criteria[end add] Technologies that are not accessibility supported (do not work with AT etc.) can be used, but cannot be used to conform to any Success Criterion.

[end add]

[begin add]The [begin change]definition of[end change] "accessibility support" is provided in the Appendix A: Glossary section of these guidelines.[end add] For more information, see Understanding accessibility support in Understanding WCAG 2.0.

[begin delete]

In order for content created with technology (Web content) (such as HTML, CSS, PDF, GIF, MPEG, Flash etc.) to be accessible to people with different types of disabilities, it is essential that the technologies [begin change]used work with the accessibility features of browsers and other user agents, including assistive technologies. In order for something to meet a Success Criterion that requires it to be "programmatically determined," it would need to be implemented using a technology that has assistive technology support.[end change] [2197]

[end delete]
[begin delete]

"Accessibility supported" means supported by users' assistive technologies as well as the accessibility features in browsers and other user agents.

[end delete]
[begin delete]

Authors who don't know which technologies or which aspects and features of a technology have support from assistive technologies should consult documented lists of technologies that are known to have accessibility support. Such lists can make it easier than it is today for an author to identify technologies or features of different technologies that are supported by assistive technologies and can be used to meet the Success Criteria that require assistive technology support (i.e. require that content can be programmatically determined.)

[end delete]
[begin delete]

Note: The requirements for "accessibility support" of Web technologies are provided in the conformance section of these guidelines (See also .)

[end delete]

WCAG 2.0 Guidelines

This section is normative.

Principle 1: Perceivable - Information and user interface components must be presentable to users in ways they can perceive

Guideline 1.1 Text Alternatives: 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 Understanding Guideline 1.1

[begin change]

1.1.1 Non-text Content: All non-text content has a text alternative that presents equivalent information, except for the situations listed below. [1992] (Level A) How to Meet 1.1.1 Understanding 1.1.1

  • Controls, Input: If [begin add]it[end add] [begin delete]non-text content[end delete] is a control or accepts user input, then it has a name that describes its purpose. (See also Guideline 4.1.)

  • [begin change]

    Media, Test, Sensory: If [begin add]it[end add] [begin delete]non-text content[end delete] is [begin delete]any of the following[end delete] [begin add](1) [end add] synchronized media, [begin add](2) [end add] live audio-only or live video-only content, [begin add](3) [end add]a test or exercise that must be presented in non-text format, [begin add](4) [end add] [begin delete]content [end delete]primarily intended to create a specific sensory experience, then text alternatives at least [begin change]provide descriptive identification of the non-text content[end change] [begin add], or (5) a media alternative to text that is clearly labeled as such [2290] [end add]. (For synchronized media, see also Guideline 1.2.)

    [end change]

    Note: Prerecorded audio-only and video-only files would be covered under Success Criterion 1.1.1, which requires text alternatives that present equivalent information.

    [2082]
  • CAPTCHA: If [begin add]it[end add] [begin delete]the purpose of non-text content[end delete] 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[begin add], and alternative forms of CAPTCHA using output modes for different types of sensory perception[end add] [begin delete]and alternative forms in different modalities[end delete] are provided to accommodate different disabilities.

  • Decoration, Formatting, Invisible: If [begin add]it[end add] [begin delete]non-text content[end delete] is pure decoration, or used only for visual formatting, or if it is not presented to users, then it is implemented [begin change]in a way[end change] [begin delete]such[end delete] that it can be ignored by assistive technology.

[end change]
[begin add]

1.1.2 Live Audio-only: All live audio-only content has a text alternative [1944] (Level AAA) How to Meet 1.1.2 Understanding 1.1.2

[end add]

Guideline 1.2 Synchronized Media: Provide synchronized alternatives for synchronized media Understanding Guideline 1.2

1.2.1 Captions (Prerecorded): Captions are provided for prerecorded synchronized media, [begin change]except if the synchronized media is an alternative to text and is clearly labeled as such [2290] [end change]. (Level A) How to Meet 1.2.1 Understanding 1.2.1

1.2.2 Audio Description or Full Text Alternative: Audio description of video, or a full text alternative for synchronized media including any interaction , is provided for prerecorded synchronized media. (Level A) How to Meet 1.2.2 Understanding 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.

1.2.3 Captions (Live): Captions are provided for live synchronized media. (Level AA) How to Meet 1.2.3 Understanding 1.2.3

Note: If synchronized media is completely computer generated, it is not live and is subject to the requirements for prerecorded synchronized media in WCAG 2.0.

1.2.4 Audio Description: Audio description of video is provided for prerecorded synchronized media. (Level AA) How to Meet 1.2.4 Understanding 1.2.4

1.2.5 Sign Language: Sign language interpretation is provided for [begin add]prerecorded [end add] synchronized media. (Level AAA) How to Meet 1.2.5 Understanding 1.2.5

1.2.6 Audio Description (Extended): Extended audio description of video is provided for prerecorded synchronized media. (Level AAA) How to Meet 1.2.6 Understanding 1.2.6

1.2.7 Full Text Alternative: A full text alternative for synchronized media including any interaction is provided for all prerecorded synchronized media, [begin change]except if the synchronized media is an alternative to text and is clearly labeled as such [2290] [end change]. (Level AAA) How to Meet 1.2.7 Understanding 1.2.7

Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example [begin change]simpler layout [2094] [end change]) without losing information or structure Understanding Guideline 1.3

1.3.1 Info and Relationships: Information[begin add], structure, [2291] [end add] and relationships conveyed through presentation can be programmatically determined or are available in text[begin delete], and notification of changes to these is available to user agent, including assistive technology (as used in this document) [2305] [end delete]. (Level A) How to Meet 1.3.1 Understanding 1.3.1

1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined [begin delete] and sequential navigation of interactive components is consistent with that sequence[end delete]. (Level A) How to Meet 1.3.2 Understanding 1.3.2

1.3.3 Sensory Characteristics: [begin add]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.[end add] [begin delete]Instructions provided for understanding and operating content do not rely on shape, size, visual location, or orientation of components.[end delete] [2015] (Level A) How to Meet 1.3.3 Understanding 1.3.3

Guideline 1.4 Distinguishable: Make it easier for [begin change]users [2204] [end change] to see and hear content including separating foreground from background Understanding Guideline 1.4

1.4.1 Use of Color: [begin add]Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.[end add] [begin delete]Any information that is conveyed by color differences is also simultaneously visually evident without the color differences.[end delete] (Level A) How to Meet 1.4.1 Understanding 1.4.1

[begin add]

Note 1: This Success Criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3. [2255]

[end add]
[begin add]

Note 2: Programmatic access to color and other visual presentation coding is covered in Guideline 1.3.

[end add]

1.4.2 Audio Control: If any audio [begin add]on a Web page[end add] 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 [begin add]to be a different level from the system volume level[end add] [begin delete]independently of the system volume[end delete]. [2131] [2185] (Level A) How to Meet 1.4.2 Understanding 1.4.2

[begin add]

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.

[end add]
[begin change]

1.4.3 Contrast (Minimum): Text and images of text have a contrast ratio of at least 5:1, except for the following: [2000] (Level AA) How to Meet 1.4.3 Understanding 1.4.3

[end change]
[begin add]
  • Large Print: Large-scale text and large-scale images of 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 incidental text in an image, or that are not visible to anyone, have no minimum contrast requirement.

[end add]
[begin add]

Note: Success Criteria 1.4.3 and 1.4.6 can be met via a contrast control available on or from the page.

[end add]

1.4.4 Resize text: [begin add] Text (but not images of text)[end add] [begin delete]Visually rendered text[end delete] can be resized without assistive technology up to 200 percent [begin delete]and down to 50 percent [2112] [end delete]without loss of content or functionality. [2164] (Level AA) How to Meet 1.4.4 Understanding 1.4.4

1.4.5 Images of Text (Limited): When [begin change]the accessibility supported technologies being used can[end change] achieve the visual presentation, text is used to convey information rather than images of text [begin change]except for the following:[end change] [begin delete]the image of the text can be visually customized to the user's requirements.[end delete] (Level AA) How to Meet 1.4.5 Understanding 1.4.5

[begin add]
  • Customizable: The image of text can be visuallycustomized to the user's requirements;

  • Essential: A particular presentation of text is essential to the information being conveyed.

[end add]
[begin add]

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

[end add]
[begin change]

1.4.6 Contrast (Enhanced): Text and images of text have a contrast ratio of at least 7:1, except for the following: [2000] (Level AAA) How to Meet 1.4.6 Understanding 1.4.6

[end change]
[begin add]
  • Large Print: Large-scale text and large-scale images of text have a contrast ratio of at least 5:1;

  • Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are incidental text in an image, or that are not visible to anyone, have no minimum contrast requirement.

[end add]
[begin add]

Note: Success Criteria 1.4.3 and 1.4.6 can be met via a contrast control available on or from the page.

[end add]

1.4.7 Low or No Background Audio: Audio content that is not an audio CAPTCHA and [2355] that contains speech in the foreground 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. (Level AAA) How to Meet 1.4.7 Understanding 1.4.7

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

[begin add]

1.4.8 Visual Presentation: For the visual presentation of blocks of text, a mechanism is available to achieve the following: (Level AAA) How to Meet 1.4.8 Understanding 1.4.8

  • foreground and background colors can be selected by the user

  • width is no more than 80 characters

  • text is not aligned on both the left and the right [1253] [569]

  • line spacing is at least space-and-a-half within paragraphs, and paragraph spacing is larger than line spacing [569]

  • text is resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text

[end add]
[begin add]

1.4.9 Images of Text (Essential): Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. (Level AAA) How to Meet 1.4.9 Understanding 1.4.9

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

[2128]
[end add]

Principle 2: Operable - User interface components and navigation must be operable

Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard Understanding 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 function requires input that depends on the path of the user's movement and not just the endpoints. (Level A) How to Meet 2.1.1 Understanding 2.1.1

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.

[begin add]

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

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.

[2222]
[end add]

2.1.3 Keyboard (No Exception): All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA) How to Meet 2.1.3 Understanding 2.1.3

Guideline 2.2 Enough Time: Provide users with disabilities enough time to read and use content Understanding Guideline 2.2

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

  • 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 [2226] "), 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 [begin delete]is part of an activity where moving, blinking, scrolling, or auto-updating timing is essential [begin delete](for example, time-based testing) [end delete]and time limits [2227] [end delete] cannot be extended [begin delete]further[end delete] without invalidating the activity; or [1949]

  • [begin add]

    20 Hour Exception: the time limit is longer than 20 hours. [2114]

    [end add]
[begin add]

Note: This Success Criterion acts to ensure that changes in content or context as a result of a time limit will not occur unexpectedly, preventing users from completing tasks. While exceptions to Success Criterion 2.2.1 where timing is essential exist, guideline 2.2 in general limits changes in content for no reason. 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. [2340]

[end add]

2.2.2 Pausing: Moving, blinking, scrolling, or auto-updating information [begin add]on a Web page that lasts for more than [begin change]three[end change] seconds[end add] can be paused by the user unless [begin change]the movement, blinking, scrolling, or auto-updating[end change] is part of an activity where [begin add]the changes are[end add] [begin delete]timing or movement are[end delete] essential. Moving [begin add]or blinking[end add] content that is pure decoration can be stopped or hidden by the user. (Level AA) How to Meet 2.2.2 Understanding 2.2.2

Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3.

[begin add]

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.

[end add]
[begin add]

Note 3: Content that is updated from a process, real-time or remote stream 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. [2132]

[end add]

2.2.3 No Timing: Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. (Level AAA) How to Meet 2.2.3 Understanding 2.2.3

2.2.4 Interruptions: Interruptions[begin delete], such as updated content,[end delete] can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA) How to Meet 2.2.4 Understanding 2.2.4

2.2.5 Re-authenticating: When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA) How to Meet 2.2.5 Understanding 2.2.5

[begin change]

Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures Understanding Guideline 2.3

[end change]

2.3.1 Three Flashes or Below Threshold: [begin add] Web pages do [end add] [begin delete]Content does[end delete] 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) How to Meet 2.3.1 Understanding 2.3.1

[begin add]

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.

[end add]

2.3.2 Three Flashes: [begin add] Web pages do [end add] [begin delete]Content does[end delete] not contain anything that flashes more than three times in any one second period. (Level AAA) How to Meet 2.3.2 Understanding 2.3.2

Guideline 2.4 Navigable: Provide ways to help users with disabilities navigate, find content and determine where they are Understanding Guideline 2.4

[begin add] [end add]

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

Guideline 3.1 Readable: Make text content readable and understandable Understanding Guideline 3.1

3.1.1 Language of Page: The default human language of each Web page [begin delete]within the content [end delete]can be programmatically determined. (Level A) How to Meet 3.1.1 Understanding 3.1.1

3.1.2 Language of Parts: The human language of each [begin change]passage[end change] or phrase in the content can be programmatically determined [begin add] 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[end add]. [2069] (Level AA) How to Meet 3.1.2 Understanding 3.1.2

[begin delete]

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.

[end delete]

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. (Level AAA) How to Meet 3.1.3 Understanding 3.1.3

3.1.4 Abbreviations: A mechanism for [begin change]identifying[end change] the expanded form or meaning of abbreviations is available. (Level AAA) How to Meet 3.1.4 Understanding 3.1.4

3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level, supplemental content, or [begin add]a version[end add] [begin delete]an alternate version is available[end delete] that does not require reading ability more advanced than the lower secondary education level, [begin add]is available[end add]. (Level AAA) How to Meet 3.1.5 Understanding 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. (Level AAA) How to Meet 3.1.6 Understanding 3.1.6

Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways Understanding Guideline 3.2

3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) How to Meet 3.2.1 Understanding 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. (Level A) How to Meet 3.2.2 Understanding 3.2.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. (Level AA) How to Meet 3.2.3 Understanding 3.2.3

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

3.2.5 Change on Request: Changes of context are initiated only by user request[begin add] or a mechanism is available to turn off such changes [2349] [end add]. (Level AAA) How to Meet 3.2.5 Understanding 3.2.5

Guideline 3.3 Input Assistance: Help users avoid and correct mistakes Understanding Guideline 3.3

3.3.1 Error Identification: If an input error is [begin delete]automatically [2235] [end delete] detected, the item that is in error is identified and [begin add]the error is [2012] [end add] described to the user in text. (Level A) How to Meet 3.3.1 Understanding 3.3.1

3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) How to Meet 3.3.2 Understanding 3.3.2

[2342]

3.3.3 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. (Level AA) How to Meet 3.3.3 Understanding 3.3.3

3.3.4 Error Prevention (Legal, Financial, Data): For [begin add]Web pages[end add] [begin delete]forms[end delete] that cause legal commitments or financial transactions [begin add]for the user [1947] [end add]to occur, that modify or delete user-controllable data in data storage systems, or that submit [begin add]user [1947] [end add]test responses, at least one of the following is true: (Level AA) How to Meet 3.3.4 Understanding 3.3.4

  1. Reversible: [begin change]Submissions [1947] [end change] are reversible.

  2. Checked: [begin change]Data entered by the user[end change] is checked for input errors [begin delete]before going on to the next step in the process [1947] [end delete] [begin add] and the user is provided an opportunity to correct them [2014] [end add].

  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the [begin change]submission [1947] [end change].

3.3.5 Help: Context-sensitive help is available. (Level AAA) How to Meet 3.3.5 Understanding 3.3.5

3.3.6 Error Prevention (All): For [begin add]Web pages[end add] [begin delete]forms[end delete] that require the user to submit information, at least one of the following is true: (Level AAA) How to Meet 3.3.6 Understanding 3.3.6

  1. Reversible: [begin change]Submissions [1947] [end change] are reversible.

  2. Checked: [begin change]Data entered by the user[end change] is checked for input errors [begin delete]before going on to the next step in the process [1947] [end delete] [begin add] and the user is provided an opportunity to correct them [2014] [end add].

  3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the [begin change]submission [1947] [end change].

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: Maximize compatibility with current and future user agents, including assistive technologies Understanding 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, [begin delete]and [end delete] the elements are nested according to their specifications[begin add], and any IDs are unique [1928] [end add]. (Level A) How to Meet 4.1.1 Understanding 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. (Level A) How to Meet 4.1.2 Understanding 4.1.2

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

Conformance

This section is normative.

[begin add]

This section lists requirements for conformance to WCAG 2.0 as well as information about how to make [begin change]conformance claims, which are optional[end change]. [begin change]It also introduces what it means for Web content technologies to be accessibility-supported, since only accessibility-supported technologies can be relied on for conformance. Understanding Conformance includes further explanation of this concept. [2273] [end change] [2277]

[end add]
[begin delete]

Conformance means that Web content satisfies a Success Criterion the Success Criteria. This conformance section describes conformance, lists the conformance requirements as well as how to make optional conformance claims, and explains the important role of accessibility support of Web technologies.

[end delete]

Conformance requirements

In order [begin add]for a Web page [end add]to conform to WCAG 2.0, all of the following conformance requirements must be [begin add]satisfied[end add] [begin delete]met for each Web page[end delete]:

[begin change]

1.) Conformance Level: One of the following levels of conformance is met in full. [2220]

  • Level A: For Level A conformance (the minimum level of conformance), the Web page satisfies all the Level A Success Criteria, or a conforming alternate version is provided.

  • Level AA: For Level AA conformance, the Web page satisfies all the Level A and Level AA Success Criteria, or a Level AA conforming alternate version is provided.

  • Level AAA: For Level AAA conformance, the Web page satisfies all the Level A, Level AA and Level AAA Success Criteria, or a Level AAA conforming alternate version is provided.

Note: Although conformance can only be achieved at the stated levels, authors are encouraged to satisfy and report progress toward meeting Success Criteria from all levels beyond the achieved level of conformance.

[end change]
[begin delete]

For level A conformance (the minimum level of conformance), the Web page satisfies a Success Criterion all the Level A Success Criteria, or the page satisfies conformance requirement 4.

[end delete]
[begin delete]

For level AA conformance, the Web page satisfies all the Level A and Level AA Success Criteria, or the page satisfies conformance requirement 4.

[end delete]
[begin delete]

For level AAA conformance, the Web page satisfies all the Level A, Level AA and Level AAA Success Criteria, or the page satisfies conformance requirement 4.

[end delete]
[begin delete]

If the Web page does not meet all of the Success Criteria for a specified level, then a mechanism to obtain an alternate version that meets all of the Success Criteria can be derived from the nonconforming content or its URI, and that mechanism meets all Success Criteria for the specified level of conformance. 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). If multiple language versions are available, then conforming versions are required for each language offered.

[begin delete]

Editorial Note: As currently worded, requirement #4 ensures that a mechanism is available to find a conforming version from any nonconforming version. The working group is concerned that it has not identified enough supported mechanisms to meet the needs and constraints of different technologies or the limitations authors may have in their content or server. Requirement #4 is therefore "at risk" in its current form. If there are not sufficient techniques to meet the current language, it would have to change. The two options under consideration if that happens both have disadvantages. The options are:

  • Fallback option #1: Requiring an accessible link from the nonconforming content, which would block use of some current and future technologies if they do not support WCAG conforming links, or

  • Fallback option #2: Allowing the requirement to be met by a single page with links to the conforming and non-conforming pages, or other techniques that may provide an option to find the conforming version when browsing, but that would leave the user with no way to find the conforming page after reaching a non-conforming page via search, or a link from a blog, email, article, other page etc.

Further discussion of this topic is available at Alternate Versions Conformance Requirement. The working group seeks suggestions for additional sufficient techniques that would allow us to keep the current language as well as comments, input, and thoughts on the two alternatives should we fail to identify enough.

[end delete]
[end delete]

2.) Full pages: Conformance is for full Web page(s) only, and cannot be achieved if part of a Web page is excluded.

Note: For the purpose of determining conformance, a conforming alternative to part of a page's content is considered part of the page when the alternative content is obtainable directly from the page[begin add], e.g., a long description[end add].

[begin change]

3.) Complete processes: When a series of Web pages present sequential steps that need to be completed in order to accomplish an activity, all Web pages in the series conform at a particular level. (Conformance is not possible at any level if all pages in the sequence do not conform at that level.)

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 for any page that is part of the sequence to conform.

[end change]

4.) Accessibility-Supported Technologies Only: Only [begin delete]documented [end delete] accessibility supported [begin delete]Web [end delete]technologies are relied upon to [begin add]satisfy the[end add] [begin delete] meet[end delete] Success Criteria. Any information or functionality that is implemented in technologies that are not accessibility supported must also be available via technologies that are accessibility supported. [begin add](See Understanding accessibility support.) [2276] [end add]

5.) Non-Interference: If [begin delete]Web [end delete]technologies that are not accessibility supported are used on a page, or accessibility-supported technologies are used in a non-conforming way, then they do not block the ability of users to access the rest of the page. [begin delete]Specifically: [end delete] [begin add]Specifically, the Web page as a whole continues to meet the conformance requirements under all of the following conditions:[end add]

[begin add]
  1. when any (non accessibility-supported) technology is turned on in a user agent, and

  2. when it is turned off in a user agent, and

  3. when it is not supported by a user agent

[end add]
[begin add]

Note: The following Success Criteria all apply to full pages including technologies that are not accessibility supported or relied upon to meet the other Success Criteria because they deal with things that could interfere with overall use of the page: 1.4.2 - Audio Control, 2.1.2 - No Keyboard Trap, 2.3.1 - Three Flashes or Below Threshold, and 2.2.2 - Pausing.

[end add]
[begin delete]
  1. No Keyboard Trap: If focus can be moved to technologies that are not accessibility supported 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 A Success Criteria.

  2. Three Flashes or Below Threshold: To minimize the risk of seizures due to photosensitivity, content does 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 (see Success Criterion 2.3.1).

  3. Non support: The content continues to meet the conformance requirements when the (non accessibility-supported) technology is turned on, turned off, or is not supported by a user agent.

[end delete]
[begin delete]

For the purpose of determining conformance, a conforming alternative to part of a page's content is considered part of the page.

[end delete]
[begin add]

Note: If pages cannot conform (for example, conformance test pages or example pages) they cannot be included in the scope of conformance or conformance claim.

[end add]

For more information, see Understanding Conformance Requirements.

[begin delete]

Accessibility Support of Web Technologies

In choosing Web technology (Web content) (HTML, scripting, etc.) that will be used when creating content that will meet the WCAG 2.0 Success Criteria, authors must use technologies that are supported by users' assistive technologies as well as the accessibility features in browsers and other user agent. Such technologies are referred to as "accessibility supported."

Using public documented lists of technologies that have accessibility support

The easiest way to be sure that the technologies and features being used have the necessary AT support is to use technologies from documented lists of Web technologies that are "accessibility supported." (See Documented lists of Web technologies with accessibility support in Understanding WCAG 2.0.)

Creating your own list of technologies that have accessibility support

Authors, companies or others may wish to create and use their own lists of accessibility-supported technologies.

Rules for Supported Technologies

To qualify as an accessibility-supported technology, the following must be true for a technology:

  1. The Web technology must be supported by users' assistive technology (AT). This means that either the technology implements and tests accessibility APIs that are required in order for the users' assistive technology to make the technology accessible, or the technology has been tested for interoperability with users' assistive technology in the human language of the content.

  2. The Web technology must have accessibility-supported user agents that are available to users.

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

    1. The technology is supported natively in widely-distributed user agents that are also accessibility supported (such as HTML and CSS); OR

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

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

    4. The 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 1: Web technologies that are not accessibility supported can be used as long as and are met.

Note 2: When a Web Technology is "accessibility supported," it does not imply that the entire technology must be supported. Most technologies lack support for at least one feature. When referring to "accessibility support" for a technology, the support for specific aspects, features, and extensions should be cited if the technology as a whole is not accessibility supported. A profile of a technology may be used to give a name to the set of aspects, features, or extensions of a technology that are "accessibility supported."

Note 3: When citing technologies that have multiple versions, the version(s) supported should be specified.

[end delete]

Conformance claims (optional)

[begin change]

Conformance is defined only for Web pages. However, a conformance claim may be made to cover one page, a series of pages, or multiple related Web pages.

[end change]

Required components of a conformance claim

[begin change]

Conformance claims are not required. Authors can conform to WCAG 2.0 without making a claim. However, if a conformance claim is made, then the conformance claim must include the following information:

[end change]
  1. Date of the claim

  2. Guidelines title, version and URI "Web Content Accessibility Guidelines 2.0 at {URI of final document}"

  3. Conformance level satisfied: (Level A, AA or AAA)

  4. [begin add]

    A concise description of the Web pages such as a list of URIs for which the claim is made, including whether subdomains are included in the claim.

    [end add]
    [begin delete]

    A description of the URIs that the claim is being made for, including whether subdomains are included in the claim.

    [end delete]
    [begin add]

    Note 1: The Web pages may be described by list or by an expression which describes all of the URIs included in the claim.

    Note 2: Web-based products that do not have a URI prior to installation on the customer's Web site may have a statement that the product would conform when installed.

    [end add]
  5. A list of accessibility-supported technologies that includes all of the [begin add]Web content[end add] technologies relied upon .

    Note: When citing technologies that have multiple versions, the version(s) supported must be specified.

Optional components of a conformance claim

In addition to the required components of a conformance claim above, consider providing additional information to assist users. Recommended additional information includes:

  1. A list of Success Criteria beyond the level of conformance claimed that have been met. This information should be provided in a form that consumers can use, preferably machine-readable metadata.

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

    [begin delete]

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

    [end delete]
  3. [begin change]

    A list of user agents, including assistive technologies, that were used to test the content. [2224]

    [end change]
  4. Information about any additional steps taken that go beyond the Success Criteria to enhance accessibility.

  5. [begin change]

    A machine-readable metadata version of the list of specific technologies that are relied upon.

    [end change]
  6. A machine-readable metadata version of the conformance claim.

[begin delete]

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

[end delete]

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, an article that allows users to add comments to the bottom, or applications supporting user contributed content. Another example would be a page composed of content aggregated from multiple contributors, such as in portals and news sites. 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. [begin change]

    A determination of conformance can be made based on best knowledge. If a page of this type is monitored and kept conforming (non-conforming content is immediately removed or made conforming) then a determination or claim of conformance can be made since, except for errors in externally contributed content which are corrected or removed immediately, the page conforms. No conformance claim [begin change]can[end change] be made if it is not possible to monitor or correct non-conforming content;

    [end change]

    OR

  2. [begin change]

    A "statement of partial conformance" is made, that the page does not conform, but could conform if certain parts were removed. 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." In addition, the following would also be true of the non-conforming content. The content that is excluded in the statement of partial conformance:

    [end change]
    1. [begin add]

      cannot be content that is under the author's control

      [end add]
      [begin delete]

      The content that is excluded in the statement of partial conformance cannot be content that is under the author's control.

      [end delete]
    2. [begin add]

      must be described in a way that that users can identify (e.g. they can't be described as "all parts that we do not control" unless they are clearly marked as such.)

      [end add]
      [begin delete]

      The content that is excluded in the statement of partial conformance 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.)

      [end delete]

Appendix A: Glossary

This section is normative.

abbreviation

shortened form of a word, phrase, or name [begin add]where the original expansion has not been rejected by the organization that it refers to and where the abbreviation has not become part of the language[end add]

Note: This includes initialisms and acronyms where:

  1. initialisms are shortened forms of a name or phrase made from the initial letters of words or syllables contained in that name or phrase

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

  2. acronyms are abbreviated forms 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.

accessibility supported

supported by users' assistive technologies as well as the accessibility features in browsers and other user agents

[begin add]

To qualify as an accessibility-supported Web content technology (or feature of a technology), both of the following must be true for a Web content technology (or feature): [2174]

[end add]
[begin add]
  1. The Web content technology must be supported by users' assistive technology (AT). This means that the technology has been tested for interoperability with users' assistive technology in the human language(s) of the content,

    AND

  2. The Web content technology must have accessibility-supported user agents that are available to users. This means that at least one of the following is true:

    1. The technology is supported natively in widely-distributed user agents that are also accessibility supported (such as HTML and CSS);

      OR

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

      OR

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

      OR

    4. The user agent(s) that support the technology are accessibility supported and are available for download or purchase in a way that:

      1. does not cost a person with a disability any more than a person without a disability and

      2. is as easy to find and obtain for a person with a disability as it is for a person without disabilities.

[end add]
[begin add]

Note 1: The WCAG Working group and the W3C do not specify which or how many assistive technologies must support a Web technology in order for it to be classified as accessibility supported. (See Level of Assistive Technology Support Needed for "Accessibility Support".)

[end add]
[begin add]

Note 2: Web technologies that are not accessibility supported can be used as long as they are not relied upon and the page as a whole meets the conformance requirements including Conformance Requirement 4: Accessibility-Supported Technologies Only and Conformance Requirement 5: Non-Interference are met.

[end add]

Note 3: When a Web Technology is "accessibility supported," it does not imply that the entire technology must be supported. Most technologies lack support for at least one feature. When documenting "accessibility support" for a technology, the support for specific aspects, features, and extensions should be cited if the technology as a whole is not accessibility supported. A profile of a technology may be used to give a name to the set of aspects, features, or extensions of a technology that are "accessibility supported." [begin add]Pages conform to WCAG only if aspects or features of the technology that are accessibility supported can be relied upon to meet WCAG requirements. [2174] [end add]

[begin add]

Note 4: When citing Web content technologies that have multiple versions, the version(s) supported should be specified.

[end add]
[begin add]

Note 5: The easiest way to be sure that the Web content technologies and features being used and relied upon are accessibility supported is to use technologies from documented lists of accessibility supported Web content technologies. (See Understanding Documented lists of Web technologies with Accessibility Support.) [2273] Some authors, companies or others may wish to document and use their own lists of accessibility-supported Web content technologies. However, all technologies on the list must meet the definition of accessibility supported Web content technologies above. [2219]

[end add]
activity where [begin add]moving, blinking, scrolling, or auto-updating[end add] [begin delete]timing[end delete] is essential

activity where [begin add]moving, blinking, scrolling, or auto-updating[end add] [begin delete]timing[end delete] is [begin add]central to[end add] [begin delete]part of[end delete] the design of the activity and removal [begin delete]of the time dependency [end delete]would [begin add]fundamentally [end add]change the functionality of the content

ambiguous to users in general

the purpose cannot be determined from the link and all information of the Web page presented to the user simultaneously with the link (i.e. readers without disabilities would not know what a link would do until they activated it)

Example: The word guava in the following sentence "One of the notable exports is guava" is a link. The link could lead to a definition of guava, a chart listing the quantity of guava exported or a photograph of people harvesting guava. Until the link is activated, all readers are unsure and the person with a disability is not at any disadvantage.

[begin delete]Application Programming Interface (API)[end delete]
[begin delete]

definitions of how communication may take place between applications

[end delete]
[begin delete]

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 agent and promote the development of multi-platform assistive technology (as used in this document). 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.

[end delete]
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)
[begin add]

hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide [begin change]functionality[end change] to meet the requirements of users with disabilities that go beyond those offered by [begin delete]the [end delete]mainstream user agents [2140]

[end add]
[begin delete]

a user agent that[begin delete] both[end delete]:

[end delete]
[begin delete]
  1. provides services to meet the requirements of users with disabilities that go beyond those offered by the mainstream user agents. Such services include alternative presentations (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. [begin change]may rely[end change] [begin delete]usually relies[end delete] on services (such as retrieving Web content and parsing markup) provided by one or more other mainstream user agents. Assistive technologies communicate data and messages with mainstream user agents by using and monitoring APIs

[end delete]
[begin add]

Note 1: [begin change]functionality[end change] provided by assistive technology includes alternative presentations (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). [2140] [2270]

[end add]
[begin add]

Note 2: Assistive technologies often communicate data and messages with mainstream user agents by using and monitoring APIs. [2270]

[end add]
[begin add]

Note 3: The distinction between mainstream user agents and assistive technologies is not absolute. Many mainstream user agents provide some features to assist individuals with disabilities. The basic difference is that mainstream user agents target broad and diverse audiences that usually include people with and without disabilities. Assistive technologies target narrowly defined populations of users with specific disabilities. The assistance provided by an assistive technology is more specific and appropriate to the needs of its target users. The mainstream user agent may provide important [begin change]functionality[end change] to assistive technologies like retrieving Web content from program objects or parsing markup into identifiable bundles. [2171]

[end add]
[begin delete]

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

[end delete]
[begin delete]

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

[end delete]
[begin delete]

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

[end delete]

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 to 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[begin add] (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices.)[end add];

  • 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.)

Note 3: Also called "video description" and "descriptive narration."

blink
[begin change]

switch back and forth between two visual states in a way that is meant to draw attention [2289]

[end change]
[begin change]

Note: See also flash (It is possible for something to be large enough and blink brightly enough at the right frequency to be also classified as a flash).

[end change]
blocks of text

more than one sentence of text

CAPTCHA

initialism for "Completely Automated Public Turing test to tell Computers and Humans Apart"

Note 1: CAPTCHA tests often involve asking the user to type in text that is displayed in an obscured image or audio file.

Note 2: A Turing test is any system of tests designed to differentiate a human from a computer. It is named after famed computer scientist Alan Turing. The term was coined by researchers at Carnegie Mellon University. [CAPTCHA]

captions

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

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

[begin add]

Note 2: Audio descriptions can be, but do not need to be, captioned since they are descriptions of information that is already presented visually.

[end add]
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.

[begin add]

Example: Submitting a form, opening a new window, or moving focus to a different component are examples of changes of context. [1129]

[end add]
conformance

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

conforming alternate version
[begin change]

version that

[end change]
  1. conforms at the designated level, and

  2. provides all of the same information and functionality in the same human language, and

  3. is as up to date as the non-conforming [begin change]content[end change], and

  4. for which one [begin add]at least [end add]of the following is true:

    1. the conforming version can be reached from the non-conforming page via an accessibility supported mechanism, or

    2. the non-conforming version can only be reached from the conforming version, or

    3. the non-conforming version can only be reached from a conforming page that also provides a mechanism to reach the conforming version

[begin change]

Note 1: In this definition, "can only be reached" means that there is some mechanism, such as a conditional re-direct, that prevents a user from "reaching" (loading) the non-conforming page unless the user had just come from the specified page.

[end change]

Note 2: The alternate version does not need to be matched page for page with the original (e.g. the [begin change]conforming alternate version[end change] may consist of multiple pages).

Note 3: If multiple language versions are available, then conforming [begin add]alternate [end add]versions are required for each language offered.

Note 4: Alternate versions may be provided to accommodate different technology environments or user groups. Each version should be as conformant as possible. One version must be fully conformant in order to meet conformance requirement 1.

[begin add]

Note 5: The conforming alternative version does not need to reside within the scope of conformance as long as it is as freely available as the non-conforming version.

[end add]

Note 6: Alternate versions should not be confused with supplementary [begin add]content[end add] , which support the original page and enhance comprehension.

Note 7: Setting user preferences within the content to produce a conforming version is an acceptable mechanism for reaching another version as long as the method used to set the preferences is accessibility supported.

content (Web content)

information and sensory experience to be communicated to the user by means of a user agent, [begin add]including[end add] [begin delete]as well as[end delete] code or markup that defines the [begin add]content's[end add] structure, presentation, and interactions[begin delete]associated with those elements [end delete]

context-sensitive help

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

contrast ratio

(L1 + 0.05) / (L2 + 0.05), where

Note 1: Contrast ratios can range from 1 to 21 (commonly written 1:1 to 21:1).

Note 2: For dithered colors, use the average values of the colors that are dithered (average R, average G, and average B).

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

Note 4: Background color is the specified color of content over which the text is to be rendered in normal usage. If no background color is specified, then white is assumed.

[begin change]

Note 5: Background color is the specified color of content over which the text is to be rendered in normal usage. It is a failure if no background color is specified when a foreground color is specified, because the user's default background color is unknown and cannot be evaluated for sufficient contrast. For the same reason, it is a failure if no foreground color is specified when a background color is specified. [2263]

[end change]
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.

flash

a pair of opposing changes in relative luminance which may cause seizures in some people if it is large enough and in the right frequency range

Note 1: See general flash threshold and red flash threshold for information about types of flash that are not allowed.

Note 2: See also blink.

[2289]
full text alternative for synchronized media including any interaction

document including correctly sequenced text descriptions of all visual settings, actions, speakers, and non-speech sounds, and transcript of all dialogue combined with a means of achieving any outcomes that are achieved using interaction (if any) during the synchronized media

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

functionality

processes and outcomes achievable through user action

general flash and red flash thresholds

a sequence of flashes or rapidly changing image sequences where all three of the following [begin change]are true[end change]:

  1. there are more than three [begin change] General Flashes and / or more than three Red Flashes [end change] within any one-second period; and

  2. the flashing is below 50 Hz; and

  3. the combined area of flashes occurring concurrently [begin change] [begin delete]and contiguously[end delete] occupies more than a total of .006 steradians within any 10 degree visual field on the screen (25% of any 10 degree visual field on the screen) at typical viewing distance, where:[end change]

    [begin add]
    • A General Flash is defined as a pair of opposing changes in relative luminance of 10% or more of the maximum relative luminance where the relative luminance of the darker image is below 0.80; and where "a pair of opposing changes" is an increase followed by a decrease, or a decrease followed by an increase, and

    • A Red Flash is defined as any pair of opposing transitions involving a saturated red.

    [end add]
[begin add]

[begin add]Exception:[end add] Flashing that is a fine, balanced, pattern such as white noise or an alternating checkerboard pattern with "squares" smaller than 0.1 degree on a side does not violate the thresholds.

[end add]
[begin delete]

For the general flash threshold, a flash is defined as a pair of opposing changes in relative luminance of 10% or more and the relative luminance of the darker image is below 0.80. An "opposing change" is an increase followed by a decrease, or a decrease followed by an increase.

[end delete]
[begin delete]

For the red flash threshold, a flash is defined as any transition to or from a saturated red.

[end delete]
[begin change]

Note 1: For general software or 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 for standard screen sizes and viewing distances (e.g. 15-17 inch screen at 22-26 inches). (Higher resolutions displays showing the same rendering of the content yield smaller and safer images so it is lower resolutions that are used to define the thresholds.)

[end change]
[begin add]

Note 2: A transition is the change in relative luminance (or relative luminance/color for red flashing) between adjacent peaks and valleys in a plot of relative luminance (or relative luminance/color for red flashing) measurement against time. A flash consists of two opposing transitions.

[end add]
[begin add]

Note 3: The current working definition in the field for "pair of opposing transitions involving a saturated red" is where, for either or both states involved in each transition, R/(R+ G + B) >= 0.8, and the change in the value of (R-G-B)x320 is > 20 (negative values of (R-G-B)x320 are set to zero) for both transitions. R, G, B values range from 0-1 as specified in “relative luminance” definition. (Harding and Binnie 2002)

[end add]
[begin add]

Note 4: Tools are available that will carry out analysis from video screen capture.

[end add]
[begin add]

Note 5: No tool is necessary to evaluate for this condition if flashing is less than or equal to 3 flashes in any one second or greater than 50 Hz. Content automatically passes (see #1 and #2 above).

[end add]
[begin add]

Note 6: 50 Hz is used to coincide with the AC line frequency in Europe and other countries. However almost half of the population is susceptible to 50 Hz flashing whereas only 15 % are susceptible to 60 Hz. 75 Hz or higher is recommended where possible.

[end add]
human language

language that is spoken, written or signed ([begin change]through visual or tactile means [2264] [end change]) [begin delete]by humans [end delete]to communicate with [begin add]humans[end add] [begin delete]one another[end delete] [2139]

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

[begin add]

Note: idioms cannot be translated directly, word for word, without losing their (cultural or language-dependent) meaning. [2265]

[end add]
[begin delete]

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.

[end delete]

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.

incidental text in an image

text that is inconsequential to the meaning of the image

Example: In a photo of two men talking on a street corner, there is a sign on a store in the background.

information that is conveyed by color differences
[begin delete]

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

[end delete]
informative

for information purposes and not required for conformance

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

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

[begin change]

Note 1: A label is presented to all users whereas the name may be hidden and only exposed by assistive technology. In many (but not all) cases the name and the label are the same. [2200]

[end change]
[begin add]

Note 2: The term label is not limited to the label element in HTML. [2107]

[end add]
larger scale (text)

with at least 18 point or 14 point bold or font size that would yield equivalent stroke width for Chinese, Japanese and Korean (CJK) fonts [2175]

Note 1: Fonts with extraordinarily thin strokes or unusual features and characteristics that reduce the familiarity of their letter forms are harder to read, especially at lower contrast levels.

Note 2: Font size is the size when the content is delivered. It does not include resizing that may be done by a user.

[begin add]

Note 3: The actual size of the character that a user sees in dependent both on the author-defined size and the users display or user-agent settings. This Success Criterion is based on common pixel sizes available today. Users who have low vision would be responsible for choosing appropriate settings. [2267]

[end add]
legal commitments

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.

link purpose

nature of the result obtained by activating a hyperlink

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.

media alternative to text

media that presents no more information than is already presented in text (directly or via text alternatives) [2250] [2290]

Note: A media alternative to text is provided for those who benefit from alternate representations of text. Media alternatives to text may be audio-only, video-only (including sign-language video), or audio-video.

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 1: The name may be hidden and only exposed by assistive technology, whereas a label is presented to all users. In many (but not all) cases, the label and the name are the same.

Note 2: This is unrelated to the name attribute in HTML.

navigated sequentially

navigated in the order defined for advancing focus (from one element to the next) [begin change]using[end change] the keyboard

non-text content

any content that is not a sequence of characters that can be programmatically determined or where the sequence is not expressing something in human language

Note: This includes ASCII Art (which is a pattern of characters), [begin add]emoticons, [2268] [end add]leetspeak (which is character substitution), [begin add]and images representing text [2139] [end add].

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 resumed 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: Successful use of a series of Web pages on a shopping site requires users to view alternative products, prices and offers, 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 determiend (programmatically determinable) link context

additional information that can be programmatically determined from relationships with a link, combined with the link text, and presented to users in different modalities

[begin change]

Example: In HTML, information that is programmatically determinable from a link in English includes text that is in the same [begin delete]sentence, [end delete]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. [2245]

[end change]
[begin delete]

Example: A screen reader provides commands to read the current sentence when focus is on a link in that sentence.

[end delete]
[begin add]

Note: Since screen readers interpret punctuation, they can also provide the context from the current sentence, when the focus is on a link in that sentence. [2245]

[end add]
programmatically determined / programmatically determinable

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 markup language from elements and attributes that are accessed directly by commonly available assistive technology.

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

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

Note: Text is only purely decorative if the words can be rearranged or substituted without changing their purpose.

Example: The cover page of a dictionary has random words in very light text in the background.

real-time event

event that a) occurs at the same time as the viewing and b) is not completely generated by the content

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

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

relationships

meaningful associations between distinct pieces of content

relative luminance

the relative perceived brightness of any point, normalized to 0 for black and 1 for maximum white

Note 1: The relative luminance of an sRGB color is defined as L = 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

and RsRGB, GsRGB, and BsRGB are defined as:

  • RsRGB = R8bit/255

  • GsRGB = G8bit/255

  • BsRGB = B8bit/255

The "^" character is the exponentiation operator. (Formula taken from [sRGB] and [IEC-4WD]).

Note 2: Almost all systems used today to view Web content assume sRGB encoding. Unless it is known that another color space will be used to process and display the content, authors should evaluate using sRGB colorspace. If using other color spaces, see Understanding Success Criterion 1.4.3.

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

Note 4: Tools are available that automatically do the calculations when testing contrast and flash.

Note 5: A MathML version of the relative luminance definition is available.

relied upon (technologies that are)

the content would not conform if that technology is turned off or not supported

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.

satisfies a Success Criterion

the Success Criterion does not evaluate to 'false' when applied to [begin delete]all of the content on [end delete]the page

section

A self-contained portion of written content that deals with one or more related topics or thoughts

Note: A section may consist of one or more paragraphs and include graphics, tables, lists and sub-sections.

[2231]
set of Web pages

collection of Web pages that [begin add]share a common purpose and that are created by the same[end add] [begin delete]have a specific relationship to each other and that are created as a body of work by an[end delete] author, group or organization [2213]

Note: Different language versions would be considered different [begin add]sets of Web pages[end add] [begin delete]bodies of work[end delete].

[begin delete]
[begin delete]

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

[end delete]
[end delete]
sign language

a [begin delete]visual [end delete]language using combinations of movements of the hands and arms, facial expressions, [begin add]or[end add] [begin delete]and[end delete] body positions to convey meaning [2309]

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.

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.

synchronized media

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

technology (Web content)

[begin add] mechanism for encoding instructions to be rendered, played or executed by user agents [end add] [begin delete]markup language, programming language, style sheet, data format, or API [end delete] [2045]

[begin add]

Note 1: As used in these guidelines "Web Technology" and the word "technology" (when used alone) both refer to Web Content Technologies.

Note 2: Web content technologies may include markup languages, data formats, or programming languages that authors may use alone or in combination to create end-user experiences that range from static Web pages to synchronized media presentations to dynamic Web applications. [2045]

[end add]
[begin add]

Example: Some common examples of Web content technologies include HTML, CSS, SVG, PNG, PDF, Flash, and JavaScript. [2045]

[end add]
text

sequence of characters that can be programmatically determined, where the sequence is expressing something in human language

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

Example: An image of a chart is described in text in the paragraph after the chart. The short text-alternative for the chart indicates that a description follows.

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

user interface component

a part of the content that is perceived by users as a single control for a distinct function

Note: Multiple user interface components may be implemented as a single programmatic element. Components here is not tied to programming techniques but rather to what the user perceives as separate controls.

Example: An applet has a "control" that can be used to move through content by line or page or random access. Since each of these would need to have a name and be setable independently, they would each be a "user interface component."

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 presents content

Note 1: The user agent presents 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

[begin add]a non-embedded resource [begin delete]that is referenced by a URI[end delete] [begin add]obtained from a single URI using HTTP[end add] plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent [end add] [begin delete]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[end delete] [1948]

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

Note 2: For the purposes of conformance with these guidelines, a resource must be "non-embedded" within the scope of conformance to be considered a Web page.

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

Example 2: A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program lives entirely at http://example.com/mail, but includes an inbox, a contacts area and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar to display, but do not change the URL of the page as a whole.

Example 3: A customizable portal site, where users can choose content to display from a set of different content modules.

Example 4: When you enter "http://shopping.example.com/" in your browser, you enter a movie-like interactive shopping environment where you visually move about a store dragging products off of the shelves around you [begin add]and[end add] into a visual shopping cart in front of you. Clicking on a product causes it to be demonstrated with a specification sheet floating alongside.

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)

  • Roberto Castaldo (IWA / HWG)

  • Sofia Celic (Vision Australia)

  • Michael Cooper (W3C / MIT)

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

  • Bengt Farre (W3C Invited Expert)

  • Nikolaos Floratos (ANEC)

  • Loretta Guarino Reid (Google)

  • Katie Haritos-Shea (W3C Invited Expert)

  • Sean Hayes (Microsoft)

  • Andrew Kirkpatrick (Adobe)

  • Andrew LaHart (IBM)

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

  • Alex Li (SAP AG)

  • David MacDonald (E-Ramp Inc.)

  • Sorcha Moore (Segala)

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

  • Cynthia Shelly (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, Aries Arditi, Mike Barta, Sandy Bartell, Kynn Bartlett, Marco Bertoni, Harvey Bingham, Paul Bohman, Dick Brown, Doyle Burnett, Jonathan Chetwynd, Wendy Chisholm, Alan Chuter, David M Clark, Joe Clark, Tom Croucher, Nir Dagan, Daniel Dardailler, Geoff Deering, Don Evans, Alan J. Flavell, Becky Gibson, Al Gilman, Kerstin Goldsmith, Jon Gunderson, Emmanuelle Gutiérrez y Restrepo, Eric Hansen, Donovan Hipke, Bjoern Hoehrmann, Yvette Hoitink, Ian Jacobs, Phill Jenkins, Leonard R. Kasday, Ken Kipness, Andrew Kirkpatrick, Marja-Riitta Koivunen, Scott Luebking, Tim Lacy, Jim Ley, William Loughborough, Greg Lowney, Luca Mascaro, 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, Neil Soiffer, Jim Thatcher, Takayuki Watanabe, Jason White.

Appendix C: References

This section is informative.

CAPTCHA
The CAPTCHA Project, Carnegie Mellon University. The project is online at http://www.captcha.net.
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.
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.
WCAG10
Web Content Accessibility Guidelines 1.0, G. Vanderheiden, W. Chisholm, I. Jacobs, Editors, W3C Recommendation, 5 May 1999, http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/. The latest version of WCAG 1.0 is available at http://www.w3.org/TR/WAI-WEBCONTENT/.