WCAG 2.0 at @media
Just a quick heads-up - as readers of this site may be (or, more hopefully, are) aware, Patrick, myself, Gez Lemon and Andy Clarke are hosting a panel on WCAG 2.0:
In this panel, we'll try and get to grips with the philosophy, the content, the good, the bad, and the controversies of the second edition of the Web Content Accessibility Guidelines and look at how they impact on areas such as design, or the use of widgets.
Well, that's what the blurb says, and we've certainly got our ideas about what to cover but we're interested to get some feedback in advance - or rather some questions in advance - that you might like to hear us cover on the day itself. If you have a comment, be that a simple question, something that you'd like clarifying or a rant about your personal pet hate with WCAG 2.0, please add it here and we'll do our best to incorporate it on the day. Over to you ...
5 Comments:
I'm planning to update my WCAG 2 article to take into account the latest version of the documentation which I must say looks much more readable than the november working draft. When I've had a proper chance to re-review I'll drop a more serious line with anything of particular interest.
Only thing so far is I'd definitely mention technology baselines as it's an entirely new idea from WCAG 1.0.
If a site currently satisfies WCAG 1 to a specified level will it automatically satisfy WCAG 2 to the same level? If not can you suggest what the best strategic approach might be for reaching that level under WCAG 2?
Well, I'm still in the LONG process of trying to get through the 600+ pages of WCAG 2.0 and supporting documentation, so more questions may come later. But therein lies my biggest issue - how do we expect propogation and implementation of WCAG 2.0 when perhaps the only people on the planet that have and will ever read it all are those that wrote it.
I know there will be lots of "WCAG 2.0 for the Rest of Us" type articles, but I see the sheer mass and complexity of the new guidelines as leading to their downfall.
Considering WCAG1.0 effectively banned the use of JavaScript, how does WCAG 2.0 tackle it, and how does the idea of baselining affect AJAX applications.
Why have they removed valid code from the checkpoints (now - success criteria)
Post a Comment
Links to this post:
Create a Link
<< Home