Buzz Archives for August 2003
JAWS petition: just say no
There is increasing buzz in web designer circles about a petition to Freedom Scientific to produce a free version of their JAWS screen reader so that web designers can test their own web pages. JAWS is the leading screen reader on the market by a wide margin, and as ...
By Mark Pilgrim | Filed in Accessibility
- Assistive Device Behavior Charts
-
Over at Juicy Studio, Gez Lemon is developing a chart that shows the capabilities of various assistive devices commonly used by others to access web content. Included in this list of devices are JAWS for Windows, WindowEyes, IBM Home Page Reader, pwWebSpeak, and EmacSpeak(linux based).Gez announced the launch via his ...
By Holly Marie Koltz | Filed in Accessibility
- Validation just got better
-
Much clearer error explanations and a new "fussy parsing" mode are the major new features of the latest W3C Validator Beta release:“The big news in this version is internal support for custom and customizeable error explanations. This means an end to digging all over the net drying to figure out ...
By Matthias Gutfeldt | Filed in Validation
- An Accessibility Presentation For the People
-
For the People ("Bringing our world together, one voice at a time.") is a voice chat service that's worth checking out, not least because tomorrow they will be having a presentation by Gary Moulton from Microsoft's accessibility division. You will need to join to take part (and hopefully there's still time to ...
By Ian Lloyd | Filed in Accessibility
- New CSS Working Drafts
-
The W3C Working Groups on Wednesday released three new Working Drafts attached to CSS: the CSS3 Presentation Levels Module, meant to aid creation of outlines and slide presentations; the CSS Print Profile, for printing documents on low-cost hardware; and the CSS3 Syntax Module. Developer comments on these ...
By Ben Henick | Filed in CSS, W3C/Standards Documentation
- Aural Pleasure
-
In an eloquent radio interview for National Public Radio (NPR), Paul Ford of ftrain describes the evolution of Web standards. What's especially interesting is that Paul uses descriptions of human language as a metaphor for the merging of various Web standards. He carries the metaphor through very well, and as ...
By Molly E. Holzschlag | Filed in Web Standards (general)
- Postcard Tips
-
This is an alternative way to get the message out. Matt Robinsion developed the Wish You Were Here pages : a small site designed to advocate modern web design practice, with tips for web designers. Tips are arranged or grouped in categories from Design(Making your site attractive and ...
By Holly Marie Koltz | Filed in 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)