Skip to content

Alfa Fully Automated ACT Implementation

Number of Rules Implemented
Consistent Partially consistent
WCAG 2 rules 19 1
Proposed rules 10 5

Implemented Rules

Rule Name Type Consistency
autocomplete attribute has valid value WCAG 2 Rule Consistent
Button has non-empty accessible name WCAG 2 Rule Consistent
Element with lang attribute has valid language tag WCAG 2 Rule Consistent
Element marked as decorative is not exposed WCAG 2 Rule Consistent
Form field has non-empty accessible name WCAG 2 Rule Consistent
HTML page lang attribute has valid language tag WCAG 2 Rule Consistent
HTML page has non-empty title WCAG 2 Rule Consistent
Image button has non-empty accessible name WCAG 2 Rule Consistent
Image has non-empty accessible name WCAG 2 Rule Consistent
Letter spacing in style attributes is not !important WCAG 2 Rule Consistent
Link has non-empty accessible name WCAG 2 Rule Consistent
SVG element with explicit role has non-empty accessible name WCAG 2 Rule Consistent
Element with presentational children has no focusable content WCAG 2 Rule Consistent
Headers attribute specified on a cell refers to cells in the same table element WCAG 2 Rule Consistent
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
Menuitem has non-empty accessible name WCAG 2 Rule Consistent
Element in sequential focus order has visible focus WCAG 2 Rule Partial
ARIA attribute is defined in WAI-ARIA Proposed Rule Consistent
ARIA required context role Proposed Rule Consistent
ARIA required ID references exist Proposed Rule Consistent
ARIA required owned elements Proposed Rule Partial
ARIA state or property is permitted Proposed Rule Consistent
ARIA state or property has valid value Proposed Rule Consistent
Orientation of the page is not restricted using CSS transforms Proposed Rule Consistent
Heading has non-empty accessible name Proposed Rule Partial
Iframe elements with identical accessible names have equivalent purpose Proposed Rule Partial
Iframe element has non-empty accessible name Proposed Rule Consistent
Links with identical accessible names have equivalent purpose Proposed Rule Partial
Meta element has no refresh delay (no exception) Proposed Rule Consistent
Role attribute has valid value Proposed Rule Consistent
Element with role attribute has required states and properties Proposed Rule Consistent
Table header cell has assigned cells Proposed Rule Partial

About Alfa (fully automated) 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 (fully automated) using the sia-r10 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

Button has non-empty accessible name

This rule is implemented by Alfa (fully automated) 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
  • 4.1.2 Name, Role, Value
  • 4.1.2 Name, Role, Value

Element with lang attribute has valid language tag

This rule is implemented by Alfa (fully automated) 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 31 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected Reported
  • 3.1.2 Language of Parts
  • 3.1.2 Language of Parts

*: 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 Alfa (fully automated) 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 (fully automated) 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 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

HTML page lang attribute has valid language tag

This rule is implemented by Alfa (fully automated) 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
  • 3.1.1 Language of Page
  • 3.1.1 Language of Page
Test Results
sia-r5
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 Alfa (fully automated) 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
  • 2.4.2 Page Titled
  • 2.4.2 Page Titled

Image button has non-empty accessible name

This rule is implemented by Alfa (fully automated) 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
Test Results
sia-r28
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 Alfa (fully automated) 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
  • 1.1.1 Non-text Content
  • 1.1.1 Non-text Content
Test Results
sia-r2
Passed Example 1 passed
Passed Example 2 passed
Passed Example 3 passed
Passed Example 4 passed
Passed Example 5 inapplicable
Passed Example 6 inapplicable
Passed Example 7 inapplicable
Passed Example 8 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
Inapplicable Example 5 inapplicable

Letter spacing in style attributes is not !important

This rule is implemented by Alfa (fully automated) using the sia-r91 procedure. The implementation is fully consistent with the Letter spacing in style attributes is not !important WCAG 2 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
  • 1.4.12 Text Spacing
  • 1.4.12 Text Spacing
Test Results
sia-r91
Passed Example 1 inapplicable
Passed Example 2 passed
Passed Example 3 passed
Passed Example 4 passed
Passed Example 5 passed
Passed Example 6 inapplicable
Passed Example 7 inapplicable
Passed Example 8 inapplicable
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
Passed Example 5 * untested
Passed Example 6 * untested
Inapplicable Example 2 * untested

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

Link has non-empty accessible name

This rule is implemented by Alfa (fully automated) using the sia-r11 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.4 Link Purpose (In Context)
  • 2.4.9 Link Purpose (Link Only)
  • 4.1.2 Name, Role, Value

SVG element with explicit role has non-empty accessible name

This rule is implemented by Alfa (fully automated) using the sia-r43 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
sia-r43
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 Alfa (fully automated) using the sia-r90 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
sia-r90
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 Alfa (fully automated) 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 WCAG 2 rule. It covers all 18 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

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

*: 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

This rule is implemented by Alfa (fully automated) using the sia-r9 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

Meta viewport allows for zoom

This rule is implemented by Alfa (fully automated) using the sia-r47 procedure. The implementation is fully consistent with the Meta viewport allows for zoom WCAG 2 rule. It covers 11 of the 16 examples. For 5 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
  • 1.4.4 Resize text
  • 1.4.4 Resize text
Test Results
sia-r47
Passed Example 1 passed
Passed Example 2 passed
Passed Example 3 inapplicable
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
Passed Example 2 * untested
Passed Example 5 * untested
Failed Example 2 * untested
Failed Example 3 * untested
Failed Example 7 * untested

*: 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 Alfa (fully automated) using the sia-r63 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

HTML page has lang attribute

This rule is implemented by Alfa (fully automated) using the sia-r4 procedure. The implementation is fully consistent with the HTML page has lang attribute WCAG 2 rule. It covers 6 of the 7 examples. On 1 example the implementation cannot tell the outcome. This is often because of technical limitations in tools. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected Reported
  • 3.1.1 Language of Page
  • 3.1.1 Language of Page
Test Results
sia-r4
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 cannot tell

Menuitem has non-empty accessible name

This rule is implemented by Alfa (fully automated) using the sia-r94 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
sia-r94
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

Element in sequential focus order has visible focus

This rule is implemented by Alfa (fully automated) using the sia-r65 procedure. The implementation is partially consistent with the Element in sequential focus order has visible focus WCAG 2 rule. It covers 4 of the 7 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
  • 2.4.7 Focus Visible
  • 2.4.7 Focus Visible
Test Results
sia-r65
Passed Example 1 passed
Passed Example 2 passed
Passed Example 3 cannot tell
Passed Example 4 cannot tell
Failed Example 1 cannot tell
Inapplicable Example 1 inapplicable
Inapplicable Example 2 inapplicable

ARIA attribute is defined in WAI-ARIA

This rule is implemented by Alfa (fully automated) 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
Test Results
sia-r20
Passed Example 1 passed
Passed Example 2 passed
Passed Example 3 passed
Passed Example 4 passed
Failed Example 1 failed
Failed Example 2 failed
Inapplicable Example 1 inapplicable

ARIA required context role

This rule is implemented by Alfa (fully automated) 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 required ID references exist

This rule is implemented by Alfa (fully automated) using the sia-r19 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

ARIA required owned elements

This rule is implemented by Alfa (fully automated) using the sia-r68 procedure. The implementation is partially consistent with the ARIA required owned elements proposed rule. It covers 15 of the 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 state or property is permitted

This rule is implemented by Alfa (fully automated) using the sia-r18 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 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 (fully automated) using the sia-r19 procedure. The implementation is fully consistent with the ARIA state or property has valid value proposed rule. It covers 20 of the 21 examples. On 1 example the implementation cannot tell the outcome. This is often because of technical limitations in tools. The implementation correctly reports 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 transforms

This rule is implemented by Alfa (fully automated) using the sia-r44 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
sia-r44
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 inapplicable
Inapplicable Example 5 inapplicable

Heading has non-empty accessible name

This rule is implemented by Alfa (fully automated) 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
None
  • 1.3.1 Info and Relationships

Iframe elements with identical accessible names have equivalent purpose

This rule is implemented by Alfa (fully automated) 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 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
sia-r15
Passed Example 1 passed
Passed Example 2 passed
Passed Example 3 passed
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 passed
Passed Example 10 passed
Failed Example 1 cannot tell
Failed Example 2 cannot tell
Failed Example 3 cannot tell
Failed Example 4 cannot tell
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
Inapplicable Example 8 inapplicable
Inapplicable Example 9 inapplicable

Iframe element has non-empty accessible name

This rule is implemented by Alfa (fully automated) using the sia-r13 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
sia-r13
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 inapplicable

Links with identical accessible names have equivalent purpose

This rule is implemented by Alfa (fully automated) 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 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
sia-r41
Passed Example 1 passed
Passed Example 2 cannot tell
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 passed
Passed Example 10 passed
Passed Example 11 passed
Passed Example 12 passed
Failed Example 1 cannot tell
Failed Example 2 cannot tell
Failed Example 3 cannot tell
Failed Example 4 cannot tell
Failed Example 5 cannot tell
Failed Example 6 cannot tell
Inapplicable Example 1 inapplicable
Inapplicable Example 2 inapplicable
Inapplicable Example 3 inapplicable

Meta element has no refresh delay (no exception)

This rule is implemented by Alfa (fully automated) using the sia-r96 procedure. The implementation is fully consistent with the Meta element has no refresh delay (no exception) proposed rule. It covers all 13 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected Reported
  • 2.2.4 Interruptions
  • 3.2.5 Change on Request
  • 2.2.4 Interruptions
  • 3.2.5 Change on Request
Test Results
sia-r96
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 inapplicable
Inapplicable Example 4 inapplicable
Inapplicable Example 5 inapplicable
Inapplicable Example 6 inapplicable
Inapplicable Example 7 inapplicable
Inapplicable Example 8 inapplicable

Role attribute has valid value

This rule is implemented by Alfa (fully automated) using the sia-r110 procedure. The implementation is fully consistent with the Role attribute has valid value proposed rule. It covers all 10 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Success Criteria
Expected Reported
None
  • 1.3.1 Info and Relationships
Test Results
sia-r110
Passed Example 1 passed
Passed Example 2 passed
Passed Example 3 passed
Failed Example 1 failed
Failed Example 2 failed
Inapplicable Example 1 inapplicable
Inapplicable Example 2 inapplicable
Inapplicable Example 3 inapplicable
Inapplicable Example 4 inapplicable
Inapplicable Example 5 inapplicable

Element with role attribute has required states and properties

This rule is implemented by Alfa (fully automated) using the sia-r16 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
  • 1.3.1 Info and Relationships
  • 4.1.2 Name, Role, Value

Table header cell has assigned cells

This rule is implemented by Alfa (fully automated) 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
Test Results
sia-r46
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 failed
Failed Example 2 failed
Failed Example 3 inapplicable
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
Back to Top