Lets create an open source web accessibility policy

Recently I’ve come accross a prob­lem. Man­agers are often unable to con­vey what the acces­si­bil­ity requirments are for a prod­uct to their devel­op­ers, out­side of “it needs to be acces­si­ble.” I’ve been work­ing on a doc­u­ment that serves as both our acces­si­bil­ity pol­icy and as guide­lines for us and the devel­op­ers and con­trac­tors who work on our sites. Now I would like to release the first ver­sion of this doc­u­ment to any­body who would like to read it, and encourge any­body to make sug­ges­tions and changes [that are clearly marked] and send it back to me and I will look at inter­grat­ing the changes.

So Down­load the doc­u­ment and then email me back the doc­u­ment at ici.webmaster@gmail.com with your revi­sions. No guar­an­tees that your change will make it in every­time, but if we all are work­ing together, I think we can ceate a pretty use­ful document.

  1. Joe Clark says:

    Um… why is it a Word document?

  2. temelini says:

    Come on Joe. How about some­thing con­struc­tive? We all know that you know your stuff, but snide com­ments are really unnecessary.

  3. Joe Clark says:

    You think *that* was snide?

    That must have been the first sen­tence of mine you’d ever read, then.

  4. temelini says:

    Ooooh, sorry Joe. I for­got, you are a rab­ble rouser. You just go ahead and do your thing then. Rock on.

  5. ana says:

    you can not talk about open source and offer a doc

    ;)

  6. Jeff says:

    Ok, Ana, Joe, jump up to the next thread and give some input on what for­mat we should be using. I don’t care if the for­mat is open source as much as I care that the process and final prod­uct is free and open.

  7. temelini says:

    they can, jeff, but they won’t. It’s sim­ply not as fun as pop­ping in and offer­ing com­ments that are the equiv­a­lent of an eye roll. You sim­ply are not on the edge. Give it up. Every­one knows it… well, ana and joe clearly do.

Reply

or