Buzz Archives for February 2006
Kudos to Michigan State
Michigan State University launched a redesign of its Web site, yesterday. Designed and developed with best practices that follow Web Standards and Web Accessibiity, the university Web site looks good and validates to the XHTML strict doctype. The redesign involved the teamwork of the MSU Libraries, Computing, and ...
By Holly Marie Koltz | Filed in Education, Education TF, General
- Quick Explanation of the Object Literal
-
Christian Heilmann explains the object literal JavaScript syntax.
By Christian Heilmann | Filed in DOM, DOM Scripting TF
- NFB vs. Target in perspective
-
Since the National Federation of the Blind sued Target Corp. for the inaccessibility of its Web site, many people have taken sides, vilifying Target and/or lionizing NFB in turn. I think it's too early for that, if it's necessary at all. In terms of US law, this was a suit ...
By Matt May | Filed in Accessibility, Legal
- Yahoo Releases its User Interface Library
-
Graded Browser Support, design patterns library, user interface library. Its been a busy day over at the Yahoo Developer Network.
By Jeremy Keith | Filed in Authoring Tools, DOM, DOM Scripting TF
- Yahoo! Developers: Setting a Standard for the New Professionalism
-
In an article published Monday, February 13, 2006, Yahoo! Senior Web Developer Nate Koechley outlines the Yahoo! concept of Graded Browser Support. The approach is a work of art so beautiful and sensible it literally made me weep for joy. In light of ongoing discussion regarding a new professionalism for Web ...
By Molly E. Holzschlag | Filed in Browsers, Web Standards (general)
- Staying on Target
-
A lot can happen in 24 hours. In the time since yesterday's post, Taking Aim at Target(.com), the Target.com web site has been changed to address at least the image based submit buttons on the Target Pharmacy sign in page. It no longer requires a mouse click to submit the forms. They ...
By Derek Featherstone | Filed in Accessibility, Legal
- Taking Aim at Target(.com)
-
With a name like Target, you would almost think they would have seen it coming, wouldn't you? The US National Federation of the Blind (NFB) has brought legal action against Target corporation (a major US-based discount retailer which operates more than 1,300 stores in 47 states) because their web site is ...
By Derek Featherstone | Filed in Accessibility, Legal
!importantFixed in Later IE7 Releases-
It was brought to my attention today that the IE7 Beta 2 Preview wasn't honoring the role of the !important declaration and as such was causing alternative box model hacks to fail. !important is important for several important reasons. First is the very reason !important exists, which is to ...
By Molly E. Holzschlag | Filed in Browsers, Bugs, CSS, Microsoft
- AJAX for Eclipse
-
IBM, Mozilla, Zimbra and Dojo announce a project to develop AJAX widgets for Eclipse.
By Chris Kaminski | Filed in Authoring Tools, DOM Scripting TF
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)