Buzz Archives for March 2008
Announcing the Adobe Task Force
Today WaSP announced that the Dreamweaver Task Force will be renamed the Adobe Task Force to reflect a widened scope.
By Stephanie Sullivan | Filed in Adobe TF, Authoring Tools, Dreamweaver TF, Outreach, WaSP Announcement
- Annual Public WaSP Meeting at SXSW
-
All SXSW Interactive attendees are welcome to attend WaSP's annual public meeting which will be held tomorrow, Monday, March 10. The session runs from 5:00 pm to 6:00 pm (Central Daylight Time) and will be held in room 19AB (Level 4). Everyone is welcome to join our Meebo chat as ...
By Kimberly Blessing | Filed in General, Outreach
- Street Team: Make Your Mark
-
The WaSP Street Team launches its first community project: bookmarks which you can place in libraries, schools, and bookstores to help signal to readers that the material is out of date.
By Glenda Sims | Filed in General, Outreach, Street Team, Training, Web Standards (general)
- Microsoft releases the first IE8 Beta
-
In other news, the ACID2 test page has become overwhelmed.
By Aaron Gustafson | Filed in Browsers, Microsoft
- Microsoft rethinks IE8’s default behavior
-
Perhaps it was our complaining or perhaps it was a reconsideration of its own interoperability principles, but Microsoft has decided to change its course on IE8 and will opt-in to its new standards mode by default.
By Aaron Gustafson | Filed in Browsers, Microsoft, Microsoft TF
- 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 | Filed in Acid3, General, WaSP Announcement
- What do you want from CSS3 - one week left
-
(Polish translation) As part of the outreach work we're doing in partnership with the W3C's CSS Working group, we invited all web professionals to tell the Working Group what they want from the next version of the spec. As the Working Group's face-to-face meeting is at the end of March, we will ...
By Bruce Lawson | Filed in Action, CSS, Design, W3C/Standards Documentation
- Yahoo! UK & Ireland TV Listings site relaunches, chock full of standards
-
While it's become much more common than, say, a couple years ago, it still deserves mention whenever a high-profile website relaunches with exemplary web development practices. Such is the case with the Yahoo! UK & Ireland TV Listings site, which this past week relaunched with some of the leanest and ...
By Faruk Ateş | Filed in General, 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)