Make it work!
In web technology, as in fashion, one day you’re in, and the next day you’re out.
In a Fashion Edition of A List Apart, For People Who Make Websites, I take a fair and balanced look at Web 2.0. And Colin Lieberman tells how to pull AAA accessibility out of your hat when the W3C kills acronym, Microsoft ignores abbr, and JAWS hates dfn.
The Web Content Accessibility Guidelines (WCAG) Working Group has released Working Drafts of the Web Content Accessibility Guidelines 2.0 and HTML Techniques for WCAG 2.0 and a First Public Working Draft of Understanding WCAG 2.0. Following WCAG makes Web content more accessible to the vast majority of users, including people with disabilities and older users, using many different devices including a wide variety of assistive technology.
When finished, WCAG 2.0 will clarify what was vague in previous Web Accessibility Initiative (WAI) guidelines. It will also come with developer-friendly techniques and glosses, making accessibility easier to understand, and accessible markup easier to build into the sites we create.
At the conference here in Gijón I have spent days with some of the leaders of this WAI and WCAG 2.0 activity. What they are doing has the potential to help all web users and all of us who serve them. — 1 am Gijón, Asturias, Spain
Another lecture season kicks off this week with my lunchtime keynote address at Active Insights, WebSideStory’s two-day user forum on best practices in digital marketing. Catch me if you can: Thursday, 10 November, the Grand Ballroom, the Roosevelt Hotel, Madison Avenue at 45th Street, New York City.
In Issue No. 207 of A List Apart, for people who make websites, we highlight a few unexpected consequences — both positive and negative — of common interface design and accessibility choices.