Where specific, constructive functional requirements are provided to web content developers, there is a much greater chance that the web content will be accessible. The goal is to specify accurately the constraints within which developers must work, not to contrain their creativity. Good developers will appreciate clear specifications and web content can be as exciting as anyone can imagine and still accessibility compliant.
Poor specifications make the development process very expensive and it is often almost impossible to make inaccessible content accessible, if this is not worked on unitl the content has been developed.
A sample set of functional requirements is provided below as an example. (Sorry, this is not here yet.)
Last updated: 8 March 2002