Buzz Archives for February 2007
Failed and Flawed Accessibility Organisations
Mike Davies suggests that a number of accessibility related web sites and groups have failed to come up with the goods but still has high hopes for the WaSP ATF and WCAG Samurai.
By Ian Lloyd | Filed in Accessibility, Accessibility TF
- Notable web experts who are [x]: Women and non-Caucasians
-
[To those who are advocates of politically correct language, I apologize in advance for the blunt way in which I frame the role of race in this post.] Between Jason Kottke and WaSP founder Jeffrey Zeldman, the buzz is building yet again on the subject of conference panel composition… specifically, the ...
By Ben Henick | Filed in Emerging Technology, Outreach, Training, Web Standards (general)
- Petition the UK government for accessibility
-
The newspapers are reporting that the UK government is worried because an online petition on the 10 Downing Street website has more than a million signatures protesting about transport policy. Which reminded me that there's a petition on that site set up by Ian Fenn after the fiasco of the ...
By Bruce Lawson | Filed in Accessibility, Action, General
- What to do with WCAG 2?
-
To say that the W3C has been working on the Web Content Accessibility Guidelines (WCAG) version 2.0 for some time would be an understatement. The first public working draft for WCAG 2 was posted on January 25, 2001 - a full 6 years ago. Just less than a year ago ...
By Derek Featherstone | Filed in Accessibility, Web Standards (general)
- Talking with Microsoft about IE.next
-
I was in Redmond on Friday to meet with a few folks on the Internet Explorer team to discuss improvements we (as in the WaSP DOM Scripting and Microsoft task forces, and the JS Ninjas) wanted to see in IE.next.
By Aaron Gustafson | Filed in Browsers, DOM Scripting TF, Microsoft TF
- WaSP Announces the International Liaison Group (ILG)
-
A passion and hope I had during my years as Group Lead for the Web Standards Project was to reach out and create a network with peers around the globe. After all, this is the World Wide Web, right? It made sense to me that in order to advance our ...
By Molly E. Holzschlag | Filed in International Liaison Group, WaSP Announcement
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)