Trusted Tester ACT Implementation
This page is under development and has not been approved by the working group.
Number of Rules Implemented
|
Consistent |
Partially consistent |
| WCAG 2 rules |
2 |
0 |
| Proposed rules |
7 |
5 |
Implemented Rules
About Trusted Tester Results
Results in this page are taken from a public
test report
published by US federal government.
Data is published using the
EARL+JSON-LD data format.
Implementation Details
HTML page has lang attribute
This rule is implemented by Trusted Tester using the
3.1.1-page-language-defined procedure.
The implementation is
fully consistent with the
HTML page has lang attribute
WCAG 2 rule.
It covers all 7 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
HTML page has non-empty title
This rule is implemented by Trusted Tester using the
2.4.2-page-title-defined procedure.
The implementation is
fully consistent with the
HTML page has non-empty title
WCAG 2 rule.
It covers all 11 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
Audio element content has text alternative
This rule is implemented by Trusted Tester using the
1.2.1-audio-transcript-text procedure.
The implementation is
fully consistent with the
Audio element content has text alternative
proposed rule.
It covers all 8 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
-
1.2.1
Audio-only and Video-only (Prerecorded)
|
-
1.2.1
Audio-only and Video-only (Prerecorded)
|
Text content that changes automatically can be paused, stopped or hidden
This rule is implemented by Trusted Tester using the
2.2.2-auto-updating procedure.
The implementation is
fully consistent with the
Text content that changes automatically can be paused, stopped or hidden
proposed rule.
It covers all 11 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
Focusable element has no keyboard trap
This rule is implemented by Trusted Tester using the
2.1.2-no-keyboard-trap procedure.
The implementation is partially
consistent with the
Focusable element has no keyboard trap
proposed rule.
It covers 15 of the 16 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
Focusable element has no keyboard trap via non-standard navigation
This rule is implemented by Trusted Tester using the
2.1.2-no-keyboard-trap procedure.
The implementation is partially
consistent with the
Focusable element has no keyboard trap via non-standard navigation
proposed rule.
It covers all 7 examples.
The implementation reports different success criteria as failed from what is expected by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
None
|
|
Focusable element has no keyboard trap via standard navigation
This rule is implemented by Trusted Tester using the
2.1.2-no-keyboard-trap procedure.
The implementation is partially
consistent with the
Focusable element has no keyboard trap via standard navigation
proposed rule.
It covers all 10 examples.
The implementation reports different success criteria as failed from what is expected by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
None
|
|
Heading is descriptive
This rule is implemented by Trusted Tester using the
2.4.6-heading-purpose procedure.
The implementation is
fully consistent with the
Heading is descriptive
proposed rule.
It covers all 17 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
-
2.4.6
Headings and Labels
|
-
2.4.6
Headings and Labels
|
HTML page title is descriptive
This rule is implemented by Trusted Tester using the
2.4.2-page-title-purpose procedure.
The implementation is
fully consistent with the
HTML page title is descriptive
proposed rule.
It covers all 6 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
Image accessible name is descriptive
This rule is implemented by Trusted Tester using the
1.1.1-meaningful-image-name procedure.
The implementation is partially
consistent with the
Image accessible name is descriptive
proposed rule.
It covers 14 of the 16 examples.
For 2 examples
no results were reported. This can happen when examples are newer then the
test results.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
HTML graphics contain no text
This rule is implemented by Trusted Tester using the
1.4.5-image-of-text procedure.
The implementation is
fully consistent with the
HTML graphics contain no text
proposed rule.
It covers all 14 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
-
1.4.5
Images of Text
-
1.4.9
Images of Text (No Exception)
|
-
1.4.5
Images of Text
-
1.4.9
Images of Text (No Exception)
|
Menuitem has non-empty accessible name
This rule is implemented by Trusted Tester using the
update needed procedure.
The implementation is
fully consistent with the
Menuitem has non-empty accessible name
proposed rule.
It covers all 8 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
Element in sequential focus order has visible focus
This rule is implemented by Trusted Tester using the
2.4.7-focus-visible procedure.
The implementation is
fully consistent with the
Element in sequential focus order has visible focus
proposed rule.
It covers all 9 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
Video element auditory content has captions
This rule is implemented by Trusted Tester using the
1.2.2-captions-equivalent procedure.
The implementation is partially
consistent with the
Video element auditory content has captions
proposed rule.
It covers all 8 examples.
The implementation reports different success criteria as failed from what is expected by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
None
|
-
1.2.2
Captions (Prerecorded)
|