This page is under development and has not been approved by the working group.
Number of Rules Implemented
|
Consistent |
Partially consistent |
| WCAG 2 rules |
11 |
0 |
| Proposed rules |
9 |
10 |
Implemented Rules
About Alfa Results
Results in this page are taken from a public
test report
published by Siteimprove.
Data is published using the
EARL+JSON-LD data format.
Implementation Details
autocomplete attribute has valid value
This rule is implemented by Alfa using the
sia-r10 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 Alfa using the
sia-r12 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 Alfa using the
sia-r7 procedure.
The implementation is
fully consistent with the
Element with lang attribute has valid language tag
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 |
|
|
|
Element marked as decorative is not exposed
This rule is implemented by Alfa using the
sia-r86 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 Alfa using the
sia-r8 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 lang attribute has valid language tag
This rule is implemented by Alfa using the
sia-r5 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 Alfa using the
sia-r6 procedure.
The implementation is
fully consistent with the
HTML page lang and xml:lang attributes have matching values
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 |
|
|
|
HTML page has non-empty title
This rule is implemented by Alfa using the
sia-r1 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 Alfa using the
sia-r28 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 Alfa using the
sia-r2 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 |
|
|
|
Link has non-empty accessible name
This rule is implemented by Alfa using the
sia-r11 procedure.
The implementation is
fully consistent with the
Link has non-empty accessible name
WCAG 2 rule.
It covers all 26 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)
|
-
2.4.4
Link Purpose (In Context)
-
2.4.9
Link Purpose (Link Only)
-
4.1.2
Name, Role, Value
-
|
aria-* attribute is defined in WAI-ARIA
This rule is implemented by Alfa using the
sia-r20 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
|
ARIA required context role
This rule is implemented by Alfa using the
sia-r42 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 state or property is permitted
This rule is implemented by Alfa using the
sia-r18 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 which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
None
|
|
ARIA state or property has valid value
This rule is implemented by Alfa using the
sia-r19 procedure.
The implementation is partially
consistent with the
ARIA state or property has valid value
proposed rule.
It covers 23 of the 24 examples.
The implementation correctly reports no success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
None
|
None
|
Orientation of the page is not restricted using CSS transform property
This rule is implemented by Alfa using the
sia-r44 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 |
|
|
|
svg element with explicit role has non-empty accessible name
This rule is implemented by Alfa using the
sia-r43 procedure.
The implementation is
fully consistent with the
svg element with explicit role has non-empty accessible name
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 Alfa using the
sia-r64 procedure.
The implementation is partially
consistent with the
Heading has non-empty accessible name
proposed rule.
It covers all 15 examples.
The implementation reports different success criteria as failed from what is expected by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
-
1.3.1
Info and Relationships
|
-
1.3.1
Info and Relationships
-
2.4.6
Headings and Labels
-
|
id attribute value is unique
This rule is implemented by Alfa using the
sia-r3 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 elements with identical accessible names have equivalent purpose
This rule is implemented by Alfa using the
sia-r15 procedure.
The implementation is partially
consistent with the
iframe elements with identical accessible names have equivalent purpose
proposed rule.
It covers 14 of the 23 examples.
On 9 examples
the implementation cannot tell the outcome. This is often because of technical
limitations in tools.
The implementation reports different success criteria as failed from what is expected by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
None
|
Links with identical accessible names have equivalent purpose
This rule is implemented by Alfa using the
sia-r41 procedure.
The implementation is partially
consistent with the
Links with identical accessible names have equivalent purpose
proposed rule.
It covers 8 of the 21 examples.
On 13 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 |
-
2.4.9
Link Purpose (Link Only)
|
None
|
Menuitem has non-empty accessible name
This rule is implemented by Alfa using the
sia-r94 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 element has no refresh delay
This rule is implemented by Alfa using the
sia-r9 procedure.
The implementation is partially
consistent with the
meta element has no refresh delay
proposed rule.
It covers 13 of the 15 examples.
For 2 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 |
-
2.2.1
Timing Adjustable
-
2.2.4
Interruptions
-
3.2.5
Change on Request
|
-
2.2.1
Timing Adjustable
-
2.2.4
Interruptions
-
3.2.5
Change on Request
-
-
|
meta element has no refresh delay (no exception)
This rule is implemented by Alfa using the
sia-r96 procedure.
The implementation is partially
consistent with the
meta element has no refresh delay (no exception)
proposed rule.
It covers 12 of the 14 examples.
For 2 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 |
-
2.2.4
Interruptions
-
3.2.5
Change on Request
|
-
2.2.4
Interruptions
-
3.2.5
Change on Request
-
-
|
meta viewport allows for zoom
This rule is implemented by Alfa using the
sia-r47 procedure.
The implementation is partially
consistent with the
meta viewport allows for zoom
proposed rule.
It covers all 11 examples.
The implementation reports different success criteria as failed from what is expected by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
-
1.4.4
Resize text
-
1.4.10
Reflow
|
Object element rendering non-text content has non-empty accessible name
This rule is implemented by Alfa using the
sia-r63 procedure.
The implementation is
fully consistent with the
Object element rendering non-text content has non-empty accessible name
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 |
|
|
|
Element with presentational children has no focusable content
This rule is implemented by Alfa using the
sia-r90 procedure.
The implementation is partially
consistent with the
Element with presentational children has no focusable content
proposed rule.
It covers all 7 examples.
The implementation reports different success criteria as failed from what is expected by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
|
|
-
1.3.1
Info and Relationships
-
4.1.2
Name, Role, Value
|
Element in sequential focus order has visible focus
This rule is implemented by Alfa using the
sia-r65 procedure.
The implementation is partially
consistent with the
Element in sequential focus order has visible focus
proposed rule.
It covers 7 of the 9 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
|
Table header cell has assigned cells
This rule is implemented by Alfa using the
sia-r46 procedure.
The implementation is partially
consistent with the
Table header cell has assigned cells
proposed rule.
It covers 15 of the 16 examples.
The implementation correctly reports which success criteria are failed by this rule.
See understanding ACT consistency.
Success Criteria
| Expected | Reported |
-
1.3.1
Info and Relationships
|
-
1.3.1
Info and Relationships
-
|
headers attribute specified on a cell refers to cells in the same table element
This rule is implemented by Alfa using the
sia-r45 procedure.
The implementation is
fully consistent with the
headers attribute specified on a cell refers to cells in the same table element
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
-
|