SortSite ACT Implementation
This page is under development and has not been approved by the working group.
Number of Rules Implemented
|
Consistent |
Partially consistent |
| WCAG 2 rules |
16 |
1 |
| Proposed rules |
19 |
4 |
Implemented Rules
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
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 20 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
|
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 |
|
|
|
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 |
|
|
|
*: These examples are not yet approved for the rule. Results on these outcomes are not
taken into consideration determining the consistency and coverage.
Element marked as decorative is not exposed
This rule is implemented by 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
|
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 17 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
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 |
|
|
|
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 |
|
|
|
HTML page lang and xml:lang attributes have matching values
This rule is implemented by SortSite using the
AccPageXmlLangMismatch procedure.
The implementation is partially
consistent with the
HTML page lang and xml:lang attributes have matching values
WCAG 2 rule.
It covers 11 of the 12 examples.
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 |
|
|
|
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 |
|
|
|
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
|
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 |
|
|
|
Letter spacing in style attributes is not !important
This rule is implemented by SortSite using the
AccCssLetterSpacingImportant procedure.
The implementation is
fully consistent with the
Letter spacing in style attributes is not !important
WCAG 2 rule.
It covers all 16 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
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)
-
2.4.9
Link Purpose (Link Only)
|
-
4.1.2
Name, Role, Value
-
2.4.4
Link Purpose (In Context)
-
2.4.9
Link Purpose (Link Only)
|
Word spacing in style attributes is not !important
This rule is implemented by SortSite using the
AccCssWordSpacingImportant procedure.
The implementation is
fully consistent with the
Word spacing in style attributes is not !important
WCAG 2 rule.
It covers all 16 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
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 |
|
|
|
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 |
|
|
|
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
|
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
proposed 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
|
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
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 |
|
|
|
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
|
ARIA required owned elements
This rule is implemented by SortSite using the
W3cHtml5AriaRequiredChildRole-* procedure.
The implementation is partially
consistent with the
ARIA required owned elements
proposed rule.
It covers 18 of the 19 examples.
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 |
-
1.3.1
Info and Relationships
|
-
1.3.1
Info and Relationships
|
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 15 examples.
The implementation correctly reports no success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
None
|
None
|
ARIA state or property has valid value
This rule is implemented by SortSite using the
W3cHtml5Error-RnvErAval-aria-* procedure.
The implementation is
fully consistent with the
ARIA state or property has valid value
proposed rule.
It covers all 24 examples.
The implementation correctly reports no success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
None
|
None
|
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 |
|
|
|
Orientation of the page is not restricted using CSS transform property
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 transform property
proposed rule.
It covers all 10 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
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 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
|
Id attribute value is unique
This rule is implemented by SortSite using the
W3cHtml5Error-errDuplicateId procedure.
The implementation is
fully consistent with the
Id attribute value is unique
proposed rule.
It covers all 10 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
Iframe element has non-empty accessible name
This rule is implemented by SortSite using the
AccHtmlFrameTitleMissing procedure.
The implementation is partially
consistent with the
Iframe element has non-empty accessible name
proposed rule.
It covers 9 of the 10 examples.
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 |
|
|
|
Line height in style attributes is not !important
This rule is implemented by SortSite using the
AccCssLineHeightImportant procedure.
The implementation is
fully consistent with the
Line height in style attributes is not !important
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 |
|
|
|
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.9
Link Purpose (Link Only)
|
-
2.4.4
Link Purpose (In Context)
-
2.4.9
Link Purpose (Link Only)
|
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
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 |
|
|
|
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
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 |
|
|
|
Object element rendering non-text content has non-empty accessible name
This rule is implemented by SortSite using the
AccHtmlObjectNoAccName procedure.
The implementation is partially
consistent with the
Object element rendering non-text content has non-empty accessible name
proposed rule.
It covers 14 of the 18 examples.
For 4 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 |
|
|
|
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
proposed rule.
It covers all 10 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
-
1.3.1
Info and Relationships
|
-
1.3.1
Info and Relationships
|
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 8 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|
Scrollable element is keyboard accessible
This rule is implemented by SortSite using the
AccCssScrollableNoFocus procedure.
The implementation is
fully consistent with the
Scrollable element is keyboard accessible
proposed rule.
It covers all 10 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
-
2.1.1
Keyboard
-
2.1.3
Keyboard (No Exception)
|
-
2.1.1
Keyboard
-
2.1.3
Keyboard (No Exception)
|
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
|
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
proposed 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.4.3
Contrast (Minimum)
-
1.4.6
Contrast (Enhanced)
|
-
1.4.3
Contrast (Minimum)
-
1.4.6
Contrast (Enhanced)
|
Text has enhanced contrast
This rule is implemented by SortSite using the
AccHtmlContrastEnhanced procedure.
The implementation is partially
consistent with the
Text has enhanced contrast
proposed rule.
It covers 28 of the 29 examples.
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 |
-
1.4.6
Contrast (Enhanced)
|
-
1.4.6
Contrast (Enhanced)
|
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 13 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
|