Using automated testing tools
Introduction
Automated testing tools are useful in assisting content managers and web developers with the identification of accessibility issues and errors of a website.
These tools are able to perform ‘machine-operable’ testing only, and should be used as a companion alongside human site review and testing.
The following testing tool information is provided as a guide only and is not an exhaustive list.
Recommended tools
The following testing tools are recommended as the most suitable, based on volume of pages being tested:
Tool | Volume of pages | Type of tool |
---|---|---|
Web Developer Toolbar | Single pages. | Free browser extension for Firefox or Chrome. |
WAVE | Single pages or small section of pages. | Free online tool – can be used online or download the toolbar. |
OzART | Large section of pages or entire website. | Online reporting tool – produces error category specific reports, reduces time spent manually inspecting single web pages. |
NB: In some instances only one tool may be suitable regardless of the volume of pages to be tested. In addition, if no tool is suitable a manual site review will be required.
Testing coding with the Web Developer Toolbar
The following coding references are requirements from the Checklist.
Page Title
Automatic:
- None
Manual required:
- PGT_A1
- PGT_A2
- PGT_A3i,ii,iii,iv,v,vi
- PGT_A4i,ii
Not assessed:
- N/A – all page title issues can be identified using the Web Developer Toolbar, however each page must be tested individually and manually
Text Content
Automatic:
- TXT_A3ii
Manual required:
- TXT_A2ii
- TXT_A2v
- TXT_A2vii
- TXT_A3i
- TXT_AA1
- TXT_AA2
Not assessed:
- TXT_A1i, ii
- TXT_A2i, iii, v,vi
Headings
Automatic:
- None
Manual required:
- HED_A1iii
- HED_A2i, ii, iii, iv, v, vi, vii
- HED_A3i, ii, iii, iv, v
- HED_AA1
Not assessed:
- HED_A1ii
Link Text
Automatic:
- None
Manual required:
- LNK_A1i, ii, iii, iv, v, vi
- LNK_A2iii,iv
- LNK_A3i, ii,iii, iv, v, vi
- LNK_A4i, ii
- LNK_A5
- LNK_A6
- LNK_AA1i,ii
- LNK_AA2i, ii, iii
Not assessed:
- LNK_A2i,ii
Testing coding with WAVE
The following coding references are requirements from the Checklist.Page Titles
Automatic
- PGT_A1
- PGT_A2
Manual required
- PGT_A3i, ii, iii, iv,v, vi
- PGT_A4i, ii
Not assessed
- N/A – all page title issues can be identified using WAVE, however each page must be checked individually
Text Content
Automatic
- TXT_A3ii
Manual required
- TXT_A2ii, v, vii
- TXT_AA1
- TXT_AA2
Not assessed
- TXT_A1i,ii
- TXT_A2i, ii, iii, iv, vi
Headings
Automatic
- HED_A1i HED_A3iii
Manual required
- HED_A1iii
- HED_A2ii,iii, iv, v, vi
- HED_A3i,ii, iv, v
Not assessed
- HED_A1ii
- HED_A2i (WAVE does provide some indication of potential failures of this requirement), vii
- HED_AA1
Link Text
Automatic:
- None
Manual required:
- LNK_A1iii, iv, v, vi
- LNK_A2ii, iii, iv, v, vi
- LNK_A3i, ii, iv, v, vi
- LNK_A4i, ii
- LNK_A6
- LNK_AA1i,ii
- LNK_AA2i, ii, iii
Not assessed:
- LNK_A2i, ii
- LNK_A5
- LNK_AA2i, ii
Testing coding with OzART
The following coding references are requirements from the Checklist.Page Title
Automatic
- PGT_A1
- PGT_A2
- PGT_A3iv, vi
Manual required
- PGT_A3i, ii, iii,v
- PGT_A4i, ii
Not assessed
- N/A – all page title issues can be identified using OzART
Text Content
Automatic:
- TXT_A3ii
Manual required:
- TXT_A1i, ii
- TXT_A2i,iii,v, vi
- TXT_A3i
- TXT_AA1
- TXT_AA2
Not assessed:
- TXT_A2ii iv,vii
Headings
Automatic
- HED_A1i, iii
- HED_A2ii, iv
- HED_A3ii, iii, v
Manual required
- HED_A2iii, v, vi
- HED_A3i, iv
Not assessed
- HED_A1ii
- HED_A2i, vii
- HED_AA1
Link Text
Automatic:
- LNK_A1ii, iii, iv, v
- LNK_A2iii,iv
- LNK_A3v
- LNK_A6
Manual required:
- LNK_A1i, vi
- LNK_A2i, ii
- LNK_A3i, ii,iii,iv,vi
- LNK_A4i,ii
- LNK_AA1i, ii
- LNK_AA2iii
Not assessed:
- LNK_A5
- LNK_AA2i
- LNK_AA2ii