Skip to content

UsableNet AQA ACT Automated Implementation

Number of Rules Implemented
Consistent Partially consistent
WCAG 2 rules 30 0
Proposed rules 3 1

Implemented Rules

Rule Name Type Consistency
Role attribute has valid value WCAG 2 Rule Consistent
ARIA state or property has valid value WCAG 2 Rule Consistent
ARIA attribute is defined in WAI-ARIA WCAG 2 Rule Consistent
Element with lang attribute has valid language tag WCAG 2 Rule Consistent
Menuitem has non-empty accessible name WCAG 2 Rule Consistent
Iframe with interactive elements is not excluded from tab-order WCAG 2 Rule Consistent
Important letter spacing in style attributes is wide enough WCAG 2 Rule Consistent
Important word spacing in style attributes is wide enough WCAG 2 Rule Consistent
Important line height in style attributes is wide enough WCAG 2 Rule Consistent
autocomplete attribute has valid value WCAG 2 Rule Consistent
Button has non-empty accessible name WCAG 2 Rule Consistent
Element marked as decorative is not exposed WCAG 2 Rule Consistent
Form field has non-empty accessible name WCAG 2 Rule Consistent
HTML page lang attribute has valid language tag WCAG 2 Rule Consistent
HTML page has non-empty title WCAG 2 Rule Consistent
Image button has non-empty accessible name WCAG 2 Rule Consistent
Image has non-empty accessible name WCAG 2 Rule Consistent
Link has non-empty accessible name WCAG 2 Rule Consistent
SVG element with explicit role has non-empty accessible name WCAG 2 Rule Consistent
Element with presentational children has no focusable content WCAG 2 Rule Consistent
Headers attribute specified on a cell refers to cells in the same table element WCAG 2 Rule Consistent
Element with aria-hidden has no content in sequential focus navigation WCAG 2 Rule Consistent
Meta element has no refresh delay WCAG 2 Rule Consistent
Meta viewport allows for zoom WCAG 2 Rule Consistent
Object element rendering non-text content has non-empty accessible name WCAG 2 Rule Consistent
HTML page has lang attribute WCAG 2 Rule Consistent
Scrollable content can be reached with sequential focus navigation WCAG 2 Rule Consistent
Text has minimum contrast WCAG 2 Rule Consistent
Text has enhanced contrast WCAG 2 Rule Consistent
Meta element has no refresh delay (no exception) WCAG 2 Rule Consistent
ARIA state or property is permitted Proposed Rule Partial
Iframe element has non-empty accessible name Proposed Rule Consistent
Element with role attribute has required states and properties Proposed Rule Consistent
Summary element has non-empty accessible name Proposed Rule Consistent

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.

Success Criteria
Expected Reported
None
  • 1.3.1 Info and Relationships

*: 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.

Success Criteria
Expected Reported
None
  • 1.3.1 Info and Relationships

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.

Success Criteria
Expected Reported
None
  • 1.3.1 Info and Relationships
Test Results
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.

Success Criteria
Expected Reported
  • 3.1.2 Language of Parts
  • 3.1.2 Language of Parts

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.

Success Criteria
Expected Reported
  • 4.1.2 Name, Role, Value
  • 4.1.2 Name, Role, Value
Test Results
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.

Success Criteria
Expected Reported
  • 2.1.1 Keyboard
  • 2.1.1 Keyboard

*: 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.

Success Criteria
Expected Reported
  • 1.4.12 Text Spacing
  • 1.4.12 Text Spacing

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.

Success Criteria
Expected Reported
  • 1.4.12 Text Spacing
  • 1.4.12 Text Spacing

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.

Success Criteria
Expected Reported
  • 1.4.12 Text Spacing
  • 1.4.12 Text Spacing

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.

Success Criteria
Expected Reported
  • 1.3.5 Identify Input Purpose
  • 1.3.5 Identify Input Purpose

*: 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.

Success Criteria
Expected Reported
  • 4.1.2 Name, Role, Value
  • 4.1.2 Name, Role, Value

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.

Success Criteria
Expected Reported
None None
Test Results
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.

Success Criteria
Expected Reported
  • 4.1.2 Name, Role, Value
  • 4.1.2 Name, Role, Value

*: 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.

Success Criteria
Expected Reported
  • 3.1.1 Language of Page
  • 3.1.1 Language of Page
Test Results
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.

Success Criteria
Expected Reported
  • 2.4.2 Page Titled
  • 2.4.2 Page Titled

*: 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.

Success Criteria
Expected Reported
  • 1.1.1 Non-text Content
  • 4.1.2 Name, Role, Value
  • 1.1.1 Non-text Content
  • 4.1.2 Name, Role, Value

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.

Success Criteria
Expected Reported
  • 1.1.1 Non-text Content
  • 1.1.1 Non-text Content

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.

Success Criteria
Expected Reported
  • 4.1.2 Name, Role, Value
  • 2.4.4 Link Purpose (In Context)
  • 2.4.4 Link Purpose (In Context)
  • 4.1.2 Name, Role, Value

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.

Success Criteria
Expected Reported
  • 1.1.1 Non-text Content
  • 1.1.1 Non-text Content

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.

Success Criteria
Expected Reported
  • 4.1.2 Name, Role, Value
  • 4.1.2 Name, Role, Value
Test Results
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.

Success Criteria
Expected Reported
  • 1.3.1 Info and Relationships
  • 1.3.1 Info and Relationships

*: 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.

Success Criteria
Expected Reported
  • 4.1.2 Name, Role, Value
  • 4.1.2 Name, Role, Value
Test Results
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.

Success Criteria
Expected Reported
  • 2.2.1 Timing Adjustable
  • 2.2.1 Timing Adjustable

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.

Success Criteria
Expected Reported
  • 1.4.4 Resize text
  • 1.4.4 Resize text

*: 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.

Success Criteria
Expected Reported
  • 1.1.1 Non-text Content
  • 1.1.1 Non-text Content

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.

Success Criteria
Expected Reported
  • 3.1.1 Language of Page
  • 3.1.1 Language of Page
Test Results
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.

Success Criteria
Expected Reported
  • 2.1.1 Keyboard
  • 2.1.3 Keyboard (No Exception)
  • 2.1.1 Keyboard
  • 2.1.3 Keyboard (No Exception)

*: 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.

Success Criteria
Expected Reported
  • 1.4.3 Contrast (Minimum)
  • 1.4.3 Contrast (Minimum)

*: 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.

Success Criteria
Expected Reported
  • 1.4.6 Contrast (Enhanced)
  • 1.4.6 Contrast (Enhanced)

*: 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.

Success Criteria
Expected Reported
  • 2.2.4 Interruptions
  • 3.2.5 Change on Request
  • 2.2.4 Interruptions
  • 3.2.5 Change on Request

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.

Success Criteria
Expected Reported
None None

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.

Success Criteria
Expected Reported
  • 4.1.2 Name, Role, Value
  • 4.1.2 Name, Role, Value

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.

Success Criteria
Expected Reported
None None

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.

Success Criteria
Expected Reported
  • 4.1.2 Name, Role, Value
  • 4.1.2 Name, Role, Value
Back to Top

This is an unpublished draft preview that might include content that is not yet approved. The published website is at w3.org/WAI/.