Buzz Archives: Acid3
Acid3 receptions and misconceptions and do we have a winner?
Acid3 progress and what it really means.
By Lars Gunther | October 2nd, 2008
- Acid3 Passed in 23 Days!
-
On March 3, the Web Standards Project launched the Acid3 Browser Test. On March 26, two browser teams reported that their builds passed.
By Kimberly Blessing | April 7th, 2008
- Acid3: Putting Browser Makers on Notice, Again.
-
It's been three years since we told browser makes that we want to see them smile, but now we wanna hold their hand. Acid3 goes beyond the CSS tests implemented by Acid2 and tests a browser's DOM Scripting capability, as well as continuing to probe visual rendering of CSS, SVG and ...
By Drew McLellan | March 3rd, 2008
- Acid3 nearing completion
-
If you’re a fan of the Acid browser tests, you already know that Acid3 is in the works. It’s now in a “final review” state, so please check it out and submit your feedback.
By Kimberly Blessing | February 5th, 2008
- What’s the best test for Acid3?
-
Now that all the major browsers (and many minor ones) have pledged support for Acid2, Ian Hickson has moved on to preparing Acid3 — and you can help!
By Kimberly Blessing | January 16th, 2008
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)