Today W3C WAI published WCAG 2.0 as a "W3C Proposed Recommendation". This means that the technical material of WCAG 2.0 is complete and it has been used successfully in real websites. Up next: final publication as a Web standard "W3C Recommendation", which we expect in December!
Over the last few months, the Web Content Accessibility Guidelines (WCAG) Working Group has been going through a process to ensure that WCAG 2.0 can be implemented. Developers and dsigners from around the world gave WCAG 2.0 a "test drive" in their own Web content.
The result: Successful implementations in a wide range of sites including education, commerce, government, and a blog; in languages including Japanese, German, English, and French; and using a wide range of technologies including scripting, multimedia, Flash, and WAI-ARIA. You can get the nitty-gritty details from the Implementation Report.
We learned more about how people use WCAG 2.0 and got additional feedback that resulted in a few changes from the previous publication.
Now that WCAG 2.0 technical material is stable and is proven implementable, there’s one more step: submit WCAG 2.0 Proposed Recommendation to W3C Members for final review and endorsement. That takes us into December.
Over the next few weeks we’ll also be updating existing WCAG materials and providing new materials to help transitioning to WCAG 2.0; for example, a printable version of WCAG 2.0 at a Glance and more WCAG 2.0 presentations.
But you don’t need to wait for any of that. There are a lot of reasons to start implementing WCAG 2.0 right away. See "What are the benefits of using WCAG 2.0?" in the WCAG 2 FAQ.
Note that the best place to start with WCAG 2.0 is not necessarily the technical standard itself. Instead start with:
- Overview of WCAG 2.0 Documents
- How to Meet WCAG 2.0: A customizable quick reference to WCAG 2.0 requirements…
As always, we welcome suggestions for improving these supporting documents, and we encourage translations. Each document has an e-mail address for comments, which is often in the footer, e.g., "Feedback welcome to email@example.com."
Thanks for all the support moving WCAG 2.0 towards completion. We look forward to seeing more websites and web applications meet WCAG 2.0.