I’ve detected recently a note of frustration, and downright annoyance, amongst standardistas with the W3C. I receive the newsletter “W3C Weekly News” and see endless announcements from obscure working groups working on things that are bafflingly irrelevant to what I and most other web developers actually do, whilst the interminable process of proposals and working drafts on XHTML 2.0 and CSS 3 offers no hope of a final recommendation being anywhere in sight.
9 Ways to Misunderstand Web Standards is mostly what it says it is: tips for the web developer (most of which they should frankly know already) on how not to drink the Kool-Aid. But in that document, particularly “Misunderstanding #2: ‘We Need an Alternative Mobile Web on Top of the Existing Desktop Web’” and “Misunderstanding #8: ‘The Semantic Web is Just Around the Corner’”, there are problems picked out that are more the fault of the W3C than of any web developer. If anyone is advocating the use of the term “Mobile Web” it is the W3C. And the W3C’s work on the Semantic Web has so far issued in a bunch of standards that are so complicated and difficult to implement that I doubt anyone will. (Cory Doctorow’s wonderful, funny, and short, 2001 article Metacrap suggests it’s all a pipe dream anyway.) In the meantime Microformats are taking off and actually being used, a lot, and people who are more closely related to real world web development and are sick of how slow moving the W3C are are turning their attention to groups like WHATWG and WCAG Samurai (see next paragraph).
A case in point, Joe Clark’s article, To Hell with WCAG2, over on A List Apart makes for depressing reading. It’s taken the W3C’s Web Accessibility Initiiative (WAI) five years to draft the second version of the Web Content Accessibility Guidelines (WCAG), and in that time they’ve managed to come up with something almost totally incomprehensible:
In an effort to be all things to all web content, the fundamentals of WCAG 2 are nearly impossible for a working standards-compliant developer to understand.
What’s worse is that the document apparently contradicts widely accepted best practices of accessibility that standardistas have developed over the years. In fact it also contradicts some of the W3C’s other standards!