I agreeto Idea Website to Learn from Mistakes/Success
Voting is Disabled

14 votes

I disagree



This idea is active.
Product Accessibility »

Website to Learn from Mistakes/Success

The problem with the language of the rules and regulations is that they are open for interpretation and each company implementing a new application or site can interpret differently. I think an official site that contains a running archive of compliant vs. non compliant examples of actual implementations for each rule/regulation (and why they have that status) would be helpful. That way, you could check your implementation/idea against the database. If you don't see it on there, send it in for an official review to be shared on the site. For example, applets and plugins, say you wanted to implement a link in the footer to view all plugins required on the site to cover this requirement but wasn't sure if that was good enough to be compliant. You could go on this site and see if it had ever been implemented that way and if that implementation was accepted/rejected... or again, never tried.

Submitted by anthony.prematta 2 years ago

Vote Activity Show

Similar Ideas Show


  1. The idea was posted
    2 years ago

Comments (1)

  1. Anthony, such a document actually exists. It's called the W3C's Techniques for WCAG 2.0 and can be found at www.w3.org/TR/WCAG20-TECHS/#contents . (I've given you the anchor tag directly to the table of contents because I find the top of these WCAG pages utterly unusable. Start with the TOC and you'll find it easier to use.)

    Best of all, anyone who thinks they have a technique for accessible design can submit that technique to the working group that maintains this page. Periodically, the working group review submitted techniques, determines whether they are successful, and then adds them to either the list of successful techniques or the list of failures. So you can learn what succeeded,why it succeeded, what failed, and why it failed.

    The biggest obstacle to using this list is that no WCAG working group has taken on the task of creating an index to these techniques (and other aspects of WCAG). For example, if I'm creating a form, which techniques should I review? To find that information now, I'd have to do a lot of tedious searching—and even then I wouldn't be certain that I had found all that could help.

    With such an index, in 5 minutes or less a developer or author with a specific problem should be able to find the best answer available. Depending on the complexity of their problem, implementing that answer might take a second or a week—or even longer! But they wouldn't be hit with P-O-U-R as their only way to access the word on accessibility.

    I've suggested that a WCAG working group that I thought had the role of improving education and outreach, but ultimately I was told flat out that they would not have it on their agenda at any time in the foreseeable future and, if I thought it important, I should just create it myself.

    I'm certainly not opposed to participating in creating it, but I'd have to do that in my spare time. Could I use help? Only all I can get. If you're interested in participating in this endeavor, contact me. My e-mail's pretty easy to figure out: first name dot last name [at symbol] yahoo dot com. Or you can find me on LinkedIn with a name remarkably like my own or on Twitter as @clifftyll. Maybe some day off we could figure out how to hack this elephant up into digestible portions and then start eating it the only way one can—one bite at a time.

    2 years ago
    0 Agreed
    0 Disagreed