- Web CMS: Adobe Buys Day Software for US$ 240 Million
3
comments
- Installing SharePoint 2010 on Windows 7
9
comments
- Perspectives: What the Adobe + Day Software Deal Means, Part 1
- Overview: SharePoint 2010 Metadata and Taxonomy Management
8
comments
- Web CMS: MODx Revolution Targets Drupal, Joomla Markets
11
comments
- Barebones CMS is Easier than WordPress, Drupal and Joomla
- MS Project 2010: Goodbye Portfolio Server, Hello SharePoint
8
comments
Get the NewsletterW3C Provides Guidance for Brow Beating Inaccessible Websites
By
| Published Jan 14, 2010
1
comment
1
comment
We know it’s frustrating when you come across a website that’s less than functional, full of accessibility barriers. How often do any of us take action? Those days are over.
The World Wide Web Consortium (W3C) wants you to take action when you come across an inaccessible website. They are encouraging users to tell organizations how important it is that their websites are accessible.
To help you do so, they’ve published a guide called Contacting Organizations about Inaccessible Websites. Currently in draft form, the guide offers tips for approaching the suspect site and how to describe the problem in a non-intimidating, but helpful manner. There are even sample emails and links to additional resources to help you and the offending party learn more about accessibility and its role on the Internet.
The W3C is also soliciting input from users. You can leave your ideas for the guide and your experiences dealing with inaccessible websites via their blog or through the Web Accessibility Initiative (WAI) Interest Group’s public discussion at wai-eo-editors@w3.org list (users need to subscribe first). Comments are due by February 3.
Was this article useful?
Email It
Buzz it
Tag It
Stumble It
Add RSS1 Reader Comment
Leave a Response
Processing...
Job Openings View all
| Post a job
| 
RSS
- UI/UX Designer at Nimble
- Account Associate, Inside Sales - Brand/Agency at Facebook
- Technical Web Analyst at Thomson Reuters
- Project Manage at Wireless Generation
- Technical Writer / Software Development at Omnitec Solutions, Inc
- Online Community & Content Manager at CRC
- Web Designer/User Experience Guru at Fog Creek Software
- Vice President at Emanate
Featured Events View all
| Add event
| RSS
- Aug 5, 2010 – Webinar: How Combining Enterprise CMS and BPM Boosts IT Efficiency
- Sep 19, 2010 – Oracle OpenWorld 2010
- Oct 7, 2010 – HartmanEVENT 2010 - Social Media & Mobile Usability
This is Wonderful News. The draft itself is pretty mild compared to what I would like to have ranted about (I played a small part in its content) but your title says it just like I wanted to.
In particular the admonitions concerning what to do when all else fails and the offending Website is uncooperative are tempered by tact and polity.
My personal recommendation, with no implication that this is an official W3C/WAI position is that when it becomes evident that your accessibility suggestions are being stonewalled or endlessly delayed/deferred you move from passive to active mode and institute legal proceedings. They (especially government entities) are breaking the law and violating our human rights to access. Allowing that anti-social behavior to simply continue (the laissez-faire approach) is no longer an option. If it takes “drive-by lawsuits” to achieve a universally accessible/usable Web then GO FOR IT!
Love.