Page is a not externally linkable
LiamMcGee - 10:43 am on Feb 18, 2009 (gmt 0)
A few notes to begin - Quite a few of the links in this thread are to earlier versions. For new, improved, tastier versions go see [w3.org...] This is one of a set of key docs... I recommend you start with [w3.org...] which contains all the guidelines, which links to [w3.org...] which goes deeper into each criterion, and then links through to the [w3.org...] which go into technology-specific guidance. There is also a handy diagram at [w3.org...] to show how it all fits together. If you find yourself needing to consider SEO for sites with Ajax and similar tech, you will also want to read [w3.org...] - plenty of interesting stuff to keep you going! W3C working groups collate all this info and publish it, but it relies on the wider web community for contributions, corrections and new techniques. The WCAG2.0 itself (http://www.w3.org/TR/WCAG20/) is now stable and won't change (in W3C jargon, it's 'normative'), however the supporting documents referenced above are all works in progress, and we need your help to continually improve them. You can comment on specific techniques at [w3.org...] and you can submit new ones at [w3.org...] You can keep an eye on what's going on by signing up to the Interest-Group mailing list (http://www.w3.org/WAI/IG/#mailinglist) or the Rss feed (http://www.w3.org/WAI/highlights/about-rss.html). If there are any points within the docs that need clarification, you could also post to this thread and I'll do my best to either answer your query or find someone who can. Cheers all Liam [Cards on the table - I was involved to some small degree in the production of both WCAG2.0 and in its supporting docs (one of many, many people). I'm part of the Education and Outreach Working Group at the W3C Web Accessibility Initiative. It's our job to make sure that these docs are easy to read, easy to use and explain things as clearly as possible. And to be incredibly pedantic about grammar and punctuation.]
Hi all - great to see the new WCAG docs causing a stir.