The ATF has put a lot of effort into looking at the world to analyse the issues standing in the way of broader accessibility for everyone. Having worked out the problems we face and what we are willing to tackle, we are now happy to present the Accessibility Task Force manifesto.
In a nutshell, we will work with all of the parties involved in producing web tools, content, and assistive technology to ensure:
- that all assistive technologies used to assist web browsing understand the whole of the HTML, XHTML, DOM and CSS recommendations.
- that the manufacturers of assistive technologies transparently document their products’ capabilities and behaviour in terms of standards support and scripting.
- that all Content Management Systems produce semantic, accessible, valid and lean code straight out of the box.
- that CMS vendors make certain that people with disabilities can easily use their tools to produce Web content.
- that web developers use web standards to produce their websites and, where possible, they test them with assistive technologies and with people with disabilities to ensure that they are both accessible and usable.
- that the community remember that the Web Content Accessibility Guidelines (WCAG) are only part of the puzzle—the Authoring Tool Accessibility Guidelines (ATAG), User Agent Accessibility Guidelines (UAAG) and in fact the Document Object Model (DOM) are web standards too.
In addition, I promise to try to use British spellings in order to minimise (see?) collaborative editing problems.
Your feedback is welcome. What have we missed? Whom should we approach first? What do web professionals need most to make it transparently easy to enable users with disabilities? Feel free to use the comments below.
- #1 On April 19th, 2006 4:51 pm