Cooperatively developed International standard

W3C Web Accessibility Initiative (WAI)
W3C process designed to:
- ensure broad public input, and
- encourage consensus development
Integrated Web accessibility standards suite
Policy for Authorized W3C Translations

Notes

These points are all aspects of WCAG 2.0 being a cooperatively developed International standard:

WCAG is developed by the W3C Web Accessibility Initiative (WAI)
WCAG is developed under the W3C process designed to:
- ensure broad public input, and
- encourage consensus development
WCAG is part of an integrated Web accessibility standards suite
Policy for Authorized W3C Translations

Another benefit is that WCAG, and other W3C specifications, can be translated and provided as an Authorized W3C Translation. This is especially important for non-English-speaking countries that want to adopt WCAG, rather than investing effort in developing a different set of guidelines.

Note to presenters: If you are short on time, depending on your audience, you may want to cut out this slide.

What WCAG 2 gives you

Advances from WCAG 1.0,
to WCAG 2.0

Notes

WCAG 2.0 builds on WCAG 1.0 and incorporates what we've learned to make WCAG more useful and more effective.

While the approach and a few of the requirements of WCAG 2.0 are a little different, the fundamental issues of Web accessibility are the same.

Most Web sites that meet ("conform to") WCAG 1.0 should not require significant changes in order to meet WCAG 2.0. Also, WCAG 2.0 is designed to be "backwards compatible" so that a site can meet both WCAG 1.0 and WCAG 2.0.

The differences between WCAG 1.0 and 2.0 are introduced in the "About WCAG 2.0" presentation at www.w3.org/WAI/presentations/WCAG20_about/ and the "How WCAG 2.0 Drafts Differ from WCAG 1.0" section of Overview of WCAG 2.0 Documents at www.w3.org/WAI/intro/wcag20.php#differs.

Let's look at how differences in approach and structure make WCAG 2.0 work better.

[decorative image description: hand holding silver platter with "WCAG 2.0 " on it]

(Image credit: Shawn Henry. Permission granted to use for other WCAG 2.0 presentations.)

What WCAG 2 gives you

Applies to more advanced technologies
-current, future, non-W3C

Notes

Applies to more advanced Web technologies - current, future, non-W3C WCAG 2.0 has been developed to be applicable to current technologies and to future technologies. It is designed to apply to W3C technologies, as well as technologies developed outside of W3C.

Let's look at how the different WCAG 2.0 documents provide that flexibility, as well as provide both general, technology-independent and specific guidance.

[decorative image description: hand holding silver platter with "WCAG 2.0 " on it]

WCAG 2

Formal Web standard,to become a "W3C Recommendation"
Stable
Technology-independent, broadly applicable,
Defines functionality required by users

Notes

WCAG 2.0 itself - the document at www.w3.org/TR/WCAG20 - is the formal Web standard draft, which is planned to become a "W3C Recommendation". It is the only document that defines what is required. (Other documents provide additional information, but are not part of the formal standard.)

How WCAG 2.0 documents provide a stable basis as well as flexibility

WCAG 2.0 goes through the formal W3C process and once it is completed, it is intended to be stable and relevant as technology changes over time, and apply as we develop new techniques for making the Web accessible. In order to do that, WCAG 2.0 itself needs to be broadly applicable and technology-independent. (It can't have details for specific technologies because things will change over time.)

WCAG 2.0 is not prescriptive about how to do things, but rather what functionality is needed for users. So WCAG 2.0 specifies what needs to be done for accessibility, and a related document tells how to do that.

WCAG 2.0 Guidelines and Success Criteria are technology-independent, and specific guidance is provided in the Techniques.

WCAG 2
- Formal Web standard,to become a "W3C Recommendation"
- Stable
- Technology-independent, broadly applicable,
- Defines functionality required by users

Techniques
- Formal Supporting document
- Updated
- Technology specific, HTML, CSS, etc.
- Provides "how-to" examples for developers

Notes

Techniques tell you how to meet WCAG 2.0

The Techniques for WCAG 2.0 is a supporting document that tells you how to develop accessible Web content that meets WCAG 2.0. It provides specific details:

Description
Examples, such as HTML code
Browser (User Agent) and Assistive Technology Support Notes
Resources
Tests

It also shows you common "failures", that is, some examples of how you can mess up and not meet the success criteria.

Where as WCAG 2.0 will be a stable document, the Techniques document can be updated as technologies and new techniques are developed. That's how WCAG 2.0 can provide a stable basis, with flexibility to adapt over time - through the Techniques.

Currently there are: General techniques, HTML techniques, CSS techniques, Server-Side Techniques, and others. More Techniques will be developed in the future.

WAI encourages development of techniques for non-W3C technologies as well, so there may be techniques for Flash or PDF or XYZ technology. While W3C WAI will not directly develop techniques for these other technologies, it will encourage their development.

Techniques are "informative"

Again, the Techniques are not part of the WCAG 2.0 standard, and you don't have to use them to meet WCAG 2.0. You could develop other ways to meet WCAG 2.0. This is another aspect of the flexibility of WCAG 2.0.

(By the way, if you develop new techniques to meet WCAG 2.0, you can submit them for review and inclusion in updates to the Techniques document.)

We'll look at the other informative supporting documents later.

[layout description: There are 2 columns to show comparison between WCAG 2.0 and the Techniques. The first column is headed "WCAG 2.0" and lists the bullets in gray text. The second column is labeled "Techniques" and lists bullets in black.]

WCAG 2 gives you

Clearer "success criteria,"
more precisely testable

(still need human Judgement)

Notes

WCAG 2.0 builds on WCAG 1.0 and incorporates what we've learned to make WCAG more useful and more effective.

While the approach and a few of the requirements of WCAG 2.0 are a little different, the fundamental issues of Web accessibility are the same.

Let's look at how differences in approach and structure make WCAG 2.0 work better.

[decorative image description: hand holding silver platter with "WCAG 2.0 " on it]

(Image credit: Shawn Henry. Permission granted to use for other WCAG 2.0 presentations.)

Testable Example

WCAG 1.0 Checkpoint
- 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits. . .

Notes

[read slide text]

This sounds good, however, if we look at a sample Web page, is it precise enough that we can determine whether or not the Web page meets this checkpoint?

example web page described below

Notes

Here is an example Web page. The main navigation down the left has black text on red background. Along the top are right is small black text and larger black text on light red background. In the middle is large red text on white background. There is small red text on a white background, gray background, and red background.

Do these areas meet WCAG 1.0 Checkpoint 2.2 for color contrast? While the checkpoint provides important guidance, it is not specific enough to clearly determine whether all of the color contrast on this page meets WCAG 1.0 or not.

Let's look at the similar WCAG 2.0 success criteria...

Note to presenters: Consider customizing this image. Find one with questionable color contrast from your organization or that would resonate with your audience.

Note to presenters: Remember to describe the pertinent parts of the image for people who are blind or otherwise cannot see it.

Testable Example

WCAG 1.0 Checkpoint
- 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits. . .
WCAG 2.0 Success Criteria
- 1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 5:1. . .
(from the April 2008 Draft)

Notes

The WCAG 2.0 success criteria are more specific and testable. It defines a precise contrast ratio, and there are tools that you can use to determine the contrast ratio.

That is an example of how WCAG 2.0 is more precisely testable that WCAG 1.0 is.(Remember that some success criteria need human evaluation, and cannot be evaluated only with automated tools.)

UPDATE note: Check the latest WCAG 2.0 Draft at www.w3.org/TR/WCAG20/ to get the current wording of the relevant success criteria

WCAG 2 gives you

Adaptable, flexible
for different situations,
and developing
technologies and techniques

Notes

WCAG 2.0 is adaptable and flexible, for different situations, and developing technologies and techniques.

We described earlier how WCAG 2.0 is flexible to apply to Web technologies now and in the future through WCAG 2.0 itself and the Techniques. Let's look at some other ways that WCAG is flexible and adaptable.

Next let's look at examples of what WCAG 2.0 allows that WCAG 1.0 did not; that is, where WCAG 2.0 is less restrictive than 1.0.

[decorative image description: hand holding silver platter with "WCAG 2.0 " on it]

(Image credit: Shawn Henry. Permission granted to use for other WCAG 2.0 presentations.)

More design flexibility

WCAG 1.0
Until user agents allow users to...
- 7.1 ... avoid causing the screen to flicker.
- 7.2 ... avoid causing content to blink...
- 7.3 ... avoid movement in pages.
WCAG 2.0 allows more movement within defined parameters
- 2.2.2 Blinking...
- 2.2.3 Pausing...
- 2.3.1 Three Flashes or Below Threshold...
- 2.3.2 Three Flashes...

Notes

WCAG 1.0 limited movement used in web pages, through the following checkpoints:

7.1 Until user agents allow users to control flickering,avoid causing the screen to flicker.
7.2 Until user agents allow users to control blinking,avoid causing content to blink...
7.3 Until user agents allow users to freeze moving content,avoid movement in pages.

WCAG 2.0 allows more movement, within defined parameters

2.2.2 Blinking: Content does not blink for more than three seconds, or a method is available to stop all blinking content in the Web page.
2.2.3 Pausing: Moving, blinking, scrolling, or auto-updating information can be paused by the user unless it is part of an activity where timing or movement is essential. Moving content that is pure decoration can be stopped by the user.
2.3.1 Three Flashes or Below Threshold: 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.
2.3.2 Three Flashes: Content does not contain anything that flashes more than three times in any one second period.

Note to presenters: Customize how much you use this example, and how much text you have on the slide. For longer presentations to designers who are familiar with WCAG 1.0, you might want to include all these details. For short presentations, it might be best to cover it much less, if at all.

Scripting allowed!!

Notes

Back in 1999, in the days of WCAG 1.0, there was very little support for scripting in common assistive technologies, such as screen readers. You pretty much couldn't design a site that relied on scripting and was accessible. That's changed now. All of the major browsers and assistive technologies support scripting. So now there are ways where you can use scripting, and even in some cases use it to enhance accessibility.

There are definitely some accessibility issues depending on what you do with scripting, but it's no longer something that always impairs accessibility; now it's actually encouraged in some cases.

There are several resources on the Web that provide additional guidance on accessibility and scripting.

Note to presenters: For some audiences, you might want to explain that scripting is an issue under the "Perceivable"principle. In the past, content provided through scripting was not always perceivable to uses with disabilities.

Scripting techniques

Providing client-side validation and alert
Providing a script that warns the user a time limit is about to expire
Using progressive enhancement to open new windows on user request
Using functions of the Document Object Model (DOM) to add content to a page
. . .

In fact, there are specific scripting techniques for WCAG 2.0, including: [items listed on slide] And there will probably be more in the future.

Reference: Client-side Scripting Techniques for WCAG 2.0 http://www.w3.org/TR/WCAG20-TECHS/client-side-script.html

Note to presenters: This is a particular area that you might want to cover in more or less detail depending on your audience. You can get more about scripting techniques from links in the Techniques document contents list as well as other (non-W3C WAI) resources on the Web (however, note that they may be out of date or incorrect).

Flexibility for Rich Internet
applications (Ajax, DHTML)

WAI-ARIA:
Accessible Rich Internet Applications Suite
- For example, accessible and highly usable
  expanding and collapsing menus/tree
  controls/nav bars
- Techniques for meeting WCAG 2.0

Notes

WCAG 2.0 is being developed in coordination with related work on making accessible the more advanced features of dynamic content and rich Internet applications developed with Ajax, DHTML, and other Web technologies. That work is the Accessible Rich Internet Applications Suite, WAI-ARIA, which is being developed by the W3C WAI Protocols and Formats Working Group.

A primary focus of ARIA is providing information about user interface controls to assistive technologies, e.g.: Menus, tree controls, navigation bars, Role and state

With WAI-ARIA you can make rich Internet applications much more accessible and usable by people with disabilities. For example, for a menu in a tree control, ARIA defines how to make the information about the nodes available to assistive technologies, so that users can to tell where they are in a tree, expand and collapse nodes, and get around and navigate a lot more effectively. Keyboard access is a key aspect of WAI-ARAI.

Note to presenters: This is a particular area that you might want to customize to cover in more or less detail depending on your audience. You might want to only mention it briefly and then delete the next couple of slides. You can learn more from the WAI-ARIA Overview at www.w3.org/WAI/intro/aria.php.

Please use "WAI-ARIA" on first reference, especially in print. It's OK to use just "ARIA" when you're using it repeatedly.

Adaptability through "accessibility-supported technologies"

Notes

Another way that WCAG 2.0 provides flexibility and adaptability for different situations today and as technology changes over time is through what's called "accessibility-supported technologies".

Accessibility-supported technologies are Web technologies (HTML, CSS, etc.) that an author can use to create accessible Web content.

We won't cover accessibility-supported technologies here; it is covered in other WAI material.

UPDATE Note: Make sure to check for updated information on accessibility-supported technologies. WAI may have new material that explains it in a different way. One place to check is the Overview of WCAG 2.0 Documents at http://www.w3.org/WAI/intro/wcag20 and the WCAG 2 FAQ at http://www.w3.org/WAI/WCAG20/wcag2faq.html

What WCAG 2 gives you

Extensive supporting materials,
practical implementation guidance

Notes

Let's look at how this compares to WCAG 1.0

[decorative image description: hand holding silver platter with "WCAG 2.0" on it]

WCAG 2.0 technical documents

WCAG 2.0
Understanding
Techniques

Supporting document
"Informative"
Reference manual

Notes

Techniques
With WCAG 1.0 there are some techniques. The WCAG 2.0 techniques are much more robust and comprehensive, and they include tests.

Understanding
In WCAG 1.0, brief descriptions are included in the main WCAG 1.0 document under each guideline. With WCAG 2.0, extensive guidance is provided for each guideline and success criteria in a new document, called Understanding WCAG 2.0: A guide to understanding and implementing WCAG 2.0.

With WCAG 1.0, many people had questions on how to interpret it and implement it, such as: What does this checkpoint mean? How do we implement it? How does this help people with disabilities?

With WCAG 2.0, that information is provided in the Understanding document. It tells you the intent of each guideline and success criteria and how it helps people with disabilities; provides examples; and lists related resources, such as the tools to test for color contrast that we talked about earlier.

Note that the Understanding doc is not intended to be read cover to cover; instead, it's more like a reference manual. It's the book on WCAG 2.0, from the Working Group itself.

That's a lot of information. We have something else that's incredibly useful for getting around it all...

[image description: 3 boxes stacked vertically and labeled Understanding, WCAG 2.0, Techniques.]

How to Meet WCAG 2.0

"A customizable quick reference to
WCAG 2.0 requirements (Success Criteria)
and techniques"

Lists the WCAG 2.0 requirements
Provides summary information from the other documents
Links to details

Notes

How to Meet WCAG 2.0, the customizable "Quick Reference"!

How to Meet WCAG 2.0 lists the requirements for WCAG 2.0, provides summary information from the other documents, and links to details.

How to Meet WCAG 2.0 includes the guidelines and success criteria from the normative WCAG 2.0 document.

Most people will use How to Meet WCAG 2.0 as the main tool for using WCAG 2.0.

Note to presenters: How to Meet WCAG 2.0 is a key tool that should be mentioned in almost all presentations.

Quick Reference screen shot

Screen shot of the Customization Tool for the Quick Reference with check boxes to choose various technologies, levels and sections

Notes

You can customize How to Meet WCAG 2.0 for your specific situation. You can turn off things like [multimedia and SMIL (Synchronized Multimedia Integration Language) and scripts], and select which technologies you're using. You can also select which level success criteria you want included.

You can use these options to filter what's shown in the checklist to make it shorter with only the items relevant to your project.

Check other material for more information on using How to Meet WCAG 2.0 and other WCAG 2.0 documents.

UPDATE note: The customization options might have changed since this screen capture.

[image description: Screen shot of Customizing this Quick Reference section. Text is:

Technologies: [with the following checkboxes]

HTML techniques (always shown)
Show CSS techniques and failures
Show Synchronized Media techniques and failures
Show SMIL techniques and failures
Show Client-side Scripting techniques and failures
Show Server-side Scripting techniques and failures
Show WAI-ARIA techniques and failures

Levels: [with the following checkboxes]

Show Level A Success Criteria
Show Level AA Success Criteria
Show Level AAA Success Criteria.

Sections: [with the following checkboxes]

Show Sufficient Techniques and Failures
Show Advisory Techniques

(end description)]

Intro and discussion documents

Overview
WCAG 2 FAQ
Issues, Changes

Notes

In addition, there are documents that introduce WCAG 2.0 and discuss current issues.

Overview of WCAG 2.0 Documents provides an important foundation for understanding the different WCAG 2.0 documents. It explains in text a lot of what we're covering here and more.
(If you see someone linking only to the technical documents themselves, such as in a blog post, it would be great if you would encourage them to link to Overview first. That way people can get the foundational information about the different documents, such as How to Meet WCAG 2.0, instead of potentially getting caught up in the technical document.)
WCAG 2 FAQ, which is updated fairly regularly, addresses questions such as: When will WCAG 2.0 be done? What is the current status? When should I start using WCAG 2.0?
Issues and Changes to WCAG 2.0: A Summary of Issues, Revisions and Rationales on WCAG 2.0 Working Drafts addresses things like validity, baseline, coverage of people with cognitive disabilities and the accessibility issues. If you've been following WCAG 2.0 development and are interested in how the issues were addressed, I encourage you to read that document.
Note to presenters: For shorter presentations, you might want to delete this slide and mention these resources with the next slide.

[image description: 3 boxes arranged vertically and labeled "Overview," "WCAG 2 FAQ," and "Issues, Changes".]

START HERE with WCAG 2.0

Learning about it
- Overview
- www.w3.org/WAI/intro/wcag20.php

Using it
- Quick Reference
- www.w3.org/WAI/WCAG20/quickref/

Notes

Please help spread the word about the different WCAG 2.0 documents and the best place to start. First, to learn about WCAG 2.0, start with the Overview document. And for using WCAG 2.0, you'll probably want to start with How to Meet WCAG 2.0.

[decorative image description: Arrows show 2 paths from "START HERE with WCAG 2.0": one leads to "Learning about it" and the other leads to "Using it".]

Questions?

WAI home page
www.w3.org/WAI/

Notes

There are many resources on the WAI website to answer your questions. For example,

About WCAG 2.0 presentations - videos and presentation materials
Introduction to Web Accessibility
Developing a Web Accessibility Business Case for Your Organization
How WAI Develops Accessibility Guidelines through the W3C Process

Check out the WAI Resources list at www.w3.org/WAI/Resources/Overview

There is also a WAI Interest Group mailing list where you can ask questions of the Web accessibility community.

archive: lists.w3.org/Archives/Public/w3c-wai-ig
to subscribe: www.w3.org/WAI/IG/Overview.html#Uselist

Note to presenters: Ideally you would provide a handout with the links listed. Make sure to have accessible formats as needed, e.g., large print and Braille or electronic versions. If not, make sure to leave the resources displayed long enough for people to copy down the information. Also, be prepared to read it all out slowly for people who cannot see the screen.

Source Material

Benefits of WCAG 2.0 Web Content Accessibility Guidelines

W3C WAI Education and Outreach Working Group, Shawn Henry editor

www.w3.org/WAI/presentations/WCAG20_benefits/

Note that this presentation is based on material provided by the W3C WAI Education and Outreach Working Group. The source presentation is Benefits of WCAG 2.0, edited by Shawn Henry, available from www.w3.org/WAI/presentations/WCAG20_benefits/

Note to presenters: Remember to credit this presentation as source material for your presentation, as described in Instructions for the "About WCAG 2.0" Presentation at www.w3.org/WAI/presentations/WCAG20_benefits/. In handouts, include the reference:

WCAG 2.0 Web Content Accessibility Guidelines Update, S.L. Henry, et al., ed., World Wide Web Consortium (MIT, ERCIM, Keio), September 2007. www.w3.org/WAI/presentations/WCAG20_benefits/

Benefits of WCAG 2.0

Cooperatively developed international standard
Applies to more advanced Web technologies
- current, future, non-W3C
Clearer criteria, more precisely testable
Adaptable, flexible for different situations,
and developing technologies and techniques
Extensive supporting materials,
practical implementation guidance

Notes

To review what we discussed: [text in slide]

[decorative image description: hand holding silver platter with "WCAG 2.0" on it]

WCAG 2
Benefits you!

Notes

About this presentation

Please read the
Instructions for the "About WCAG 2.0" Presentation at
www.w3.org/WAI/presentations/WCAG20_about/
for an introduction, tips, and permission to use.

Notes

[slide is hidden in some software so it will not display]

[DRAFT] Benefits of WCAG 2.0 Presentation

IMPORTANT: Instructions

Notes

Benefits of Web Content Accessibility Guidelines WCAG 2.0

Notes

WCAG 2.0 is...

Notes

WCAG 2 gives you

Notes

Who Developes WCAG

Notes

How WCAG is developed, Stage 1

Notes

Integrated Accessibility Guidelines

Notes

Cooperatively developed International standard

Notes

What WCAG 2 gives you

Notes

What WCAG 2 gives you

Notes

Notes

Notes

WCAG 2 gives you

Notes

Testable Example

Notes

Notes

Testable Example

Notes

WCAG 2 gives you

Notes

More design flexibility

Notes

Scripting allowed!!

Notes

Scripting techniques

Flexibility for Rich Internet applications (Ajax, DHTML)

Notes

Adaptability through "accessibility-supported technologies"

Notes

What WCAG 2 gives you

Notes

WCAG 2.0 technical documents

Notes

How to Meet WCAG 2.0

Notes

Quick Reference screen shot

Notes

Intro and discussion documents

Notes

START HERE with WCAG 2.0

Notes

Questions?

Notes

Source Material

Benefits of WCAG 2.0

Notes

WCAG 2 Benefits you!

Notes

About this presentation

Notes

Benefits of
Web Content Accessibility Guidelines
WCAG 2.0

Flexibility for Rich Internet
applications (Ajax, DHTML)

WCAG 2
Benefits you!