Accessible collaborative documents
Despite the pooh-poohing of the format, I am still backing the idea of a universal accessible web policy for developers. But lets take a step back and take care of the format issue first. I chose to publish this in a Word Doc, because everybody I know uses word to edit and write content (including those with screen readers). It also has some features for tracking changes, which we have already used on this document within my office.
So lets hear some constructive ideas on what format we should all be working in, as I am going to try and drag more people into this. I looked into Wikis a little bit, but it didn’t seem like a great fit for this project. Using and XML or HTML document seems like it might exclude people who don’t work with those formats.
Go.
Christopher Phillips responds:
Posted: February 17th, 2005 at 12:54 am →
Jeff- I think you’ve made a good choice with the Word Doc, but you may also want to reconsider a wiki. There would be some setup, but it condenses the steps of download, turn on track changes, edit, save, send back to author to just edit and save online- and most types of wiki software have good tracking features built-in.
Kenny Page responds:
Posted: April 9th, 2005 at 5:43 am →
Guys - not wanting to rubbish the whole idea, especially as i’m posting long after discussions have started, but..
Would it not be more beneficial to build an open source web accessibility verification tool similar to the old offline Bobby java application?
If you think back, the wider web design community *used* to have a tool, now they don’t.