Webmate Accessibility Workbench ACT Implementation

Number of Rules Implemented
	Consistent	Partially consistent
WCAG 2 rules	29	1
Proposed rules	15	9

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 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
HTML page title is descriptive	WCAG 2 Rule	Consistent
Scrollable content can be reached with sequential focus navigation	WCAG 2 Rule	Consistent
Text has minimum contrast	WCAG 2 Rule	Consistent
Text has enhanced contrast	WCAG 2 Rule	Partial
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	Partial
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	Consistent
HTML element language subtag matches language	Proposed Rule	Consistent
Form field label is descriptive	Proposed Rule	Partial
Heading is descriptive	Proposed Rule	Consistent
Heading has non-empty accessible name	Proposed Rule	Consistent
HTML page language subtag matches default language	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
Link is descriptive	Proposed Rule	Consistent
Link in context is descriptive	Proposed Rule	Consistent
Links with identical accessible names have equivalent purpose	Proposed Rule	Consistent
Links with identical accessible names and same context serve equivalent purpose	Proposed Rule	Partial
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	Partial
Visible label is part of accessible name	Proposed Rule	Consistent

About Webmate Accessibility Workbench Results

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

Implementation Details

Role attribute has valid value

This rule is implemented by Webmate Accessibility Workbench using the 674b10-test 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	4.1.2 Name, Role, Value

Test Results
	674b10-test
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

ARIA state or property has valid value

This rule is implemented by Webmate Accessibility Workbench using the 6a7281-test procedure. The implementation is fully consistent with the ARIA state or property has valid value WCAG 2 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
	6a7281-test
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

ARIA attribute is defined in WAI-ARIA

This rule is implemented by Webmate Accessibility Workbench using the 5f99a7-test procedure. The implementation is fully consistent with the ARIA attribute is defined in WAI-ARIA 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
None	4.1.2 Name, Role, Value

Test Results
	5f99a7-test
Passed Example 1	cannot tell
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	cannot tell
Failed Example 1	failed
Failed Example 2	failed
Inapplicable Example 1	inapplicable

Element with lang attribute has valid language tag

This rule is implemented by Webmate Accessibility Workbench using the de46e4-test 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

Test Results
	de46e4-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Failed Example 8	failed
Failed Example 9	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed

Menuitem has non-empty accessible name

This rule is implemented by Webmate Accessibility Workbench using the m6b1q3-test 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
	m6b1q3-test
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

Iframe with interactive elements is not excluded from tab-order

This rule is implemented by Webmate Accessibility Workbench using the akn7bn-test procedure. The implementation is fully consistent with the Iframe with interactive elements is not excluded from tab-order WCAG 2 rule. It covers all 9 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
2.1.1 Keyboard	2.1.1 Keyboard

Test Results
	akn7bn-test
Passed Example 1	passed
Passed Example 2	passed
Failed Example 1	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 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.

Important letter spacing in style attributes is wide enough

This rule is implemented by Webmate Accessibility Workbench using the 24afc2-test procedure. The implementation is fully consistent with the Important letter spacing in style attributes is wide enough WCAG 2 rule. It covers 17 of the 19 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.4.12 Text Spacing	1.4.12 Text Spacing

Test Results
	24afc2-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	cannot tell
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	cannot tell
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Inapplicable Example 8	inapplicable
Inapplicable Example 9	passed

Important line height in style attributes is wide enough

This rule is implemented by Webmate Accessibility Workbench using the 78fd32-test procedure. The implementation is fully consistent with the Important line height in style attributes is wide enough WCAG 2 rule. It covers all 24 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
1.4.12 Text Spacing	1.4.12 Text Spacing

Test Results
	78fd32-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Inapplicable Example 8	passed
Inapplicable Example 9	passed
Inapplicable Example 10	passed

autocomplete attribute has valid value

This rule is implemented by Webmate Accessibility Workbench using the 73f2c2-test 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
	73f2c2-test
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	inapplicable
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
Inapplicable Example 8 *	inapplicable
Inapplicable Example 9 *	inapplicable

*: 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 Webmate Accessibility Workbench using the 97a4e1-test procedure. The implementation is fully consistent with the Button has non-empty accessible name WCAG 2 rule. It covers all 17 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

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

Test Results
	97a4e1-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	inapplicable
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	passed
Inapplicable Example 4	inapplicable
Inapplicable Example 5	passed

Element marked as decorative is not exposed

This rule is implemented by Webmate Accessibility Workbench using the 46ca7f-test 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
	46ca7f-test
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 Webmate Accessibility Workbench using the e086e5-test procedure. The implementation is fully consistent with the Form field has non-empty accessible name WCAG 2 rule. It covers all 19 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

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

Test Results
	e086e5-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Passed Example 8	passed
Failed Example 8	failed
Passed Example 8 *	passed

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

HTML page lang attribute has valid language tag

This rule is implemented by Webmate Accessibility Workbench using the bf051a-test 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
	bf051a-test
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 Webmate Accessibility Workbench using the 2779a5-test 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
	2779a5-test
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
Passed Example 2 *	passed
Failed Example 6 *	untested

*: 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 Webmate Accessibility Workbench using the 59796f-test 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
	59796f-test
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 Webmate Accessibility Workbench using the 23a2a8-test 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

Test Results
	23a2a8-test
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

Link has non-empty accessible name

This rule is implemented by Webmate Accessibility Workbench using the c487ae-test procedure. The implementation is fully consistent with the Link has non-empty accessible name WCAG 2 rule. It covers all 28 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

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

Test Results
	c487ae-test
Passed Example 1	passed
Passed Example 2	inapplicable
Passed Example 3	inapplicable
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Passed Example 9	passed
Passed Example 10	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Failed Example 8	failed
Failed Example 9	failed
Failed Example 10	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	inapplicable
Inapplicable Example 6	inapplicable
Passed Example 11	passed
Failed Example 11	failed

SVG element with explicit role has non-empty accessible name

This rule is implemented by Webmate Accessibility Workbench using the 7d6734-test 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
	7d6734-test
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 Webmate Accessibility Workbench using the 307n5z-test 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
	307n5z-test
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	inapplicable

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

This rule is implemented by Webmate Accessibility Workbench using the a25f45-test 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

Test Results
	a25f45-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	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 Webmate Accessibility Workbench using the 6cfa84-test 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
	6cfa84-test
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 Webmate Accessibility Workbench using the bc659a-test 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
	bc659a-test
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	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 Webmate Accessibility Workbench using the b4f0c3-test 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

Test Results
	b4f0c3-test
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 *	cannot tell
Failed Example 7 *	cannot tell

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

Object element rendering non-text content has non-empty accessible name

This rule is implemented by Webmate Accessibility Workbench using the 8fc3b6-test 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
	8fc3b6-test
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 Webmate Accessibility Workbench using the b5c3f8-test 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
	b5c3f8-test
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 Webmate Accessibility Workbench using the c4a8a4-test procedure. The implementation is fully consistent with the HTML page title is descriptive 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.2 Page Titled	2.4.2 Page Titled

Test Results
	c4a8a4-test
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	inapplicable

Scrollable content can be reached with sequential focus navigation

This rule is implemented by Webmate Accessibility Workbench using the 0ssw9k-test 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
	0ssw9k-test
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
Passed Example 2 *	passed
Passed Example 3 *	untested
Inapplicable Example 2 *	inapplicable
Inapplicable Example 3 *	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.

Text has minimum contrast

This rule is implemented by Webmate Accessibility Workbench using the afw4f7-test 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
	afw4f7-test
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	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
Passed Example 7 *	cannot tell
Failed Example 11 *	untested

*: 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 Webmate Accessibility Workbench using the 09o5cg-test procedure. The implementation is partially consistent with the Text has enhanced contrast WCAG 2 rule. It covers 18 of the 34 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
1.4.6 Contrast (Enhanced)	1.4.6 Contrast (Enhanced) 1.4.3 Contrast (Minimum)

Test Results
	09o5cg-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	cannot tell
Passed Example 7	passed
Passed Example 8	passed
Passed Example 9	passed
Passed Example 10	passed
Failed Example 1	passed
Failed Example 2	failed
Failed Example 3	cannot tell
Failed Example 4	failed
Failed Example 5	cannot tell
Failed Example 6	cannot tell
Failed Example 7	passed
Failed Example 8	passed
Failed Example 9	passed
Failed Example 10	cannot tell
Failed Example 11	passed
Failed Example 12	cannot tell
Failed Example 13	cannot tell
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	cannot tell
Inapplicable Example 7	cannot tell
Inapplicable Example 8	inapplicable
Inapplicable Example 9	cannot tell
Inapplicable Example 10	inapplicable
Inapplicable Example 11	cannot tell
Passed Example 6 *	cannot tell

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

Meta element has no refresh delay (no exception)

This rule is implemented by Webmate Accessibility Workbench using the bisz58-test procedure. The implementation is fully consistent with the Meta element has no refresh delay (no exception) WCAG 2 rule. It covers all 13 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
2.2.4 Interruptions 3.2.5 Change on Request	2.2.4 Interruptions 3.2.5 Change on Request 2.2.1 Timing Adjustable

Test Results
	bisz58-test
Passed Example 1	passed
Passed Example 2	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	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

ARIA required context role

This rule is implemented by Webmate Accessibility Workbench using the ff89c9-test procedure. 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
	ff89c9-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	inapplicable

ARIA required ID references exist

This rule is implemented by Webmate Accessibility Workbench using the in6db8-test procedure. The implementation is fully consistent with the ARIA required ID references exist proposed 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
None	4.1.2 Name, Role, Value

Test Results
	in6db8-test
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	cannot tell
Inapplicable Example 3	inapplicable

ARIA required owned elements

This rule is implemented by Webmate Accessibility Workbench using the bc4a75-test 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
	bc4a75-test
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
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 Webmate Accessibility Workbench using the 5c01ea-test procedure. The implementation is partially consistent with the ARIA state or property is permitted proposed rule. It covers 16 of the 19 examples. For 3 examples no results were reported. This can happen when examples are newer then the test results. The implementation correctly reports 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
	5c01ea-test
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
Passed Example 11	passed
Passed Example 12	untested
Passed Example 13	untested
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	untested
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable

Block of repeated content is collapsible

This rule is implemented by Webmate Accessibility Workbench using the 3e12e1-test 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
	3e12e1-test
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 Webmate Accessibility Workbench using the cf77f2-test procedure. The implementation is partially consistent with the Bypass Blocks of Repeated Content proposed rule. It covers 13 of the 14 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.1 Bypass Blocks	2.4.1 Bypass Blocks

Test Results
	cf77f2-test
Passed Example 1	inapplicable
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	inapplicable
Passed Example 8	inapplicable
Passed Example 9	passed
Passed Example 10	passed
Passed Example 11	inapplicable
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 Webmate Accessibility Workbench using the 047fe0-test 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
	047fe0-test
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 Webmate Accessibility Workbench using the ye5d6e-test 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
	ye5d6e-test
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 Webmate Accessibility Workbench using the b40fd1-test procedure. The implementation is fully consistent with the Document has a landmark with non-repeated content proposed rule. It covers 7 of the 8 examples. On 1 example the implementation cannot tell the outcome. This is often because of technical limitations in tools. The implementation correctly reports no success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	None

Test Results
	b40fd1-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	cannot tell
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Inapplicable Example 1	inapplicable

HTML element language subtag matches language

This rule is implemented by Webmate Accessibility Workbench using the off6ek-test procedure. The implementation is fully consistent with the HTML element language subtag matches language 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
3.1.2 Language of Parts	3.1.2 Language of Parts

Test Results
	off6ek-test
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
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	inapplicable

Form field label is descriptive

This rule is implemented by Webmate Accessibility Workbench using the cc0f0a-test procedure. The implementation is partially consistent with the Form field label is descriptive proposed rule. It covers 13 of the 14 examples. On 1 example 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
2.4.6 Headings and Labels	2.4.6 Headings and Labels 3.3.2 Labels or Instructions

Test Results
	cc0f0a-test
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	cannot tell
Inapplicable Example 3	inapplicable

Heading is descriptive

This rule is implemented by Webmate Accessibility Workbench using the b49b2e-test procedure. The implementation is fully consistent with the Heading 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
	b49b2e-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable

Heading has non-empty accessible name

This rule is implemented by Webmate Accessibility Workbench using the ffd0e9-test 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
	ffd0e9-test
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

HTML page language subtag matches default language

This rule is implemented by Webmate Accessibility Workbench using the ucwvc8-test procedure. The implementation is fully consistent with the HTML page language subtag matches default language 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
3.1.1 Language of Page	3.1.1 Language of Page

Test Results
	ucwvc8-test
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
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable
Inapplicable Example 5	inapplicable
Inapplicable Example 6	inapplicable

Iframe elements with identical accessible names have equivalent purpose

This rule is implemented by Webmate Accessibility Workbench using the 4b1c6c-test 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
	4b1c6c-test
Passed Example 1	cannot tell
Passed Example 2	passed
Passed Example 3	cannot tell
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	passed
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 Webmate Accessibility Workbench using the cae760-test 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
	cae760-test
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

Link is descriptive

This rule is implemented by Webmate Accessibility Workbench using the aizyf1-test procedure. The implementation is fully consistent with the Link is descriptive 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
2.4.9 Link Purpose (Link Only)	2.4.9 Link Purpose (Link Only)

Test Results
	aizyf1-test
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
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable

Link in context is descriptive

This rule is implemented by Webmate Accessibility Workbench using the 5effbb-test procedure. The implementation is fully consistent with the Link in context is descriptive proposed 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
2.4.4 Link Purpose (In Context)	2.4.4 Link Purpose (In Context) 2.4.9 Link Purpose (Link Only)

Test Results
	5effbb-test
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
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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable

Links with identical accessible names have equivalent purpose

This rule is implemented by Webmate Accessibility Workbench using the b20e66-test procedure. The implementation is fully consistent with the Links with identical accessible names have equivalent purpose proposed 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
2.4.9 Link Purpose (Link Only)	2.4.9 Link Purpose (Link Only)

Test Results
	b20e66-test
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
Passed Example 11	inapplicable
Passed Example 12	inapplicable
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	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable

Links with identical accessible names and same context serve equivalent purpose

This rule is implemented by Webmate Accessibility Workbench using the fd3a94-test procedure. The implementation is partially consistent with the Links with identical accessible names and same context serve equivalent purpose proposed rule. It covers 16 of the 24 examples. On 3 examples the implementation cannot tell the outcome. This is often because of technical limitations in tools. For 1 example no results were reported. This can happen when examples are newer then the test results. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
2.4.4 Link Purpose (In Context)	2.4.4 Link Purpose (In Context)

Test Results
	fd3a94-test
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	passed
Failed Example 2	cannot tell
Failed Example 3	passed
Failed Example 4	cannot tell
Failed Example 5	passed
Failed Example 6	passed
Failed Example 7	untested
Failed Example 8	cannot tell
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	passed
Inapplicable Example 4	inapplicable
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	inapplicable

Element with role attribute has required states and properties

This rule is implemented by Webmate Accessibility Workbench using the 4e8ab6-test 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
	4e8ab6-test
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
Failed Example 6	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	passed
Inapplicable Example 3	inapplicable

Summary element has non-empty accessible name

This rule is implemented by Webmate Accessibility Workbench using the 2t702h-test 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

Test Results
	2t702h-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Inapplicable Example 1	inapplicable
Inapplicable Example 2	inapplicable
Inapplicable Example 3	inapplicable
Inapplicable Example 4	inapplicable

Table header cell has assigned cells

This rule is implemented by Webmate Accessibility Workbench using the d0f69e-test procedure. The implementation is partially consistent with the Table header cell has assigned cells proposed rule. It covers 13 of the 16 examples. On 3 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
	d0f69e-test
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	cannot tell
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 Webmate Accessibility Workbench using the 2ee8b8-test 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

Test Results
	2ee8b8-test
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	inapplicable
Passed Example 6	inapplicable
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