Buzz Archives for November 2008
Want to set up a Web Standards Café?
As a hat tip to Blue Beanie Day 2008 and in the spirit of helping spread the word of web standards, the International Liaison Group thought we'd celebrate by putting together a Web Standard Café Kit. Web Standards Cafés have been held all over the world bringing together people passionate about ...
By Henny Swan | Filed in Action, International Liaison Group, Outreach, WSCafe
- WCAG 2.0 resources
-
Here's a starter list of some resources to help transition to WCAG 2 from the world of WCAG 1, now the new standard goes to proposed recommendation status. This is just a starter list; please add other resources that you recommend in the comments. It would be great to have ...
By Bruce Lawson | Filed in Accessibility, W3C/Standards Documentation, Web Standards (general)
- WCAG 2 and mobileOK Basic Tests specs are proposed recommendations
-
WCAG 2 and the mobileOK Basic Tests specifications have been moved to "proposed recommendation status" by the W3C, which means that the technical material is complete and it has been implemented in real sites. WCAG 2 Shawn Henry writes of WCAG 2, Over the last few months, the Web Content ...
By Bruce Lawson | Filed in Accessibility, Browsers, General, Mobile, Validation, W3C/Standards Documentation, Web Standards (general)
The Web Standards Project is a grassroots coalition fighting for standards which ensure simple, affordable access to web technologies for all.
Recent Buzz
WCAG 2.0 is a W3C Recommendation
By Matt May | December 11th, 2008
After 9.5 years of work, the Web Content Accessibility Guidelines 2.0 have reached W3C Recommendation status. On behalf of the WaSP Accessibility Task Force, I’d like to welcome WCAG 2 officially into the pantheon of Web standards.
I think this tweet by caledoniaman sums up the level of anticipation:
WCAG 2.0 and a new Guns ‘n’ Roses album in the same year. What’s the world coming to.
Interesting comparison. They’ve each had about as many pre-releases. In any case, I can say, having spent over 8 years with it, that WCAG 2 is not as entertaining as Chinese Democracy. But I do think that it’s better equipped to stand the test of time.
If I had to pick one thing I’m most happy about, I’d say it’s that the HTML- and text-centrism in WCAG 1 is largely gone. In its place is a much more flexible (dare I say robust?) concept of accessibility-supported technology. So when newer technologies can show themselves to be directly accessible, they too can be used in WCAG 2-conformant content.
Over the years, many people have conflated “WCAG-conformant” with “accessible,” and that’s led to people making statements like: “Don’t use JavaScript–it’s inaccessible.” That’s bad for everyone, from users with disabilities who actually can work with JavaScript (which is to say, the vast majority), to Web designers and developers, to policymakers, to those developing new technologies.
With WCAG 2, “Don’t use x” is no longer valid. (Was it ever?) It is now up to you, the developer, to work on the direct accessibility of your content, no matter what technology you choose. I believe we’re about to experience a new wave of accessible design techniques, as a result.
But first, we need to flush “Don’t use x” out of our system. Some are accustomed to saying it about anything they’re not comfortable with. That’s only holding accessible design back. It’s time to learn what’s out there, today, and use it in everyday Web design. It’s time to make everyone’s Web more accessible. Have a look at the WCAG 2.0 Recommendation, and its supporting material. Then, start thinking about what a more accessible Web could be. We still have a lot of work to do.
Filed in Accessibility, Accessibility TF, W3C/Standards Documentation, Web Standards (general) | Comments (8)