standards wcag

WCAG 2.0 Last Call Working Draft

If you haven’t already heard, the W3C WAI is has announced the final review of WCAG 2.0. But before you submit your clever suggestions, be sure to review the WCAG 2.0 Documents.

Other folks blogging about the WCAG 2.0 final review:

guidelines podcast wcag

Podcast #55: WCAG Samurai

The WCAG Samurai is an “independent group of developers convened in 2006” and headed up by Joe Clark, accessibility guru. In this podcast, Dennis and Ross discuss the WCAG Samurai’s errata to the W3C’s WCAG 1.0 web accessibility guidelines. This includes:

  • what it is and if we should use it
  • discussing the 12 main points
  • which WCAG 1.0 Priority 3 guidelines to ignore

Download Web Axe Episode 55 (WCAG Samurai)

The WCAG 1 + Samurai Guidelines

  1. Provide equivalent alternatives to auditory and visual content
  2. Don’t rely on colour alone
  3. Use markup and stylesheets and do so properly
  4. Clarify natural-language usage
  5. Create tables that transform gracefully
  6. Ensure that pages featuring new technologies transform gracefully
  7. Ensure user control of time-sensitive content changes
  8. Design for device-independence
  9. Use interim solutions
  10. Use W3C technologies and guidelines
  11. Provide context and orientation information

Related Links


expert podcast wcag

Podcast #50: Analysis of WCAG 2.0

The lastest version of the W3C’s Web Content Accessibility Guidelines is discussed by Dennis, Ross, Jared Smith and Joe Dolson.

Download Web Axe Episode 50 (Analysis of WCAG 2.0)



  • Refresh Detroit, June 20th – Catherine Hayes Inner Circle Media, Ruby on Rails
  • Refresh San Fran? Refresh San Jose? Who’ll start one?

Questions/Topics Include

  • Do you feel that (good) progress is being made after the concerns voiced about a year ago?
  • Do you feel that “Success Criteria” make more sense than the previous “Priority levels/Checkpoints”?
  • There is still a “loophole” for an alternative accessible page. Is this acceptable?
  • Valid code is still not a requirement (politically motivated?). Should it be?
  • Do you think that the WCAG 2 is too broad and vague?
  • Is the quick reference an acceptable method for developers to understand WCAG2 if the actual documents are to complex?

WCAG 2.0 Links

news wcag

For Review: Updated WCAG 2.0 Documents

The Web Content Accessibility Guidelines 2.0 (WCAG 2.0) Working Draft documents were updated 17 May 2007. These documents incorporate resolutions to comments from the 2006 Last Call Working Draft. The Web Accessibility Initiative (WAI) encourages you to review the WCAG 2.0 Working Draft and submit any new comments. Please see the additional information in:

Please send comments by 29 June 2007.

articles expert interview standards wcag

Interview with Judy Brewer on WCAG 2.0

What’s the heck’s going on with WCAG 2.0? Last I heard turned out to be an April Fool’s joke!

Thankfully, Jared Smith of The Web Standards Project (and WebAIM) has interviewed Judy Brewer on the subject. Judy is the Director of the Web Accessibility Initiative (WAI) at the World Wide Web Consortium (W3C). WCAG 2.0 is apparently in the second stage of four. Although moving very slowly, it seems many of the large concerns of the development community are being address (such as the complex language of the first draft).