Buzz Archives for August 2007
The good, the bad, and the ugly - iPhone edition
The iPhone has had a tremendous impact on the web, eliciting impassioned testimony from supporters and detractors alike. What does it mean for the web standards? What about the rest of the mobile web? And (how) should we design for it?
By Aaron Gustafson | Filed in Browsers, Emerging Technology, Mobile, Opinion
- Amazon allowing CSS customization
-
In a fairly interesting move, Amazon is now allowing aStores to be customized using CSS.
By Aaron Gustafson | Filed in CSS, Design
- Business Week: Jeffrey Zeldman: King of Web Standards
-
This week, Business Week has published a Special Report on WASP co-founder Jeffrey Zeldman.
By Andy Clarke | Filed in General, Web Standards (general)
- Obstacles to Accessible Flash
-
Adobe Flash can often get a bad rap from the standards community, but the reality is that there are many situations where Flash is the most appropriate tool for the job. As well as just being the best technology for some applications, the Flash Player also enjoys near ubiquity in ...
By Drew McLellan | Filed in Accessibility, 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)