Buzz Archives for November 2005
Pandora’s Box (Model) of CSS Hacks And Other Good Intentions
This Thanksgiving I’ve decided it’s about time that I provided some more background and analysis on one of the things I am certainly unintentionally (in)famous for.
By Tantek Çelik | Filed in Browsers, Bugs, CSS, Education, HTML/XHTML, Microsoft, Outreach, Validation, W3C/Standards Documentation, Web Standards (general)
- The W3C Web API Working Group
-
W3C announces the Web API group to develop specifications that enable improved client-side application development on the Web.
By Jeremy Keith | Filed in DOM Scripting TF, W3C/Standards Documentation
- Beyond New Professionalism
-
In Molly's recent WaSP buzz, Web Standards and The New Professionalism she offers: Today, I want to express that I believe that this new professionalism means taking responsibility for the education of ourselves and each other, and ensuring that reversions like Disney Store UK never happen again. As part of the ...
By Holly Marie Koltz | Filed in Education, Education TF, Web Standards (general)
- Web Standards and The New Professionalism
-
Either you’re with us or against us: you know your craft (or you’re willing to learn) or you don’t. We’re in a process of defining a new professionalism for Web developers and designers.
By Molly E. Holzschlag | Filed in Accessibility, Web Standards (general)
- How to Create User-Friendly Pop-Under Ads
-
A pop-under ad that avoids the problem of blocking access to content.
By Christian Heilmann | Filed in DOM, DOM Scripting TF
- An Open Letter to Disney Store UK
-
Dear Disney Store UK, I would write this to you directly via your site feedback page but it is throwing Access database errors. The email appears to be down as well. So instead, I'm going to write my letter here in a public forum in the hopes that someone from your ...
By Molly E. Holzschlag | Filed in Accessibility, Bizarre, CSS, Design, HTML/XHTML
- IE7 Conditional Comments
-
In mid October, the IE Blog urged developers to stop using CSS hacks to workaround IE's problems, and start relying on Microsoft's proprietary conditional comments. I wrote up my thoughts about the new syntax, and it seemed practical enough considering that IE7 is looking to address most of the reasons ...
- WaSP Microsoft Task Force Update: Upcoming Products, XAML, Acid2, SXSW, and IE7 Revealed
-
The WaSP Microsoft Task Force held another face-to-face meeting with available members on Tuesday. We met in a Starbucks along the waterfront in rainy Seattle. While the setting might have been a bit predictable, the conversation was unique and at times, very encouraging. WaSPs at the meeting were DL Byron ...
By Molly E. Holzschlag | Filed in Authoring Tools, Browsers, CSS, Design, HTML/XHTML, Microsoft, Microsoft TF, 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)