Planning for accessibility
Planning in advance
Make sure that there is a clear statement regarding accessibility compliance in your Quality Standards documentation - usually in the Requirements documentation for the project.
If it is known in advance that a particular project will be using technologies with known accessibility problems, for example Flash, then the document must explain what other measures will be taken to provide an accessible alternative. Accessibility should be considered at every stage of the life-cycle.
Early testing
It is a good idea to do some preliminary tests of designs and templates for compliance early on in the life-cycle of a project, before an entire product is developed on the basis of those designs. It is far quicker and cheaper to build in accessibility from the start rather than trying to retrofit a completed project.
Keeping records
Web projects should maintain records and produce evidence of accessibility testing.
Find out more about checking and testing your site.