Equal Access Accessibility Checker ACT Implementation

Implemented Rules

About Equal Access Accessibility Checker Results

ACT rule results were generated using the latest `accessibility-checker` from NPM using the [ACT test driver](https://github.com/IBMa/equal-access/tree/master/accessibility-checker/test-act). Results were created using the `preview` archive and the `IBM_Accessibility` policy. Mappings from ACT Rules to Accessibility Checker rule ids and reason codes can be found in [`act_aligned.json`](https://github.com/IBMa/equal-access/blob/master/accessibility-checker/test-act/act_aligned.json) and [`ace_mapping.js`](https://github.com/IBMa/equal-access/blob/master/accessibility-checker/test-act/ace_mapping.js). Results indicate the rule ids and reason codes related to the ACT rule are generated in the following format: `RuleId1:ReasonCode1,ReasonCode2|RuleId2:ReasonCode3,ReasonCode4`.

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

Implementation Details

Button has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Input_ExplicitLabel:Pass_0,Fail_1,Fail_2 procedure. The implementation is partially consistent with the Button has non-empty accessible name WCAG 2 rule. It covers 12 of the 17 examples. For 5 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Form field has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Input_ExplicitLabel:Pass_0,Fail_1,Fail_2 procedure. The implementation is partially consistent with the Form field has non-empty accessible name WCAG 2 rule. It covers 14 of the 17 examples. For 3 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

HTML page has lang attribute

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Html_HasLang:Pass_0,Fail_3, and WCAG20_Elem_Lang_Valid:Pass_0,Fail_1 procedures. Failed examples should be failed by at least one of these procedures. The implementation is partially consistent with the HTML page has lang attribute WCAG 2 rule. It covers 4 of the 7 examples. For 3 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

HTML page lang attribute has valid language tag

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Elem_Lang_Valid:Pass_0,Fail_1,Fail_2,Fail_3 procedure. The implementation is partially consistent with the HTML page lang attribute has valid language tag WCAG 2 rule. It covers 6 of the 7 examples. For 1 example no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

HTML page lang and xml:lang attributes have matching values

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Html_HasLang:Pass_0,Fail_4,Fail_5 procedure. The implementation is partially consistent with the HTML page lang and xml:lang attributes have matching values WCAG 2 rule. It covers 8 of the 12 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.

HTML page has non-empty title

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Doc_HasTitle:Pass_0,Fail_1,Fail_2,Fail_3 procedure. The implementation is partially consistent with the HTML page has non-empty title WCAG 2 rule. It covers 10 of the 11 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.

Image button has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Input_ExplicitLabelImage:Pass_0,Pass_1,Pass_2,Fail, and Rpt_Aria_ValidIdRef:Pass_0,Fail_1 procedures. Failed examples should be failed by at least one of these procedures. The implementation is partially consistent with the Image button has non-empty accessible name WCAG 2 rule. It covers 2 of the 12 examples. For 10 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.

Image has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Img_HasAlt:Pass_0,Fail_1,Fail_2,Fail_3, and HAAC_Aria_ImgAlt:Pass_0,Fail_1,Fail_2,Fail_3 procedures. Failed examples should be failed by at least one of these procedures. The implementation is partially consistent with the Image has non-empty accessible name WCAG 2 rule. It covers 1 of the 18 examples. For 17 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Link has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_A_HasText:Pass_0,Fail_1 procedure. The implementation is partially consistent with the Link has non-empty accessible name WCAG 2 rule. It covers 20 of the 28 examples. For 8 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

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

ARIA attribute is defined in WAI-ARIA

This rule is implemented by Equal Access Accessibility Checker using the Rpt_Aria_ValidProperty:Pass_0,Fail_1 procedure. The implementation is partially consistent with the ARIA attribute is defined in WAI-ARIA proposed rule. It covers 6 of the 7 examples. For 1 example no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

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

This rule is implemented by Equal Access Accessibility Checker using the aria_hidden_focus_misuse:Pass_0,Fail_1 procedure. The implementation is partially consistent with the Element with aria-hidden has no content in sequential focus navigation proposed rule. It covers 9 of the 14 examples. For 5 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

ARIA required context role

This rule is implemented by Equal Access Accessibility Checker using the Rpt_Aria_RequiredParent_Native_Host_Sematics:Pass_0,Fail_1 procedure. The implementation is partially consistent with the ARIA required context role proposed rule. It covers 10 of the 15 examples. For 4 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

ARIA state or property is permitted

This rule is implemented by Equal Access Accessibility Checker using the aria_semantics_attribute:Pass_0,Fail_1 procedure. The implementation is partially consistent with the ARIA state or property is permitted 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 reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

ARIA state or property has valid value

This rule is implemented by Equal Access Accessibility Checker using the Rpt_Aria_ValidPropertyValue:Pass_0,Fail_1 procedure. The implementation is partially consistent with the ARIA state or property has valid value proposed rule. It covers 17 of the 24 examples. For 5 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

SVG element with explicit role has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the HAAC_Aria_ImgAlt:Pass_0,Fail_2, and HAAC_Aria_SvgAlt:Pass_0,Fail_2 procedures. Failed examples should be failed by at least one of these procedures. The implementation is partially consistent with the SVG element with explicit role has non-empty accessible name proposed rule. It covers 0 of the 10 examples. For 10 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Id attribute value is unique

This rule is implemented by Equal Access Accessibility Checker using the RPT_Elem_UniqueId:Pass_0,Fail_1,Fail_2 procedure. The implementation is partially consistent with the Id attribute value is unique proposed rule. It covers 8 of the 10 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.

Iframe element has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Frame_HasTitle:Pass_0,Fail_1 procedure. The implementation is partially consistent with the Iframe element has non-empty accessible name proposed rule. It covers 6 of the 10 examples. For 4 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Menuitem has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the Rpt_Aria_WidgetLabels_Implicit:Pass_0,Fail_1 procedure. The implementation is partially consistent with the Menuitem has non-empty accessible name proposed rule. It covers 6 of the 8 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.

Meta viewport allows for zoom

This rule is implemented by Equal Access Accessibility Checker using the meta_viewport_zoom:Pass_0,Potential_1 procedure. The implementation is partially consistent with the Meta viewport allows for zoom proposed rule. It covers 6 of the 11 examples. For 5 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

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

This rule is implemented by Equal Access Accessibility Checker using the WCAG20_Object_HasText:Pass_0,Fail_1 procedure. The implementation is partially consistent with the Object element rendering non-text content has non-empty accessible name proposed rule. It covers 8 of the 14 examples. For 6 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.

Role attribute has valid value

This rule is implemented by Equal Access Accessibility Checker using the Rpt_Aria_ValidRole:Pass_0,Fail_2,Potential_1 procedure. The implementation is partially consistent with the Role attribute has valid value proposed rule. It covers 4 of the 10 examples. On 1 example the implementation cannot tell the outcome. This is often because of technical limitations in tools. For 5 examples no results were reported. This can happen when examples are newer then the test results. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Element with role attribute has required states and properties

This rule is implemented by Equal Access Accessibility Checker using the combobox_popup_reference:Pass_expanded,Pass_collapsed,Fail_1.2_missing_controls,Fail_1.2_popup_reference_missing procedure. The implementation is partially consistent with the Element with role attribute has required states and properties proposed rule. It covers 2 of the 8 examples. For 6 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.

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

This rule is implemented by Equal Access Accessibility Checker using the table_headers_ref_valid:Pass_0,Fail_1,Fail_2,Fail_3,Fail_4 procedure. The implementation is partially consistent with the Headers attribute specified on a cell refers to cells in the same table element proposed rule. It covers 12 of the 17 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.