SortSite ACT Implementation

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

Implemented Rules

Rule Name	Type	Consistency
Role attribute has valid value	WCAG 2 Rule	Consistent
ARIA state or property has valid value	WCAG 2 Rule	Consistent
ARIA attribute is defined in WAI-ARIA	WCAG 2 Rule	Consistent
Element with lang attribute has valid language tag	WCAG 2 Rule	Consistent
Menuitem has non-empty accessible name	WCAG 2 Rule	Consistent
Iframe with interactive elements is not excluded from tab-order	WCAG 2 Rule	Consistent
Important letter spacing in style attributes is wide enough	WCAG 2 Rule	Consistent
Important word spacing in style attributes is wide enough	WCAG 2 Rule	Consistent
Important line height in style attributes is wide enough	WCAG 2 Rule	Consistent
autocomplete attribute has valid value	WCAG 2 Rule	Consistent
Button has non-empty accessible name	WCAG 2 Rule	Consistent
Element marked as decorative is not exposed	WCAG 2 Rule	Consistent
Form field has non-empty accessible name	WCAG 2 Rule	Consistent
HTML page lang attribute has valid language tag	WCAG 2 Rule	Consistent
HTML page has non-empty title	WCAG 2 Rule	Consistent
Image button has non-empty accessible name	WCAG 2 Rule	Consistent
Image has non-empty accessible name	WCAG 2 Rule	Consistent
Link has non-empty accessible name	WCAG 2 Rule	Consistent
SVG element with explicit role has non-empty accessible name	WCAG 2 Rule	Consistent
Element with presentational children has no focusable content	WCAG 2 Rule	Consistent
Headers attribute specified on a cell refers to cells in the same table element	WCAG 2 Rule	Consistent
Element with aria-hidden has no content in sequential focus navigation	WCAG 2 Rule	Consistent
Meta element has no refresh delay	WCAG 2 Rule	Consistent
Meta viewport allows for zoom	WCAG 2 Rule	Consistent
Object element rendering non-text content has non-empty accessible name	WCAG 2 Rule	Consistent
HTML page has lang attribute	WCAG 2 Rule	Consistent
Scrollable content can be reached with sequential focus navigation	WCAG 2 Rule	Consistent
Element in sequential focus order has visible focus	WCAG 2 Rule	Consistent
Text has minimum contrast	WCAG 2 Rule	Consistent
Text has enhanced contrast	WCAG 2 Rule	Consistent
ARIA required context role	Proposed Rule	Consistent
ARIA required ID references exist	Proposed Rule	Consistent
ARIA required owned elements	Proposed Rule	Consistent
ARIA state or property is permitted	Proposed Rule	Consistent
Audio or video element avoids automatically playing audio	Proposed Rule	Consistent
Orientation of the page is not restricted using CSS transforms	Proposed Rule	Consistent
Heading has non-empty accessible name	Proposed Rule	Consistent
Iframe element has non-empty accessible name	Proposed Rule	Consistent
Link in context is descriptive	Proposed Rule	Consistent
Element with role attribute has required states and properties	Proposed Rule	Consistent
Summary element has non-empty accessible name	Proposed Rule	Consistent
Table header cell has assigned cells	Proposed Rule	Consistent
Visible label is part of accessible name	Proposed Rule	Consistent

About SortSite Results

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

Implementation Details

Role attribute has valid value

This rule is implemented by SortSite using the W3cHtml5Error-RnvErAval-role 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 no success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	None

Test Results
	W3cHtml5Error-RnvErAval-role
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed

ARIA state or property has valid value

This rule is implemented by SortSite using the AccAriaAttributeInvalid procedure. The implementation is fully consistent with the ARIA state or property has valid value WCAG 2 rule. It covers all 21 examples. The implementation correctly reports no success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	None

Test Results
	AccAriaAttributeInvalid
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Passed Example 9	passed
Passed Example 10	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed

ARIA attribute is defined in WAI-ARIA

This rule is implemented by SortSite using the W3cHtml5Error-RnvErAkey-aria-* procedure. The implementation is fully consistent with the ARIA attribute is defined in WAI-ARIA WCAG 2 rule. It covers all 7 examples. The implementation correctly reports no success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	None

Test Results
	W3cHtml5Error-RnvErAkey-aria-*
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Failed Example 1	failed
Failed Example 2	failed
Inapplicable Example 1	passed

Element with lang attribute has valid language tag

This rule is implemented by SortSite using the AccHtmlElementLangInvalid 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
	AccHtmlElementLangInvalid
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Failed Example 8	failed
Failed Example 9	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed

Menuitem has non-empty accessible name

This rule is implemented by SortSite using the AccAriaMenuitemBlank 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
	AccAriaMenuitemBlank
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Failed Example 1	failed
Failed Example 2	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed

Iframe with interactive elements is not excluded from tab-order

This rule is implemented by SortSite using the AccHtmlIframeTabindexInteractive 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
	AccHtmlIframeTabindexInteractive
Passed Example 1	passed
Passed Example 2	passed
Failed Example 1	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 6 *	passed

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

Important letter spacing in style attributes is wide enough

This rule is implemented by SortSite using the AccCssLetterSpacingImportant procedure. The implementation is fully consistent with the Important letter spacing in style attributes is wide enough WCAG 2 rule. It covers all 19 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
1.4.12 Text Spacing	1.4.12 Text Spacing

Test Results
	AccCssLetterSpacingImportant
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Inapplicable Example 8	passed
Inapplicable Example 9	passed

Important word spacing in style attributes is wide enough

This rule is implemented by SortSite using the AccCssWordSpacingImportant procedure. The implementation is fully consistent with the Important word spacing in style attributes is wide enough WCAG 2 rule. It covers all 19 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
1.4.12 Text Spacing	1.4.12 Text Spacing

Test Results
	AccCssWordSpacingImportant
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Inapplicable Example 8	passed
Inapplicable Example 9	passed

Important line height in style attributes is wide enough

This rule is implemented by SortSite using the AccCssLineHeightImportant 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
	AccCssLineHeightImportant
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 SortSite using the AccHtmlAutocompleteInvalid 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
	AccHtmlAutocompleteInvalid
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Passed Example 9	passed
Failed Example 6	failed
Failed Example 7	failed
Failed Example 8	failed
Failed Example 9	failed
Failed Example 10	failed
Inapplicable Example 8	passed
Inapplicable Example 9	passed
Inapplicable Example 8 *	passed
Inapplicable Example 9 *	passed

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

Button has non-empty accessible name

This rule is implemented by SortSite using the AccHtmlButtonBlank 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
	AccHtmlButtonBlank
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed

Element marked as decorative is not exposed

This rule is implemented by SortSite using the AccAriaRoleConflict 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
	AccAriaRoleConflict
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
Inapplicable Example 1	passed

Form field has non-empty accessible name

This rule is implemented by SortSite using the AccHtmlControlLabelMissing 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
	AccHtmlControlLabelMissing
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Passed Example 8	passed
Failed Example 8	failed
Passed Example 8 *	passed

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

HTML page lang attribute has valid language tag

This rule is implemented by SortSite using the AccHtmlPageLangInvalid 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
	AccHtmlPageLangInvalid
Passed Example 1	passed
Passed Example 2	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed

HTML page has non-empty title

This rule is implemented by SortSite using the AccPageNoTitle 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
	AccPageNoTitle
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Inapplicable Example 1	passed
Passed Example 2 *	passed
Failed Example 6 *	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 SortSite using the AccHtmlInputImageNoAlt 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
	AccHtmlInputImageNoAlt
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed

Image has non-empty accessible name

This rule is implemented by SortSite using the AccHtmlImgNoAlt 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
	AccHtmlImgNoAlt
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed

Link has non-empty accessible name

This rule is implemented by SortSite using the AccHtmlLinkTextBlank 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
	AccHtmlLinkTextBlank
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Passed Example 9	passed
Passed Example 10	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Failed Example 8	failed
Failed Example 9	failed
Failed Example 10	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Passed Example 11	passed
Failed Example 11	failed

SVG element with explicit role has non-empty accessible name

This rule is implemented by SortSite using the AccHtmlSvgElementNoName 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
	AccHtmlSvgElementNoName
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed

Element with presentational children has no focusable content

This rule is implemented by SortSite using the AccAriaPresentationalChildrenFocusable 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
	AccAriaPresentationalChildrenFocusable
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Inapplicable Example 1	passed

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

This rule is implemented by SortSite using the AccWcag2-F90-1 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
	AccWcag2-F90-1
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6 *	passed

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

Element with aria-hidden has no content in sequential focus navigation

This rule is implemented by SortSite using the AccAriaHiddenFocusableContent procedure. The implementation is fully consistent with the Element with aria-hidden has no content in sequential focus navigation 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
4.1.2 Name, Role, Value	4.1.2 Name, Role, Value

Test Results
	AccAriaHiddenFocusableContent
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	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed

Meta element has no refresh delay

This rule is implemented by SortSite using the AccHtmlMetaRefresh 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 2.2.4 Interruptions 3.2.5 Change on Request

Test Results
	AccHtmlMetaRefresh
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Inapplicable Example 8	passed

Meta viewport allows for zoom

This rule is implemented by SortSite using the AccHtmlMetaViewportNoZoom 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
	AccHtmlMetaViewportNoZoom
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Passed Example 2 *	passed
Passed Example 5 *	passed
Failed Example 2 *	failed
Failed Example 3 *	failed
Failed Example 7 *	failed

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

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

This rule is implemented by SortSite using the AccHtmlObjectNoAccName 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
	AccHtmlObjectNoAccName
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Inapplicable Example 8	passed

HTML page has lang attribute

This rule is implemented by SortSite using the AccPageLangMissing 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
	AccPageLangMissing
Passed Example 1	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed

Scrollable content can be reached with sequential focus navigation

This rule is implemented by SortSite using the AccCssScrollableNoFocus 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
	AccCssScrollableNoFocus
Passed Example 1	passed
Passed Example 2	passed
Failed Example 1	failed
Failed Example 2	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Passed Example 2 *	passed
Passed Example 3 *	untested
Inapplicable Example 2 *	passed
Inapplicable Example 3 *	passed
Inapplicable Example 6 *	passed

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

Element in sequential focus order has visible focus

This rule is implemented by SortSite using the AccWcag2-F78-1 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
	AccWcag2-F78-1
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Failed Example 1	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Passed Example 4 *	passed
Inapplicable Example 2 *	passed

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

Text has minimum contrast

This rule is implemented by SortSite using the AccHtmlContrastMinimum procedure. The implementation is fully consistent with the Text has minimum contrast WCAG 2 rule. It covers all 32 examples. 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
	AccHtmlContrastMinimum
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
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Failed Example 8	failed
Failed Example 9	failed
Failed Example 10	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Inapplicable Example 8	passed
Inapplicable Example 9	passed
Inapplicable Example 10	passed
Inapplicable Example 11	passed
Passed Example 7 *	passed
Failed Example 11 *	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 SortSite using the AccHtmlContrastEnhanced procedure. The implementation is fully consistent with the Text has enhanced contrast WCAG 2 rule. It covers all 34 examples. 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)

Test Results
	AccHtmlContrastEnhanced
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Passed Example 7	passed
Passed Example 8	passed
Passed Example 9	passed
Passed Example 10	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Failed Example 6	failed
Failed Example 7	failed
Failed Example 8	failed
Failed Example 9	failed
Failed Example 10	failed
Failed Example 11	failed
Failed Example 12	failed
Failed Example 13	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed
Inapplicable Example 6	passed
Inapplicable Example 7	passed
Inapplicable Example 8	passed
Inapplicable Example 9	passed
Inapplicable Example 10	passed
Inapplicable Example 11	passed
Passed Example 6 *	passed

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

ARIA required context role

This rule is implemented by SortSite using the W3cHtml5AriaRequiredParentRoles-* 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
	W3cHtml5AriaRequiredParentRoles-*
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed

ARIA required ID references exist

This rule is implemented by SortSite using the W3cHtml5AriaControls procedure. The implementation is fully consistent with the ARIA required ID references exist proposed rule. It covers all 9 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
	W3cHtml5AriaControls
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

ARIA required owned elements

This rule is implemented by SortSite using the W3cHtml5AriaRequiredChildRole-* 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
	W3cHtml5AriaRequiredChildRole-*
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	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed

ARIA state or property is permitted

This rule is implemented by SortSite using the W3cHtml5Error-RnvErAkey-aria-* procedure. The implementation is fully consistent with the ARIA state or property is permitted proposed rule. It covers all 16 examples. The implementation correctly reports no success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	None

Test Results
	W3cHtml5Error-RnvErAkey-aria-*
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
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed

Audio or video element avoids automatically playing audio

This rule is implemented by SortSite using the AccWcag2-F23-1 procedure. The implementation is fully consistent with the Audio or video element avoids automatically playing audio proposed 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
1.4.2 Audio Control	1.4.2 Audio Control

Test Results
	AccWcag2-F23-1
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed

Orientation of the page is not restricted using CSS transforms

This rule is implemented by SortSite using the AccCssTransformOrientationLock procedure. The implementation is fully consistent with the Orientation of the page is not restricted using CSS transforms 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
1.3.4 Orientation	1.3.4 Orientation

Test Results
	AccCssTransformOrientationLock
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed
Inapplicable Example 5	passed

Heading has non-empty accessible name

This rule is implemented by SortSite using the AccHtmlHeadingEmpty 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
	AccHtmlHeadingEmpty
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	passed
Inapplicable Example 2	passed

Iframe element has non-empty accessible name

This rule is implemented by SortSite using the AccHtmlFrameTitleMissing 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
	AccHtmlFrameTitleMissing
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed

Link in context is descriptive

This rule is implemented by SortSite using the AccHtmlLinkTextAmbiguousContext 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)

Test Results
	AccHtmlLinkTextAmbiguousContext
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	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed

Element with role attribute has required states and properties

This rule is implemented by SortSite using the W3cHtml5Error-RnvErAmis-* 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 no success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected	Reported
None	None

Test Results
	W3cHtml5Error-RnvErAmis-*
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	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed

Summary element has non-empty accessible name

This rule is implemented by SortSite using the AccHtmlSummaryBlank 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
	AccHtmlSummaryBlank
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed

Table header cell has assigned cells

This rule is implemented by SortSite using the AccHtmlTableMissingCells procedure. The implementation is fully consistent with the Table header cell has assigned cells proposed rule. It covers all 16 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

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

Test Results
	AccHtmlTableMissingCells
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
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

Visible label is part of accessible name

This rule is implemented by SortSite using the AccHtmlControlLabelInAccName 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
	AccHtmlControlLabelInAccName
Passed Example 1	passed
Passed Example 2	passed
Passed Example 3	passed
Passed Example 4	passed
Passed Example 5	passed
Passed Example 6	passed
Failed Example 1	failed
Failed Example 2	failed
Failed Example 3	failed
Failed Example 4	failed
Failed Example 5	failed
Inapplicable Example 1	passed
Inapplicable Example 2	passed
Inapplicable Example 3	passed
Inapplicable Example 4	passed