Web Content Accessibility Guidelines 2.0 Now Final
beetle496 writes "It has been going on nine years now, but finally there are formal standards for Web accessibility for technologies other than HTML. They ask that you start with the press release (lots of links), but regulars might be more entertained by the last time WCAG made the front page here. Many folks here will point out that web accessibility is old hat, and by implication this is hardly news, but if you do Web development for any government organization, you should expect that accessibility is a base requirement. The Section 508 standards are to be updated (relatively) soon too."
Good luck with your non-CSS, table-based layout, javascript and Flash-required things you like to refer to as "websites".
Is it just me or are most of these Accessibility Standards (sadly) just not worth the time and trouble?
I am hearing impaired. What's the accessibility standard to help me enjoy a podcast? Do we require closed captioning for all podcasts? Require a written transcript to be posted with every podcast?
Sure, there's plenty of podcasts I'd like to "listen" to and can't but for each pound of extra baggage we pile on a publisher, we reduce the incentive to publish. How long before all this well-intentioned madness starts to limit the amount of good material that is published?
The inevitable end result is an artificial reduction in the amount of material available to all.
"The ferrets, they're every where I tell you!"