Responding doc - intro brainstorm notes

Hi Andrew,

Here are off-to-top-of-me-'ead *rough* ideas for the beginning of the "responding" doc.

Some of the things I was trying to get at:
* make this a quick list for people who will not wade through the entire document, with links to details below so it's link an index for the page content
* address the initial angry attack issue


1. Take a deep breath  frustrating to be stopped by accessibility barriers and can get really angry. however, usually angry is not the best tone to first approach an org about their inaccessible website. take a little time to read through the info below and craft an approach that is most likely to get the response that you want.


First, understand that Web accessibility barriers are often unintentional. Most web developers are not aware of accessibility issues, and don't know how to make their website accessible.

Approaching an org with an attacking, angry, aggressive tone will usually reflect badly on you and the accessibility cause, and not get you good response. Instead, consider approaching the org as if they do not understand accessibility, and that you want to help them understand the problem and how fixing it is in their best interest.

At the same time, be aware that accessibility is recognized as a human right in things like UN Convention and many national laws. While it is best to approach an org gently at first, be firm and recognize that you might need to get stronger in subsequent dealings.


2. Find the best way to lodge your complaint

3. Provide clear details to help them understand the problem, and to know where to get information to help them fix it

4. Have reasonable expectations for initial response, and for website fixes

5. Keep a record of your correspondence

6. Encourage others to get involved. consider enlisting the support of a disability organization. 

7. Escalate as needed

8. Share this webpage with others.


Received on Wednesday, 17 June 2009 17:12:58 UTC