Axe DevTools Pro ACT Implementation

Number of Rules Implemented
	Consistent	Partially consistent
WCAG 2 rules	27	0
Proposed rules	12	10

Implemented Rules

Rule Name	Type	Consistency
autocomplete attribute has valid value	WCAG 2 Rule	Consistent
Button has non-empty accessible name	WCAG 2 Rule	Consistent
Element with lang attribute has valid language tag	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
Letter spacing in style attributes is not !important	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
HTML page title is descriptive	WCAG 2 Rule	Consistent
Iframe with interactive elements is not excluded from tab-order	WCAG 2 Rule	Consistent
Image accessible name is descriptive	WCAG 2 Rule	Consistent
Menuitem has non-empty accessible name	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
ARIA attribute is defined in WAI-ARIA	Proposed Rule	Consistent
ARIA required context role	Proposed Rule	Consistent
ARIA required owned elements	Proposed Rule	Consistent
ARIA state or property is permitted	Proposed Rule	Consistent
ARIA state or property has valid value	Proposed Rule	Consistent
Block of repeated content is collapsible	Proposed Rule	Partial
Bypass Blocks of Repeated Content	Proposed Rule	Partial
Document has heading for non-repeated content	Proposed Rule	Partial
Document has an instrument to move focus to non-repeated content	Proposed Rule	Partial
Document has a landmark with non-repeated content	Proposed Rule	Partial
Form field label is descriptive	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
Image not in the accessibility tree is decorative	Proposed Rule	Partial
Error message describes invalid form field value	Proposed Rule	Partial
Links with identical accessible names have equivalent purpose	Proposed Rule	Partial
Meta element has no refresh delay (no exception)	Proposed Rule	Consistent
Role attribute has valid value	Proposed Rule	Consistent
Element with role attribute has required states and properties	Proposed Rule	Consistent
Table header cell has assigned cells	Proposed Rule	Partial
Visible label is part of accessible name	Proposed Rule	Consistent

About Axe DevTools Pro Results

Axe DevTools Pro combines the automated results of axe-core, and results from axe Intelligent Guided Test (IGT) tools. Tools can produced multiple issue types. The ID of each issue type is given as the name of the procedure, with the tool that returns it in brackets. For example alt-text-not-meaningful (Images) is the alt-text-not-meaningful issue type reported by the Images tool.

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

Implementation Details

autocomplete attribute has valid value

This rule is implemented by Axe DevTools Pro using the autocomplete-valid 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

Test Results
	autocomplete-valid
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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	inapplicable
Inapplicable Example 6	inapplicable
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	inapplicable
Inapplicable Example 9	inapplicable

Button has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the button-name, and aria-command-name 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
	button-name	aria-command-name
Passed Example 1	passed	inapplicable
Passed Example 2	inapplicable	inapplicable
Passed Example 3	passed	inapplicable
Passed Example 4	inapplicable	passed
Passed Example 5	passed	inapplicable
Passed Example 6	passed	inapplicable
Passed Example 7	inapplicable	inapplicable
Failed Example 1	failed	inapplicable
Failed Example 2	failed	inapplicable
Failed Example 3	inapplicable	failed
Failed Example 4	failed	inapplicable
Failed Example 5	failed	inapplicable
Inapplicable Example 1	inapplicable	inapplicable
Inapplicable Example 2	inapplicable	inapplicable
Inapplicable Example 3	passed	inapplicable
Inapplicable Example 4	inapplicable	inapplicable
Inapplicable Example 5	passed	inapplicable

Element with lang attribute has valid language tag

This rule is implemented by Axe DevTools Pro using the valid-lang procedure. The implementation is fully consistent with the Element with lang attribute has valid language tag WCAG 2 rule. It covers all 31 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

Test Results
	valid-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	passed, failed
Failed Example 7	failed
Failed Example 8	failed
Failed Example 9	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
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 *	passed, failed
Failed Example 7 *	failed
Inapplicable Example 5 *	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 marked as decorative is not exposed

This rule is implemented by Axe DevTools Pro using the presentation-role-conflict procedure. 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
	presentation-role-conflict
Passed Example 1	passed
Passed Example 2	inapplicable
Passed Example 3	inapplicable
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Inapplicable Example 1	inapplicable

Form field has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the label, aria-input-field-name, and select-name 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
	label	aria-input-field-name	select-name
Passed Example 1	passed	inapplicable	inapplicable
Passed Example 2	passed	inapplicable	inapplicable
Passed Example 3	inapplicable	inapplicable	passed
Passed Example 4	passed	inapplicable	inapplicable
Passed Example 5	passed	inapplicable	inapplicable
Passed Example 6	inapplicable	passed	inapplicable
Passed Example 7	inapplicable	inapplicable	inapplicable
Failed Example 1	failed	inapplicable	inapplicable
Failed Example 2	failed	inapplicable	inapplicable
Failed Example 3	failed	inapplicable	inapplicable
Failed Example 4	inapplicable	inapplicable	failed
Failed Example 5	inapplicable	failed	inapplicable
Failed Example 6	inapplicable	failed	inapplicable
Failed Example 7	inapplicable	failed	inapplicable
Inapplicable Example 1	inapplicable	inapplicable	inapplicable
Inapplicable Example 2	inapplicable	inapplicable	inapplicable
Inapplicable Example 3	inapplicable	inapplicable	passed
Passed Example 8	passed	inapplicable	inapplicable
Failed Example 8	failed	inapplicable	inapplicable

HTML page lang attribute has valid language tag

This rule is implemented by Axe DevTools Pro using the html-lang-valid 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
	html-lang-valid
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	inapplicable

HTML page has non-empty title

This rule is implemented by Axe DevTools Pro using the document-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

Test Results
	document-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	inapplicable

Image button has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the input-image-alt 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

Test Results
	input-image-alt
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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	inapplicable

Image has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the image-alt, and role-img-alt procedures. Failed examples should be failed by at least one of these procedures. 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

Test Results
	image-alt	role-img-alt
Passed Example 1	passed	inapplicable
Passed Example 2	inapplicable	passed
Passed Example 3	inapplicable	passed
Passed Example 4	passed	inapplicable
Passed Example 5	passed	inapplicable
Passed Example 6	passed	inapplicable
Passed Example 7	passed	inapplicable
Passed Example 8	passed	inapplicable
Failed Example 1	failed	inapplicable
Failed Example 2	inapplicable	failed
Failed Example 3	failed	inapplicable
Failed Example 4	failed	inapplicable
Failed Example 5	failed	inapplicable
Inapplicable Example 1	inapplicable	inapplicable
Inapplicable Example 2	inapplicable	inapplicable
Inapplicable Example 3	inapplicable	inapplicable
Inapplicable Example 4	inapplicable	inapplicable
Inapplicable Example 5	inapplicable	inapplicable

Letter spacing in style attributes is not !important

This rule is implemented by Axe DevTools Pro using the avoid-inline-spacing procedure. The implementation is fully consistent with the Letter spacing in style attributes is not !important WCAG 2 rule. It covers 17 of the 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
	avoid-inline-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
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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	passed
Passed Example 5 *	passed
Passed Example 6 *	passed, failed
Inapplicable Example 2 *	failed

*: These examples are not yet approved for the rule. Results on these outcomes are not taken into consideration determining the consistency and coverage.

Link has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the link-name, and area-alt 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)	2.4.4 Link Purpose (In Context) 4.1.2 Name, Role, Value

Test Results
	link-name	area-alt
Passed Example 1	passed	inapplicable
Passed Example 2	inapplicable	inapplicable
Passed Example 3	inapplicable	inapplicable
Passed Example 4	passed	inapplicable
Passed Example 5	passed	inapplicable
Passed Example 6	passed	inapplicable
Passed Example 7	passed	inapplicable
Passed Example 8	passed	inapplicable
Passed Example 9	passed	inapplicable
Passed Example 10	inapplicable	passed
Failed Example 1	failed	inapplicable
Failed Example 2	failed	inapplicable
Failed Example 3	failed	inapplicable
Failed Example 4	failed	inapplicable
Failed Example 5	failed	inapplicable
Failed Example 6	failed	inapplicable
Failed Example 7	failed	inapplicable
Failed Example 8	failed	inapplicable
Failed Example 9	inapplicable	failed
Failed Example 10	failed	inapplicable
Inapplicable Example 1	passed	inapplicable
Inapplicable Example 2	inapplicable	inapplicable
Inapplicable Example 3	inapplicable	inapplicable
Inapplicable Example 4	inapplicable	inapplicable
Inapplicable Example 5	inapplicable	inapplicable
Inapplicable Example 6	inapplicable	inapplicable
Passed Example 11	passed	inapplicable
Failed Example 11	failed	inapplicable

SVG element with explicit role has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the svg-img-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

Test Results
	svg-img-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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable

Element with presentational children has no focusable content

This rule is implemented by Axe DevTools Pro using the nested-interactive 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
	nested-interactive
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	passed, failed
Failed Example 2	failed
Failed Example 3	passed, failed
Inapplicable Example 1	inapplicable

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

This rule is implemented by Axe DevTools Pro using the td-headers-attr 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 18 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
	td-headers-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	passed
Passed Example 8	passed
Failed Example 1	failed
Failed Example 2	passed, failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	inapplicable
Inapplicable Example 3	passed
Inapplicable Example 4	inapplicable
Inapplicable Example 5	inapplicable
Inapplicable Example 6 *	inapplicable

*: 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 Axe DevTools Pro using the aria-hidden-focus 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-focus
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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable

Meta element has no refresh delay

This rule is implemented by Axe DevTools Pro 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

Test Results
	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	passed, failed
Failed Example 4	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
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 Axe DevTools Pro using the meta-viewport procedure. The implementation is fully consistent with the Meta viewport allows for zoom WCAG 2 rule. It covers 14 of the 16 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

Test Results
	meta-viewport
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	inapplicable
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 *	passed
Failed Example 7 *	passed

*: 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 Axe DevTools Pro using the object-alt 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

Test Results
	object-alt
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	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	inapplicable
Inapplicable Example 8	inapplicable

HTML page has lang attribute

This rule is implemented by Axe DevTools Pro using the html-has-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
	html-has-lang
Passed Example 1	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable

HTML page title is descriptive

This rule is implemented by Axe DevTools Pro using the title-not-meaningful (structure) procedure. The implementation is fully consistent with the HTML page title is descriptive WCAG 2 rule. It covers 6 of the 7 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.4.2 Page Titled	2.4.2 Page Titled

Test Results
	title-not-meaningful (structure)
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	cannot tell

Iframe with interactive elements is not excluded from tab-order

This rule is implemented by Axe DevTools Pro using the frame-focusable-content 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. 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

Test Results
	frame-focusable-content
Passed Example 1	inapplicable
Passed Example 2	inapplicable
Failed Example 1	failed
Inapplicable Example 1	passed
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	passed
Inapplicable Example 5 *	inapplicable
Inapplicable 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 accessible name is descriptive

This rule is implemented by Axe DevTools Pro using the alt-text-short-text-not-meaningful (Images) procedure. The implementation is fully consistent with the Image accessible name is descriptive WCAG 2 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.1.1 Non-text Content	1.1.1 Non-text Content

Test Results
	alt-text-short-text-not-meaningful (Images)
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
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	inapplicable
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Inapplicable Example 8	passed
Inapplicable Example 9	inapplicable
Inapplicable Example 10	passed

Menuitem has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the button-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
	button-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	inapplicable
Inapplicable Example 2	inapplicable

Scrollable content can be reached with sequential focus navigation

This rule is implemented by Axe DevTools Pro using the scrollable-region-focusable 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)

Test Results
	scrollable-region-focusable
Passed Example 1	passed
Passed Example 2	passed
Failed Example 1	failed
Failed Example 2	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	inapplicable
Inapplicable Example 6	inapplicable

Element in sequential focus order has visible focus

This rule is implemented by Axe DevTools Pro using the focus-indicator-missing (keyboard) procedure. The implementation is fully consistent with the Element in sequential focus order has visible focus 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
2.4.7 Focus Visible	2.4.7 Focus Visible

Test Results
	focus-indicator-missing (keyboard)
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Failed Example 1	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable

Text has minimum contrast

This rule is implemented by Axe DevTools Pro using the color-contrast procedure. The implementation is fully consistent with the Text has minimum contrast WCAG 2 rule. It covers 25 of the 32 examples. On 7 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)

Test Results
	color-contrast
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	inapplicable
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	passed, failed
Failed Example 9	failed
Failed Example 10	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	cannot tell
Inapplicable Example 4	cannot tell
Inapplicable Example 5	inapplicable
Inapplicable Example 6	inapplicable
Inapplicable Example 7	inapplicable
Inapplicable Example 8	inapplicable
Inapplicable Example 9	inapplicable
Inapplicable Example 10	inapplicable
Inapplicable Example 11	inapplicable

Text has enhanced contrast

This rule is implemented by Axe DevTools Pro using the color-contrast-enhanced, and color-contrast 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 27 of the 34 examples. On 7 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
	color-contrast-enhanced	color-contrast
Passed Example 1	passed	passed
Passed Example 2	passed	cannot tell
Passed Example 3	passed	cannot tell
Passed Example 4	passed	passed
Passed Example 5	passed	passed
Passed Example 6	inapplicable	inapplicable
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	passed	cannot tell
Failed Example 3	failed	passed
Failed Example 4	passed	failed
Failed Example 5	failed	passed
Failed Example 6	passed	cannot tell
Failed Example 7	failed	passed
Failed Example 8	failed	passed
Failed Example 9	failed	passed
Failed Example 10	passed	cannot tell
Failed Example 11	passed, failed	passed
Failed Example 12	failed	passed
Failed Example 13	failed	passed
Inapplicable Example 1	inapplicable	inapplicable
Inapplicable Example 2	inapplicable	inapplicable
Inapplicable Example 3	passed	cannot tell
Inapplicable Example 4	passed	cannot tell
Inapplicable Example 5	inapplicable	inapplicable
Inapplicable Example 6	inapplicable	inapplicable
Inapplicable Example 7	inapplicable	inapplicable
Inapplicable Example 8	inapplicable	inapplicable
Inapplicable Example 9	inapplicable	inapplicable
Inapplicable Example 10	inapplicable	inapplicable
Inapplicable Example 11	inapplicable	inapplicable

ARIA attribute is defined in WAI-ARIA

This rule is implemented by Axe DevTools Pro using the aria-valid-attr procedure. The implementation is fully consistent with the ARIA attribute is defined in WAI-ARIA proposed 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	4.1.2 Name, Role, Value

Test Results
	aria-valid-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	inapplicable

ARIA required context role

This rule is implemented by Axe DevTools Pro using the aria-required-parent, and aria-required-children 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 14 of the 15 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
1.3.1 Info and Relationships	1.3.1 Info and Relationships

Test Results
	aria-required-parent	aria-required-children
Passed Example 1	passed	passed
Passed Example 2	passed	inapplicable
Passed Example 3	passed	passed
Passed Example 4	passed	passed
Passed Example 5	passed	passed
Passed Example 6	passed	passed
Failed Example 1	failed	inapplicable
Failed Example 2	failed	failed
Failed Example 3	passed	failed
Failed Example 4	failed	cannot tell
Inapplicable Example 1	inapplicable	inapplicable
Inapplicable Example 2	inapplicable	inapplicable
Inapplicable Example 3	inapplicable	inapplicable
Inapplicable Example 4	inapplicable	inapplicable
Inapplicable Example 5	passed	inapplicable

ARIA required owned elements

This rule is implemented by Axe DevTools Pro using the aria-required-children procedure. 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
	aria-required-children
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	passed, failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	passed

ARIA state or property is permitted

This rule is implemented by Axe DevTools Pro using the aria-allowed-attr, and aria-prohibited-attr procedures. Failed examples should be failed by at least one of these procedures. 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	4.1.2 Name, Role, Value

Test Results
	aria-allowed-attr	aria-prohibited-attr
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
Passed Example 11	passed	passed
Failed Example 1	failed	passed
Failed Example 2	failed	passed
Failed Example 3	passed	failed
Inapplicable Example 1	inapplicable	inapplicable
Inapplicable Example 2	inapplicable	inapplicable

ARIA state or property has valid value

This rule is implemented by Axe DevTools Pro using the aria-valid-attr-value procedure. The implementation is fully consistent with the ARIA state or property has valid value proposed rule. It covers 20 of the 21 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
None	4.1.2 Name, Role, Value

Test Results
	aria-valid-attr-value
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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	cannot tell
Inapplicable Example 4	inapplicable

Block of repeated content is collapsible

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Block of repeated content is collapsible proposed rule. It covers 1 of the 8 examples. On 7 examples the implementation cannot tell the outcome. This is often because of technical limitations in tools. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	2.4.1 Bypass Blocks

Test Results
	bypass
Passed Example 1	cannot tell
Passed Example 2	cannot tell
Passed Example 3	cannot tell
Passed Example 4	cannot tell
Failed Example 1	cannot tell
Failed Example 2	cannot tell
Failed Example 3	cannot tell
Inapplicable Example 1	inapplicable

Bypass Blocks of Repeated Content

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Bypass Blocks of Repeated Content proposed rule. It covers 9 of the 14 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
2.4.1 Bypass Blocks	2.4.1 Bypass Blocks

Test Results
	bypass
Passed Example 1	cannot tell
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	cannot tell
Passed Example 8	cannot tell
Passed Example 9	passed
Passed Example 10	passed
Passed Example 11	cannot tell
Passed Example 12	passed
Failed Example 1	cannot tell
Inapplicable Example 1	inapplicable

Document has heading for non-repeated content

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Document has heading for non-repeated content proposed rule. It covers 10 of the 14 examples. On 2 examples the implementation cannot tell the outcome. This is often because of technical limitations in tools. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	2.4.1 Bypass Blocks

Test Results
	bypass
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	inapplicable
Failed Example 1	cannot tell
Failed Example 2	passed
Failed Example 3	cannot tell
Failed Example 4	passed
Inapplicable Example 1	inapplicable

Document has an instrument to move focus to non-repeated content

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Document has an instrument to move focus to non-repeated content proposed rule. It covers 8 of the 12 examples. On 2 examples the implementation cannot tell the outcome. This is often because of technical limitations in tools. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	2.4.1 Bypass Blocks

Test Results
	bypass
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	cannot tell
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Failed Example 1	cannot tell
Failed Example 2	passed
Failed Example 3	passed
Inapplicable Example 1	inapplicable

Document has a landmark with non-repeated content

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Document has a landmark with non-repeated content proposed rule. It covers 5 of the 8 examples. On 3 examples the implementation cannot tell the outcome. This is often because of technical limitations in tools. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	2.4.1 Bypass Blocks

Test Results
	bypass
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	inapplicable
Failed Example 1	cannot tell
Failed Example 2	cannot tell
Failed Example 3	cannot tell
Inapplicable Example 1	inapplicable

Form field label is descriptive

This rule is implemented by Axe DevTools Pro using the label-visible-not-descriptive (forms) procedure. The implementation is fully consistent with the Form field label is descriptive proposed rule. It covers all 14 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
2.4.6 Headings and Labels	2.4.6 Headings and Labels

Test Results
	label-visible-not-descriptive (forms)
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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable

Heading has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the empty-heading procedure. 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
	empty-heading
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
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable

Iframe elements with identical accessible names have equivalent purpose

This rule is implemented by Axe DevTools Pro using the frame-title-unique procedure. The implementation is partially consistent with the Iframe elements with identical accessible names have equivalent purpose proposed rule. It covers 11 of the 23 examples. On 10 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
	frame-title-unique
Passed Example 1	cannot tell
Passed Example 2	passed
Passed Example 3	inapplicable
Passed Example 4	cannot tell
Passed Example 5	cannot tell
Passed Example 6	cannot tell
Passed Example 7	cannot tell
Passed Example 8	cannot tell
Passed Example 9	cannot tell
Passed Example 10	cannot tell
Failed Example 1	cannot tell
Failed Example 2	inapplicable
Failed Example 3	passed
Failed Example 4	cannot tell
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	passed
Inapplicable Example 6	inapplicable
Inapplicable Example 7	inapplicable
Inapplicable Example 8	inapplicable
Inapplicable Example 9	inapplicable

Iframe element has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the frame-title 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

Test Results
	frame-title
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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	passed

Image not in the accessibility tree is decorative

This rule is implemented by Axe DevTools Pro using the alt-text-missing + semantic-hidden (images) procedure. The implementation is partially consistent with the Image not in the accessibility tree is decorative proposed rule. It covers 17 of the 20 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

Test Results
	alt-text-missing + semantic-hidden (images)
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	passed
Failed Example 4	passed
Failed Example 5	passed
Inapplicable Example 1	passed
Inapplicable Example 2	inapplicable
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	inapplicable

Error message describes invalid form field value

This rule is implemented by Axe DevTools Pro using the form-error-required-unclear + instructions-not-included (forms) procedure. The implementation is partially consistent with the Error message describes invalid form field value proposed rule. It covers 7 of the 9 examples. For 1 example no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
3.3.1 Error Identification	3.3.2 Labels or Instructions

Test Results
	form-error-required-unclear + instructions-not-included (forms)
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	untested
Failed Example 3	failed
Failed Example 4	passed
Failed Example 5	failed
Inapplicable Example 1	inapplicable

Links with identical accessible names have equivalent purpose

This rule is implemented by Axe DevTools Pro using the identical-links-same-purpose procedure. The implementation is partially consistent with the Links with identical accessible names have equivalent purpose proposed rule. It covers 10 of the 21 examples. On 11 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.9 Link Purpose (Link Only)	2.4.9 Link Purpose (Link Only)

Test Results
	identical-links-same-purpose
Passed Example 1	passed
Passed Example 2	cannot tell
Passed Example 3	passed
Passed Example 4	cannot tell
Passed Example 5	passed
Passed Example 6	cannot tell
Passed Example 7	cannot tell
Passed Example 8	cannot tell
Passed Example 9	passed
Passed Example 10	passed
Passed Example 11	passed
Passed Example 12	passed
Failed Example 1	cannot tell
Failed Example 2	cannot tell
Failed Example 3	cannot tell
Failed Example 4	cannot tell
Failed Example 5	cannot tell
Failed Example 6	cannot tell
Inapplicable Example 1	inapplicable
Inapplicable Example 2	passed
Inapplicable Example 3	inapplicable

Meta element has no refresh delay (no exception)

This rule is implemented by Axe DevTools Pro using the meta-refresh-no-exceptions, and meta-refresh 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) proposed 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
	meta-refresh-no-exceptions	meta-refresh
Passed Example 1	passed	passed
Passed Example 2	passed	passed
Failed Example 1	passed	failed
Failed Example 2	failed	passed
Failed Example 3	passed, failed	passed
Inapplicable Example 1	inapplicable	inapplicable
Inapplicable Example 2	inapplicable	inapplicable
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

Role attribute has valid value

This rule is implemented by Axe DevTools Pro using the aria-roles procedure. The implementation is fully consistent with the Role attribute has valid value proposed 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	4.1.2 Name, Role, Value

Test Results
	aria-roles
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	inapplicable

Element with role attribute has required states and properties

This rule is implemented by Axe DevTools Pro 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 15 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	4.1.2 Name, Role, Value

Test Results
	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	passed, failed
Failed Example 6	passed, failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	passed
Inapplicable Example 3	inapplicable

Table header cell has assigned cells

This rule is implemented by Axe DevTools Pro using the th-has-data-cells procedure. The implementation is partially consistent with the Table header cell has assigned cells proposed rule. It covers 13 of the 16 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
1.3.1 Info and Relationships	1.3.1 Info and Relationships

Test Results
	th-has-data-cells
Passed Example 1	passed
Passed Example 2	inapplicable
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Failed Example 1	cannot tell
Failed Example 2	cannot tell
Failed Example 3	inapplicable
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	inapplicable
Inapplicable Example 7	inapplicable

Visible label is part of accessible name

This rule is implemented by Axe DevTools Pro using the label-content-name-mismatch procedure. The implementation is fully consistent with the Visible label is part of accessible name proposed rule. It covers 12 of the 13 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.5.3 Label in Name	2.5.3 Label in Name

Test Results
	label-content-name-mismatch
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	cannot tell
Passed Example 6	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable