• Overview of WCAG 2.0 Documents
• How to Meet WCAG 2.0 (Customisable quick reference)
• Transitioning from WCAG 1.0 to WCAG 2.0
• Accessible Forms using WCAG 2.0

If you are interested to help them, you are warmly welcome to do so by building your content following the recommended guidelines outlined here.

And you are waiting for… what? Sign in.

• Part one builds a resolution-dependent page layout and demonstrates the use or a reset style sheet.
• Part two demos the use of CSS selectors and dives into the realm of scripting and adds some neat effects using the jquery library.
• Part three covers the integration of ajax technology and starts up with a shout-out on resolution dependence.
• The fourth and last part in this series is about testing for extensibility with 8 benchmarks to thoroughly bulletproof your site.

Overall this is a carefully written Tutorial worth spending time on. Thumbs up!

So the flames have extinguished? Read more on the subject.

The reason for the update is because version 1.0 was originally published back in 1999 and in that time both web browsers and assisting technologies have evolved considerably.

Note that the WCAG Samurai Errata is not a standalone document, you should really use it as an update along the original WCAG 1.0 guidelines.

Also note that there is a Web Content Accessibility Guidelines 2.0 working draft available, lastly updated in December 2007, which you should consider to use over the 1.0 counterpart.

<meta http-equiv="X-UA-Compatible" content="IE=7;FF=2" />

… would say that our page was tested and works on IE version 7 and Firefox version 2, for example.

Now, the problem I see here is in actual browser support for backwards-compatibility rendering. Do we really believe that once IE 10 is out, our IE=7 will still work? If you ask me, this is a recipe for failure.

Read more on the subject on alistapart.com, for some enlightening articles on the subject.