# Tools

These tools help to achieve compliant development, and help make testing whole pages and sites more efficient and accurate.

If you know of additional or superior alternatives please share these with us.

# Manual tests

Much accessibility testing is conducted using standard Chromium / Mozilla developer tools plus selected extensions.

Manual testing should be conducted using both a desktop web browser, and a small-screen mobile browser with a touch interface.

# Browser extensions

Some suggested browser extensions to assist with manual testing. These may be referenced in the testing methods described below.

# Stand-alone applications

Additional stand-alone applications may be used where beneficial, including:

# Screen readers

All developers should undertake some basic screen reader testing. This is never a replacement for user testing, but can surface issues that would otherwise not be apparent.

Test with the most popular screen readers:

The Paciello Group have produced a very useful guide to which can form the basis of testing with screen readers: Basic screen reader commands for accessibility testing (opens new window)

# Automated tests

Automated testing is an efficient means of identifying issues for a small number of success criteria. For example testing for the presence of alt attributes on all images (1.1.1 (opens new window)).

Automated testing cannot reliably determine whether any success criteria is fully met, and must be accompanied by informed manual testing: automated testing cannot assess the appropriateness of an alt attribute.

Useful background reading: What we found when we tested tools on the world's least acessible webpage (opens new window)

It is very useful for testing document structure - headings and landmarks in particular - which can be tricky to evaluate manually or by reviewing markup.

The WAI maintains a list of automated accessibility testing tools (opens new window).

[TODO] Agree automated tools the project will use / support. Potential free options: