Guidance for QA Testers
Test process
Accessibility testing by its nature can only be automated in part, and, as a result, it is necessary to manually walk through the pages of the site testing against our standards.
The design and build phase of a website requires accessibility to be taken into account during the visual design, the information architecture, the template creation, the CMS setup, and the content population. The following tasks should be included in a project:
- Review templates and key pages against the Abeille Assurances accessibility guidelines
- Manually test your templates and key pages using text–only browsers and screen readers. Also check behaviours of scripting technologies (eg JavaScript and forms) and evaluate dynamically generated assets
- Conduct user testing as required. This will help you to identify any accessibility problems real–world users may have
Maintaining website accessibility is an ongoing responsibility. You need to plan how your level of accessibility is to be maintained after launch, as your website develops and grows.
Testing tools
The W3C provide a that can facilitate the testing process. In addition to these the following techniques can greatly aid accessibility testing:
- Our Accessibility checklist (xls 68kb) for test testing websites against our standards
- The WCAG2
- Browser plug–ins such as these
- A text based browser such as to test the document outline and also to provide a view on how screen readers would process the web page