Skip to content

Total Validator (+Browser) ACT Implementation

Number of Rules Implemented
Consistent Partially consistent
WCAG 2 rules 31 0
Proposed rules 10 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
Element in sequential focus order has visible focus 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 required context role Proposed Rule Consistent
ARIA required ID references exist Proposed Rule Consistent
ARIA required owned elements Proposed Rule Consistent
ARIA state or property is permitted Proposed Rule Consistent
Heading has non-empty accessible name Proposed Rule Consistent
Iframe elements with identical accessible names have equivalent purpose 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
Table header cell has assigned cells Proposed Rule Consistent
Visible label is part of accessible name Proposed Rule Consistent

About Total Validator (+Browser) Results

Results in this page are taken from a public test report published by Total Validator. Data is published using the EARL+JSON-LD data format.

Implementation Details

Role attribute has valid value

This rule is implemented by Total Validator (+Browser) using the E9651 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
  • 4.1.2 Name, Role, Value

ARIA state or property has valid value

This rule is implemented by Total Validator (+Browser) using the E9652 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
  • 4.1.2 Name, Role, Value

ARIA attribute is defined in WAI-ARIA

This rule is implemented by Total Validator (+Browser) using the E964 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
  • 4.1.2 Name, Role, Value

Element with lang attribute has valid language tag

This rule is implemented by Total Validator (+Browser) using the E9662 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 Total Validator (+Browser) using the E951 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

Iframe with interactive elements is not excluded from tab-order

This rule is implemented by Total Validator (+Browser) using the E9603 procedure. The implementation is fully consistent with the Iframe with interactive elements is not excluded from tab-order WCAG 2 rule. It covers 8 of the 9 examples. On 1 example 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
  • 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 Total Validator (+Browser) using the W917, and P917 procedures. Failed examples should be failed by at least one of these procedures. 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
Test Results
W917 P917
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Passed Example 6 passed passed
Failed Example 1 passed failed
Failed Example 2 passed failed
Failed Example 3 failed passed
Failed Example 4 failed passed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Inapplicable Example 4 passed passed
Inapplicable Example 5 passed passed
Inapplicable Example 6 passed passed
Inapplicable Example 7 passed passed
Inapplicable Example 8 passed passed
Inapplicable Example 9 passed passed

Important word spacing in style attributes is wide enough

This rule is implemented by Total Validator (+Browser) using the W917, and P917 procedures. Failed examples should be failed by at least one of these procedures. 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
Test Results
W917 P917
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Passed Example 6 passed passed
Failed Example 1 passed failed
Failed Example 2 passed failed
Failed Example 3 failed passed
Failed Example 4 failed passed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Inapplicable Example 4 passed passed
Inapplicable Example 5 passed passed
Inapplicable Example 6 passed passed
Inapplicable Example 7 passed passed
Inapplicable Example 8 passed passed
Inapplicable Example 9 passed passed

Important line height in style attributes is wide enough

This rule is implemented by Total Validator (+Browser) using the P917, and W917 procedures. Failed examples should be failed by at least one of these procedures. 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
Test Results
P917 W917
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Passed Example 6 passed passed
Passed Example 7 passed passed
Passed Example 8 passed passed
Failed Example 1 failed passed
Failed Example 2 failed passed
Failed Example 3 failed passed
Failed Example 4 failed passed
Failed Example 5 passed failed
Failed Example 6 passed failed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Inapplicable Example 4 passed passed
Inapplicable Example 5 passed passed
Inapplicable Example 6 passed passed
Inapplicable Example 7 passed passed
Inapplicable Example 8 passed passed
Inapplicable Example 9 passed passed
Inapplicable Example 10 passed passed

autocomplete attribute has valid value

This rule is implemented by Total Validator (+Browser) using the E9152 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 Total Validator (+Browser) using the E8661, and E951 procedures. Failed examples should be failed by at least one of these procedures. 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
Test Results
E8661 E951
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Passed Example 6 passed passed
Passed Example 7 passed passed
Failed Example 1 failed passed
Failed Example 2 failed passed
Failed Example 3 passed failed
Failed Example 4 failed passed
Failed Example 5 failed passed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Inapplicable Example 4 passed passed
Inapplicable Example 5 passed passed

Element marked as decorative is not exposed

This rule is implemented by Total Validator (+Browser) using the E961, and E863 procedures. Failed examples should be failed by at least one of these procedures. The implementation is fully consistent with the Element marked as decorative is not exposed WCAG 2 rule. It covers all 10 examples. The implementation correctly reports no success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected Reported
None None
Test Results
E961 E863
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Passed Example 6 passed passed
Failed Example 1 failed passed
Failed Example 2 passed failed
Failed Example 3 failed passed
Inapplicable Example 1 passed passed

Form field has non-empty accessible name

This rule is implemented by Total Validator (+Browser) using the E885, and E950 procedures. Failed examples should be failed by at least one of these procedures. 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
Test Results
E885 E950
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Passed Example 6 passed passed
Passed Example 7 passed passed
Failed Example 1 failed passed
Failed Example 2 failed passed
Failed Example 3 failed passed
Failed Example 4 failed passed
Failed Example 5 passed failed
Failed Example 6 passed failed
Failed Example 7 passed failed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Passed Example 8 passed passed
Failed Example 8 failed passed
Passed Example 8 * passed 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 Total Validator (+Browser) using the E9661 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

HTML page has non-empty title

This rule is implemented by Total Validator (+Browser) using the E870, and E869 procedures. Failed examples should be failed by at least one of these procedures. 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
Test Results
E870 E869
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Failed Example 1 passed failed
Failed Example 2 failed passed
Failed Example 3 passed failed
Failed Example 4 failed passed
Failed Example 5 failed passed
Inapplicable Example 1 passed passed
Passed Example 2 * passed passed
Failed Example 6 * passed 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 Total Validator (+Browser) using the W889 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 Total Validator (+Browser) using the E860 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 Total Validator (+Browser) using the P871, and P861 procedures. Failed examples should be failed by at least one of these procedures. 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)
  • 4.1.2 Name, Role, Value
  • 2.4.4 Link Purpose (In Context)
  • 2.4.9 Link Purpose (Link Only)
Test Results
P871 P861
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Passed Example 6 passed passed
Passed Example 7 passed passed
Passed Example 8 passed passed
Passed Example 9 passed passed
Passed Example 10 passed passed
Failed Example 1 failed passed
Failed Example 2 failed passed
Failed Example 3 failed passed
Failed Example 4 failed passed
Failed Example 5 failed passed
Failed Example 6 failed passed
Failed Example 7 failed passed
Failed Example 8 failed passed
Failed Example 9 passed failed
Failed Example 10 failed passed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Inapplicable Example 4 passed passed
Inapplicable Example 5 passed passed
Inapplicable Example 6 passed passed
Passed Example 11 passed passed
Failed Example 11 failed passed

SVG element with explicit role has non-empty accessible name

This rule is implemented by Total Validator (+Browser) using the E860 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 Total Validator (+Browser) using the E9542 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

Headers attribute specified on a cell refers to cells in the same table element

This rule is implemented by Total Validator (+Browser) using the E8952 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 Total Validator (+Browser) using the E9602 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

Meta element has no refresh delay

This rule is implemented by Total Validator (+Browser) using the E9011, and E8821 procedures. Failed examples should be failed by at least one of these procedures. 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
  • 2.2.4 Interruptions
  • 3.2.5 Change on Request
Test Results
E9011 E8821
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Failed Example 1 passed failed
Failed Example 2 failed passed
Failed Example 3 failed passed
Failed Example 4 failed passed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Inapplicable Example 4 passed passed
Inapplicable Example 5 passed passed
Inapplicable Example 6 passed passed
Inapplicable Example 7 passed passed
Inapplicable Example 8 passed passed

Meta viewport allows for zoom

This rule is implemented by Total Validator (+Browser) using the E916 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 Total Validator (+Browser) using the P865 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 Total Validator (+Browser) using the P967 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

Scrollable content can be reached with sequential focus navigation

This rule is implemented by Total Validator (+Browser) using the W900 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.

Element in sequential focus order has visible focus

This rule is implemented by Total Validator (+Browser) using the E914 procedure. The implementation is fully consistent with the Element in sequential focus order has visible focus WCAG 2 rule. It covers 5 of the 7 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
  • 2.4.7 Focus Visible
  • 2.4.7 Focus Visible
Test Results
E914
Passed Example 1 passed
Passed Example 2 passed
Passed Example 3 cannot tell
Passed Example 4 cannot tell
Failed Example 1 failed
Inapplicable Example 1 passed
Inapplicable Example 2 passed
Passed Example 4 * cannot tell
Inapplicable 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.

Text has minimum contrast

This rule is implemented by Total Validator (+Browser) using the P9121, I864, and I863 procedures. Failed examples should be failed by at least one of these procedures. 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)
  • 1.4.6 Contrast (Enhanced)
Test Results
P9121 I864 I863
Passed Example 1 passed passed passed
Passed Example 2 passed passed cannot tell
Passed Example 3 passed passed cannot tell
Passed Example 4 passed cannot tell passed
Passed Example 5 passed passed passed
Passed Example 6 passed passed passed
Passed Example 7 passed passed passed
Passed Example 8 passed passed passed
Passed Example 9 passed passed passed
Passed Example 10 passed passed passed
Passed Example 11 passed passed passed
Failed Example 1 failed passed passed
Failed Example 2 passed passed cannot tell
Failed Example 3 passed passed cannot tell
Failed Example 4 failed passed passed
Failed Example 5 failed passed passed
Failed Example 6 failed passed passed
Failed Example 7 passed passed cannot tell
Failed Example 8 failed passed passed
Failed Example 9 failed passed passed
Failed Example 10 failed passed passed
Inapplicable Example 1 passed passed passed
Inapplicable Example 2 passed passed passed
Inapplicable Example 3 passed passed passed
Inapplicable Example 4 passed passed passed
Inapplicable Example 5 passed passed passed
Inapplicable Example 6 passed passed passed
Inapplicable Example 7 passed passed passed
Inapplicable Example 8 passed passed passed
Inapplicable Example 9 passed passed passed
Inapplicable Example 10 passed passed passed
Inapplicable Example 11 passed passed passed
Passed Example 7 * passed passed passed
Failed Example 11 * passed cannot tell 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 enhanced contrast

This rule is implemented by Total Validator (+Browser) using the P9241, P9231, P9121, and I863 procedures. Failed examples should be failed by at least one of these procedures. 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)
  • 1.4.3 Contrast (Minimum)
Test Results
P9241 P9231 P9121 I863
Passed Example 1 passed passed passed passed
Passed Example 2 passed passed passed cannot tell
Passed Example 3 passed passed passed cannot tell
Passed Example 4 passed passed passed passed
Passed Example 5 passed passed passed passed
Passed Example 6 passed passed passed passed
Passed Example 7 passed passed passed passed
Passed Example 8 passed passed passed passed
Passed Example 9 passed passed passed passed
Passed Example 10 passed passed passed passed
Failed Example 1 failed passed passed passed
Failed Example 2 passed passed passed cannot tell
Failed Example 3 passed failed passed passed
Failed Example 4 passed passed failed passed
Failed Example 5 passed failed passed passed
Failed Example 6 passed passed passed cannot tell
Failed Example 7 failed passed passed passed
Failed Example 8 failed passed passed passed
Failed Example 9 failed passed passed passed
Failed Example 10 passed passed passed cannot tell
Failed Example 11 failed passed passed passed
Failed Example 12 failed passed passed passed
Failed Example 13 failed passed passed passed
Inapplicable Example 1 passed passed passed passed
Inapplicable Example 2 passed passed passed passed
Inapplicable Example 3 passed passed passed passed
Inapplicable Example 4 passed passed passed passed
Inapplicable Example 5 passed passed passed passed
Inapplicable Example 6 passed passed passed passed
Inapplicable Example 7 passed passed passed passed
Inapplicable Example 8 passed passed passed passed
Inapplicable Example 9 passed passed passed passed
Inapplicable Example 10 passed passed passed passed
Inapplicable Example 11 passed passed passed passed
Passed Example 6 * passed passed passed 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 Total Validator (+Browser) using the E9012, and E8821 procedures. Failed examples should be failed by at least one of these procedures. 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
  • 2.2.1 Timing Adjustable
Test Results
E9012 E8821
Passed Example 1 passed passed
Passed Example 2 passed passed
Failed Example 1 passed failed
Failed Example 2 failed passed
Failed Example 3 failed passed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Inapplicable Example 4 passed passed
Inapplicable Example 5 passed passed
Inapplicable Example 6 passed passed
Inapplicable Example 7 passed passed
Inapplicable Example 8 passed passed

ARIA required context role

This rule is implemented by Total Validator (+Browser) using the E963, and E962 procedures. Failed examples should be failed by at least one of these procedures. The implementation is fully consistent with the ARIA required context role proposed 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
  • 1.3.1 Info and Relationships
  • 1.3.1 Info and Relationships
Test Results
E963 E962
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Passed Example 6 passed passed
Failed Example 1 passed failed
Failed Example 2 failed passed
Failed Example 3 failed passed
Failed Example 4 failed passed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Inapplicable Example 4 passed passed
Inapplicable Example 5 passed passed

ARIA required ID references exist

This rule is implemented by Total Validator (+Browser) using the E9592 procedure. The implementation is fully consistent with the ARIA required ID references exist 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
None
  • 1.3.1 Info and Relationships
  • 4.1.2 Name, Role, Value

ARIA required owned elements

This rule is implemented by Total Validator (+Browser) using the E963, and P963 procedures. Failed examples should be failed by at least one of these procedures. The implementation is fully consistent with the ARIA required owned elements 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
  • 1.3.1 Info and Relationships
  • 1.3.1 Info and Relationships
Test Results
E963 P963
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Passed Example 6 passed passed
Failed Example 1 failed passed
Failed Example 2 failed failed
Failed Example 3 passed failed
Failed Example 4 failed passed
Failed Example 5 failed passed
Failed Example 6 passed failed
Failed Example 7 passed failed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed
Inapplicable Example 3 passed passed
Inapplicable Example 4 passed passed

ARIA state or property is permitted

This rule is implemented by Total Validator (+Browser) using the E958 procedure. The implementation is fully consistent with the ARIA state or property is permitted proposed rule. It covers all 16 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
  • 4.1.2 Name, Role, Value

Heading has non-empty accessible name

This rule is implemented by Total Validator (+Browser) using the E898, and E951 procedures. Failed examples should be failed by at least one of these procedures. The implementation is fully consistent with the Heading has non-empty accessible name proposed rule. It covers all 15 examples. The implementation correctly reports no success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected Reported
None None
Test Results
E898 E951
Passed Example 1 passed passed
Passed Example 2 passed passed
Passed Example 3 passed passed
Passed Example 4 passed passed
Passed Example 5 passed passed
Failed Example 1 failed passed
Failed Example 2 failed passed
Failed Example 3 failed passed
Failed Example 4 failed passed
Failed Example 5 failed passed
Failed Example 6 failed passed
Failed Example 7 passed failed
Failed Example 8 failed passed
Inapplicable Example 1 passed passed
Inapplicable Example 2 passed passed

Iframe elements with identical accessible names have equivalent purpose

This rule is implemented by Total Validator (+Browser) using the I873 procedure. The implementation is partially consistent with the Iframe elements with identical accessible names have equivalent purpose proposed rule. It covers 14 of the 23 examples. On 9 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

Iframe element has non-empty accessible name

This rule is implemented by Total Validator (+Browser) using the E8781 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 Total Validator (+Browser) using the E957 procedure. The implementation is fully consistent with the Element with role attribute has required states and properties proposed 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
None
  • 1.3.1 Info and Relationships
  • 4.1.2 Name, Role, Value

Summary element has non-empty accessible name

This rule is implemented by Total Validator (+Browser) using the E953 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

Table header cell has assigned cells

This rule is implemented by Total Validator (+Browser) using the W887 procedure. The implementation is fully consistent with the Table header cell has assigned cells proposed rule. It covers all 16 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

Visible label is part of accessible name

This rule is implemented by Total Validator (+Browser) using the E908 procedure. The implementation is fully consistent with the Visible label is part of accessible name proposed 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.5.3 Label in Name
  • 2.5.3 Label in Name
Back to Top