UsableNet AQA ACT Automated Implementation
Consistent | Partially consistent | |
---|---|---|
WCAG 2 rules | 30 | 0 |
Proposed rules | 3 | 1 |
Implemented Rules
About UsableNet AQA - WCAG 2.2 AA Auto Results
Results in this page are taken from a public test report published by UsableNet. Data is published using the EARL+JSON-LD data format.
Implementation Details
Role attribute has valid value
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
aria_role_not_valid
procedure.
The implementation is
fully consistent with the
Role attribute has valid value
WCAG 2 rule.
It covers all 10 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
None |
|
aria_role_not_valid | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 4 * | passed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
ARIA state or property has valid value
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
aria_value_wrong
procedure.
The implementation is
fully consistent with the
ARIA state or property has valid value
WCAG 2 rule.
It covers all 21 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
None |
|
aria_value_wrong | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Passed Example 8 | passed |
Passed Example 9 | passed |
Passed Example 10 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Failed Example 6 | failed |
Failed Example 7 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
ARIA attribute is defined in WAI-ARIA
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
invalid_aria_attr
procedure.
The implementation is
fully consistent with the
ARIA attribute is defined in WAI-ARIA
WCAG 2 rule.
It covers all 7 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
None |
|
invalid_aria_attr | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Inapplicable Example 1 | passed |
Passed Example 2 * | passed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
Element with lang attribute has valid language tag
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
element_invalid_lang
procedure.
The implementation is
fully consistent with the
Element with lang attribute has valid language tag
WCAG 2 rule.
It covers all 19 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
element_invalid_lang | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Failed Example 6 | failed |
Failed Example 7 | failed |
Failed Example 8 | failed |
Failed Example 9 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Menuitem has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
control_without_computed_name
procedure.
The implementation is
fully consistent with the
Menuitem has non-empty accessible name
WCAG 2 rule.
It covers all 8 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
control_without_computed_name | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Iframe with interactive elements is not excluded from tab-order
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
focusable_elements_inside_iframe
procedure.
The implementation is
fully consistent with the
Iframe with interactive elements is not excluded from tab-order
WCAG 2 rule.
It covers all 9 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
focusable_elements_inside_iframe | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Failed Example 1 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 6 * | passed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
Important letter spacing in style attributes is wide enough
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
wrong_letter_spacing
procedure.
The implementation is
fully consistent with the
Important letter spacing in style attributes is wide enough
WCAG 2 rule.
It covers all 19 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
wrong_letter_spacing | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 7 | passed |
Inapplicable Example 8 | passed |
Inapplicable Example 9 | passed |
Important word spacing in style attributes is wide enough
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
wrong_word_spacing
procedure.
The implementation is
fully consistent with the
Important word spacing in style attributes is wide enough
WCAG 2 rule.
It covers all 19 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
wrong_word_spacing | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 7 | passed |
Inapplicable Example 8 | passed |
Inapplicable Example 9 | passed |
Important line height in style attributes is wide enough
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
wrong_line_height
procedure.
The implementation is
fully consistent with the
Important line height in style attributes is wide enough
WCAG 2 rule.
It covers all 24 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
wrong_line_height | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Passed Example 8 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Failed Example 6 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 7 | passed |
Inapplicable Example 8 | passed |
Inapplicable Example 9 | passed |
Inapplicable Example 10 | passed |
autocomplete attribute has valid value
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
invalid_autocomplete_token
procedure.
The implementation is
fully consistent with the
autocomplete attribute has valid value
WCAG 2 rule.
It covers all 28 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
invalid_autocomplete_token | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Passed Example 8 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 7 | passed |
Passed Example 9 | passed |
Failed Example 6 | failed |
Failed Example 7 | failed |
Failed Example 8 | failed |
Failed Example 9 | failed |
Failed Example 10 | failed |
Inapplicable Example 8 | passed |
Inapplicable Example 9 | passed |
Inapplicable Example 8 * | passed |
Inapplicable Example 9 * | passed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
Button has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
input_without_computed_name
procedure.
The implementation is
fully consistent with the
Button has non-empty accessible name
WCAG 2 rule.
It covers all 17 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
input_without_computed_name | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Element marked as decorative is not exposed
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
invalid_aria_attr
procedure.
The implementation is
fully consistent with the
Element marked as decorative is not exposed
WCAG 2 rule.
It covers 9 of the 10 examples.
On 1 example
the implementation cannot tell the outcome. This is often because of technical
limitations in tools.
The implementation correctly reports no success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
None | None |
invalid_aria_attr | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Failed Example 1 | failed |
Failed Example 2 | cannot tell |
Failed Example 3 | failed |
Inapplicable Example 1 | passed |
Form field has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
input_without_computed_name
procedure.
The implementation is
fully consistent with the
Form field has non-empty accessible name
WCAG 2 rule.
It covers all 19 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
input_without_computed_name | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Failed Example 6 | failed |
Failed Example 7 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Passed Example 8 | passed |
Failed Example 8 | failed |
Passed Example 8 * | passed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
HTML page lang attribute has valid language tag
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
page_invalid_lang
procedure.
The implementation is
fully consistent with the
HTML page lang attribute has valid language tag
WCAG 2 rule.
It covers all 7 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
page_invalid_lang | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
HTML page has non-empty title
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
page_missing_title
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.
Expected | Reported |
---|---|
|
|
page_missing_title | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Inapplicable Example 1 | passed |
Passed Example 2 * | passed |
Failed Example 6 * | failed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
Image button has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
image_button_without_computed_name
procedure.
The implementation is
fully consistent with the
Image button has non-empty accessible name
WCAG 2 rule.
It covers all 12 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
image_button_without_computed_name | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Image has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
image_missing_alt
procedure.
The implementation is
fully consistent with the
Image has non-empty accessible name
WCAG 2 rule.
It covers all 18 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
image_missing_alt | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Passed Example 8 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Link has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
link_without_computed_name
procedure.
The implementation is
fully consistent with the
Link has non-empty accessible name
WCAG 2 rule.
It covers all 28 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
link_without_computed_name | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Passed Example 8 | passed |
Passed Example 9 | passed |
Passed Example 10 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Failed Example 6 | failed |
Failed Example 7 | failed |
Failed Example 8 | failed |
Failed Example 9 | failed |
Failed Example 10 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Passed Example 11 | passed |
Failed Example 11 | failed |
SVG element with explicit role has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
svg_without_alt
procedure.
The implementation is
fully consistent with the
SVG element with explicit role has non-empty accessible name
WCAG 2 rule.
It covers all 10 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
svg_without_alt | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Element with presentational children has no focusable content
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
focusable_presentational_children
procedure.
The implementation is
fully consistent with the
Element with presentational children has no focusable content
WCAG 2 rule.
It covers all 7 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
focusable_presentational_children | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Inapplicable Example 1 | passed |
Headers attribute specified on a cell refers to cells in the same table element
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
td_headers_check
procedure.
The implementation is
fully consistent with the
Headers attribute specified on a cell refers to cells in the same table element
WCAG 2 rule.
It covers all 17 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
td_headers_check | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Passed Example 8 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 4 * | passed |
Inapplicable Example 6 * | passed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
Element with aria-hidden has no content in sequential focus navigation
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
aria_hidden_focusable_descendants
procedure.
The implementation is
fully consistent with the
Element with aria-hidden has no content in sequential focus navigation
WCAG 2 rule.
It covers 13 of the 15 examples.
On 2 examples
the implementation cannot tell the outcome. This is often because of technical
limitations in tools.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
aria_hidden_focusable_descendants | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | cannot tell |
Passed Example 5 | passed |
Passed Example 6 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Failed Example 6 | cannot tell |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Meta element has no refresh delay
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
meta_refresh
procedure.
The implementation is
fully consistent with the
Meta element has no refresh delay
WCAG 2 rule.
It covers all 15 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
meta_refresh | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 7 | passed |
Inapplicable Example 8 | passed |
Meta viewport allows for zoom
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
meta_prevent_zoom
procedure.
The implementation is
fully consistent with the
Meta viewport allows for zoom
WCAG 2 rule.
It covers all 11 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
meta_prevent_zoom | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Passed Example 2 * | passed |
Passed Example 5 * | passed |
Failed Example 2 * | failed |
Failed Example 3 * | failed |
Failed Example 7 * | failed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
Object element rendering non-text content has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
object_missing_computed_name
procedure.
The implementation is
fully consistent with the
Object element rendering non-text content has non-empty accessible name
WCAG 2 rule.
It covers all 18 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
object_missing_computed_name | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Failed Example 6 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 7 | passed |
Inapplicable Example 8 | passed |
HTML page has lang attribute
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
page_missing_lang
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.
Expected | Reported |
---|---|
|
|
page_missing_lang | |
---|---|
Passed Example 1 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Scrollable content can be reached with sequential focus navigation
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
scrollable_content_focus
procedure.
The implementation is
fully consistent with the
Scrollable content can be reached with sequential focus navigation
WCAG 2 rule.
It covers all 10 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
scrollable_content_focus | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Passed Example 2 * | passed |
Passed Example 3 * | passed |
Inapplicable Example 2 * | passed |
Inapplicable Example 3 * | passed |
Inapplicable Example 6 * | passed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
Text has minimum contrast
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
color_error_normal
procedure.
The implementation is
fully consistent with the
Text has minimum contrast
WCAG 2 rule.
It covers 26 of the 32 examples.
On 6 examples
the implementation cannot tell the outcome. This is often because of technical
limitations in tools.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
color_error_normal | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | cannot tell |
Passed Example 3 | cannot tell |
Passed Example 4 | cannot tell |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Passed Example 8 | passed |
Passed Example 9 | passed |
Passed Example 10 | passed |
Passed Example 11 | passed |
Failed Example 1 | failed |
Failed Example 2 | cannot tell |
Failed Example 3 | cannot tell |
Failed Example 4 | failed |
Failed Example 5 | failed |
Failed Example 6 | failed |
Failed Example 7 | cannot tell |
Failed Example 8 | failed |
Failed Example 9 | failed |
Failed Example 10 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 7 | passed |
Inapplicable Example 8 | passed |
Inapplicable Example 9 | passed |
Inapplicable Example 10 | passed |
Inapplicable Example 11 | passed |
Passed Example 7 * | passed |
Failed Example 11 * | cannot tell |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
Text has enhanced contrast
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
color_error_enhanced
procedure.
The implementation is
fully consistent with the
Text has enhanced contrast
WCAG 2 rule.
It covers 29 of the 34 examples.
On 5 examples
the implementation cannot tell the outcome. This is often because of technical
limitations in tools.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
color_error_enhanced | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | cannot tell |
Passed Example 3 | cannot tell |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | passed |
Passed Example 8 | passed |
Passed Example 9 | passed |
Passed Example 10 | passed |
Failed Example 1 | failed |
Failed Example 2 | cannot tell |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Failed Example 6 | cannot tell |
Failed Example 7 | failed |
Failed Example 8 | failed |
Failed Example 9 | failed |
Failed Example 10 | cannot tell |
Failed Example 11 | failed |
Failed Example 12 | failed |
Failed Example 13 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 7 | passed |
Inapplicable Example 8 | passed |
Inapplicable Example 9 | passed |
Inapplicable Example 10 | passed |
Inapplicable Example 11 | passed |
Passed Example 6 * | passed |
*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.
Meta element has no refresh delay (no exception)
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
meta_refresh_no_exception
procedure.
The implementation is
fully consistent with the
Meta element has no refresh delay (no exception)
WCAG 2 rule.
It covers all 13 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
meta_refresh_no_exception | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Inapplicable Example 5 | passed |
Inapplicable Example 6 | passed |
Inapplicable Example 7 | passed |
Inapplicable Example 8 | passed |
ARIA state or property is permitted
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
invalid_aria_attr
procedure.
The implementation is partially
consistent with the
ARIA state or property is permitted
proposed rule.
It covers 16 of the 19 examples.
For 3 examples
no results were reported. This can happen when examples are newer then the
test results.
The implementation correctly reports no success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
None | None |
invalid_aria_attr | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Passed Example 7 | untested |
Passed Example 8 | untested |
Passed Example 9 | passed |
Passed Example 10 | passed |
Passed Example 11 | passed |
Passed Example 12 | untested |
Passed Example 13 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Iframe element has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
iframe_without_computed_name
procedure.
The implementation is
fully consistent with the
Iframe element has non-empty accessible name
proposed rule.
It covers all 11 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
iframe_without_computed_name | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |
Element with role attribute has required states and properties
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
aria_required_attr
procedure.
The implementation is
fully consistent with the
Element with role attribute has required states and properties
proposed rule.
It covers all 14 examples.
The implementation correctly reports no success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
None | None |
aria_required_attr | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Passed Example 6 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Failed Example 4 | failed |
Failed Example 5 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Summary element has non-empty accessible name
This rule is implemented by UsableNet AQA - WCAG 2.2 AA Auto using the
summary_without_computed_name
procedure.
The implementation is
fully consistent with the
Summary element has non-empty accessible name
proposed rule.
It covers all 12 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Expected | Reported |
---|---|
|
|
summary_without_computed_name | |
---|---|
Passed Example 1 | passed |
Passed Example 2 | passed |
Passed Example 3 | passed |
Passed Example 4 | passed |
Passed Example 5 | passed |
Failed Example 1 | failed |
Failed Example 2 | failed |
Failed Example 3 | failed |
Inapplicable Example 1 | passed |
Inapplicable Example 2 | passed |
Inapplicable Example 3 | passed |
Inapplicable Example 4 | passed |