tech support 8

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Wednesday, 6 January 2010

W3C: Contacting Organizations about Inaccessible Websites

Posted on 09:28 by Unknown

For those of us who make a living working with organizations to help make their web sites accessible to users with disabilities, we've got it easy — the client wants to hear our recommendations. As users, however, all too often we stumble across an accessibility issue and don't know what to do to correct it. Granted, in my case I have a long history of making phone calls until I get somebody on the line, but I can speak the necessary lingo, not everyone else can.

The W3C WAI has just published a document that helps walk users through the steps necessary to contact someone about the issues you find, along with tips and sample emails. They call this document (simply enough) Contacting Organizations about Inaccessible Websites. Those familiar with the W3C should not be surprised that the title bears the [Draft] declaration at the front. The overview from the document (emphasis theirs):

Steps to help you report websites with accessibility problems are described on this page:

  1. Identify key contacts
  2. Describe the problem
  3. Follow-up as needed

Additional tips include:

  • Consider what approach will get the results you want
  • Keep records of all communications for possible follow-up
  • Encourage others to also provide feedback to the organization
  • Use the sample emails provided below

Because the document is a public draft, the W3C is accepting feedback up to February 3, 2010. The WAI Interest Group (IG) has a mailing list for public discussion of topics, including this one. There is a little more detail about this process at the blog post announcing this document.

If you've ever been to site and clicked on the words next to a radio button or checkbox and had nothing happen (the button doesn't select), then this document is for you. In this example, the site developer has failed to use the label element. This one is the single biggest issue I consistently encounter (as someone who doesn't use assistive technologies as part of his daily life). So help out by offering feedback on the draft and/or notifying sites of issues.

Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in accessibility, standards, W3C, WAI | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • Copying Content Styled with Text-Transform
    Using the CSS property text-transform to automatically shift copy to uppercase has been popular for a while now, but a combination of a rec...
  • HTML5 Finally Gets... a Logo?
    Start Rant With all the debate about elements , attributes , semantic meaning and who really owns HTML5 , it's thrilling to see that t...
  • New Google Analytics Features
    In the article " Google Analytics Now More Powerful, Flexible and Intelligent " from last Tuesday (yes, I know I'm behind on t...
  • Speaking: Accessible Web Apps & Standards
    I will be speaking twice in September, both of them sponsored by Infotech Niagara. If you're in the Buffalo area, these are great opport...
  • Speaking at WordCamp Buffalo 2013
    This Saturday I will be speaking at Buffalo's second WordCamp . Last year was a great day-long event filled with many good speakers (not...
  • CSS-D Finds New Home at evolt.org
    The incredibly popular, active, and valuable mailing list devoted to Cascading Style Sheets, CSS-Discuss (css-d), has moved its hosting to ...
  • Google Chrome Pre-Installed on Sony PCs
    Google cut a deal with Sony's PC division to distribute Chrome as a pre-installed browser on their Vaio PCs. Google claims to be in talk...
  • Test in Lynx and Print, It's Your Job
    I have admittedly not taken the time to attend An Event Apart any of the times it's been held, but I do tend to follow the #aea hashtag...
  • Thanksgiving, Technology, and Just Picking a Fight
    My logs tell me that nobody took this 2011 plea seriously. I blame the typeface. Last year on Thanksgiving I made the case for ignoring soci...
  • Tables as Responsive Image Containers
    If you've been following the latest chaos in the responsive image debate, you may know that there is a battle afoot between supporters o...

Categories

  • accessibility
  • Adobe
  • analytics
  • Apple
  • apps
  • ARIA
  • Bing
  • Blink
  • Brightkite
  • browser
  • Buzz
  • Chrome
  • clients
  • css
  • design
  • Facebook
  • Firefox
  • Flash
  • fonts
  • food
  • Foursquare
  • g11n
  • geolocation
  • globalization
  • Google
  • Gowalla
  • html
  • i18n
  • ICANN
  • infographic
  • Instagram
  • internationalization
  • internet
  • Internet Explorer
  • JavaScript
  • JAWS
  • Klout
  • L10n
  • law
  • localization
  • Lynx
  • Mapquest
  • Microsoft
  • mobile
  • Netscape
  • ning
  • Opera
  • patents
  • picplz
  • Plus
  • print
  • privacy
  • project management
  • QR
  • rant
  • RSS
  • Safari
  • SCVNGR
  • search
  • SEM
  • SEO
  • social media
  • Sony
  • speaking
  • standards
  • SVG
  • touch
  • translation
  • Twitter
  • typefaces
  • usability
  • UX
  • Verizon
  • video
  • W3C
  • WAI
  • WCAG
  • WebKit
  • whatwg
  • Wired
  • WOFF
  • xhtml
  • Yahoo
  • YouTube

Blog Archive

  • ►  2013 (39)
    • ►  December (1)
    • ►  November (7)
    • ►  September (4)
    • ►  July (3)
    • ►  June (2)
    • ►  May (5)
    • ►  April (3)
    • ►  March (6)
    • ►  February (2)
    • ►  January (6)
  • ►  2012 (63)
    • ►  December (2)
    • ►  November (4)
    • ►  October (5)
    • ►  September (5)
    • ►  August (4)
    • ►  July (6)
    • ►  June (7)
    • ►  May (7)
    • ►  April (8)
    • ►  March (5)
    • ►  February (3)
    • ►  January (7)
  • ►  2011 (67)
    • ►  December (5)
    • ►  November (7)
    • ►  October (5)
    • ►  September (4)
    • ►  August (8)
    • ►  July (3)
    • ►  June (8)
    • ►  May (3)
    • ►  April (1)
    • ►  March (6)
    • ►  February (6)
    • ►  January (11)
  • ▼  2010 (100)
    • ►  December (8)
    • ►  November (7)
    • ►  October (5)
    • ►  September (10)
    • ►  August (7)
    • ►  July (11)
    • ►  June (12)
    • ►  May (6)
    • ►  April (8)
    • ►  March (10)
    • ►  February (5)
    • ▼  January (11)
      • Too Soon to Advocate HTML5?
      • Define "Cognitive Disability"
      • Mashable on the Web of Tomorrow
      • Mobile Internet Use Continues Climb
      • Firefox 3.6 Is Here
      • Accessible Video and Transcripts
      • Against Vertical Navigation
      • The Latest on HTML5
      • W3C: Contacting Organizations about Inaccessible W...
      • Article: Lots of Twitter Followers Guarantees... N...
      • ALL-CAPS: Harder to Read?
  • ►  2009 (51)
    • ►  December (9)
    • ►  November (6)
    • ►  October (21)
    • ►  September (13)
    • ►  August (2)
  • ►  2003 (3)
    • ►  October (1)
    • ►  January (2)
  • ►  2002 (9)
    • ►  December (1)
    • ►  June (3)
    • ►  April (1)
    • ►  March (3)
    • ►  January (1)
  • ►  2001 (1)
    • ►  February (1)
  • ►  2000 (4)
    • ►  October (1)
    • ►  July (1)
    • ►  June (1)
    • ►  January (1)
  • ►  1999 (7)
    • ►  November (1)
    • ►  September (2)
    • ►  August (2)
    • ►  July (1)
    • ►  June (1)
Powered by Blogger.

About Me

Unknown
View my complete profile