ACT Rules Implementation in Test Tools and Methodologies
Test Methodologies
Test methodologies provide step by step instructions on how to test accessibility standards. See understanding ACT consistency for details.
| Implementation | Standards | Consistent Rules | Report |
|---|---|---|---|
| Trusted Tester 5.1 |
|
6 Rules
7 Proposed Rules
|
|
Semi-automated Test Tools
Semi-automated tools combine user input and automated testing to test accessibility standards. See understanding ACT consistency for details.
| Implementation | Standards | Consistent Rules | Report |
|---|---|---|---|
| Alfa (semi-automated) 0.57.2 |
|
20 Rules
30 Proposed Rules
|
|
| Axe DevTools Pro 4.37.1 |
|
27 Rules
12 Proposed Rules
|
|
Automated Test Tools
Automated tools test accessibility standards fully automatically. See understanding ACT consistency for details.
| Implementation | Standards | Consistent Rules | Report |
|---|---|---|---|
| Alfa (fully automated) 0.57.2 |
|
19 Rules
10 Proposed Rules
|
|
| Axe-core 4.8.1 |
|
24 Rules
11 Proposed Rules
|
|
| Equal Access Accessibility Checker 3.1.42-rc.0 |
|
16 Rules
6 Proposed Rules
|
|
| QualWeb 3.0.0 |
|
22 Rules
8 Proposed Rules
|
|
| SortSite 6.45 |
|
24 Rules
11 Proposed Rules
|
|
| Total Validator (+Browser) 17.3.0 |
|
24 Rules
15 Proposed Rules
|
|
Accessibility Linters
Linters are fully automated tools that test source code, rather than pages displayed in a browser or other user agents. Unlike other tools, linters can skip examples that require dynamic content such as JavaScript and CSS. See understanding ACT consistency for details.
| Implementation | Standards | Consistent Rules | Report |
|---|---|---|---|
| Total Validator 17.1.0 |
|
21 Rules
15 Proposed Rules
|
|
| ember-template-lint 5.5.1 |
|
0 Rules
0 Proposed Rules
|
|
Understanding ACT Consistency
Each ACT rule has examples. Vendors of test tools and methodologies run their implementations against the examples and report the outcome in a standard format. Reports are based on publicly available data.
A test tool or methodology is considered consistent when all the following are true:
- All success criteria that should fail are reported as such, and
- all examples have the expected outcome. (I.e. passed and inapplicable examples should not be failed, and failed examples should not be passed or inapplicable), and
- there are outcomes for all examples.
Automated implementations may report a “cannot tell” on some, but not all examples and still be considered consistent.
A test tool or methodology is partially consistent when it meets some, but not all requirements. A partially consistent implementation can not include false positives; i.e. it failing any passed or inapplicable examples.
Some ACT Rules are “proposed”. These rules are agreed on by the Accessibility Conformance Testing (ACT) Rules Task Force, and are awaiting implementation and approval by the Accessibility Guidelines Working Group. For details, see about ACT Rules.
Add a Tool or Methodology
For information on how to add your accessibility test tool or methodology to the list of ACT implementations, see Submit an ACT Implementation.
See Also
Disclaimer & Feedback
Inclusion of tools and methodologies in these tables does not indicate endorsement by W3C. Tools and figures are listed for informational purposes only.
Information in these pages is derived from data published by the vendors behind these tools and methodologies. Only tools and methodologies for which public data is available can be listed on this page. Tools and methodologies often have test procedures not yet described using ACT Rules. These are not included in the implementation reports. More information about these and other tools can be found on the Web Accessibility Evaluation Tools List.
The data is taken as-is, and is not verified by the W3C. If there are any questions or concerns about the information on these pages, open an issue on GitHub or e-mail group-act-rules@w3.org.