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. 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 the act property of rule definitions. 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

Role attribute has valid value

This rule is implemented by Equal Access Accessibility Checker using the aria_role_allowed:Pass_0,Fail_2,Potential_1 procedure. The implementation is fully consistent with the Role attribute has valid value WCAG 2 rule. It covers 9 of the 10 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.

ARIA state or property has valid value

This rule is implemented by Equal Access Accessibility Checker using the aria_attribute_value_valid:Pass_0,Fail_1 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 which success criteria are failed by this rule. See understanding ACT consistency.

ARIA attribute is defined in WAI-ARIA

This rule is implemented by Equal Access Accessibility Checker using the aria_attribute_allowed:Pass_0,Fail_1 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 which success criteria are failed by this rule. See understanding ACT consistency.

Element with lang attribute has valid language tag

This rule is implemented by Equal Access Accessibility Checker using the element_lang_valid:Pass_0,Fail_1,Fail_2 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.

Menuitem has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the aria_widget_labelled:Pass_0,Fail_1 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.

Important letter spacing in style attributes is wide enough

This rule is implemented by Equal Access Accessibility Checker using the text_spacing_valid:pass,fail_letter_spacing_style,fail_word_spacing_style,fail_line_height_style 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.

Important word spacing in style attributes is wide enough

This rule is implemented by Equal Access Accessibility Checker using the text_spacing_valid:pass,fail_letter_spacing_style,fail_word_spacing_style,fail_line_height_style 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.

Important line height in style attributes is wide enough

This rule is implemented by Equal Access Accessibility Checker using the text_spacing_valid:pass,fail_letter_spacing_style,fail_word_spacing_style,fail_line_height_style 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.

Button has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the input_label_exists:Pass_0,Fail_1,Fail_2 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.

Element marked as decorative is not exposed

This rule is implemented by Equal Access Accessibility Checker using the aria_attribute_valid:Pass,Fail_invalid_role_attr,Fail_invalid_implicit_role_attr, and img_alt_null:potential_aria_override procedures. Failed examples should be failed by at least one of these procedures. The implementation is partially consistent with the Element marked as decorative is not exposed WCAG 2 rule. It covers all 10 examples. 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 input_label_exists:Pass_0,Fail_1,Fail_2 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.

*: 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 Equal Access Accessibility Checker using the html_lang_valid:Pass_0,Fail_1,Fail_2,Fail_3 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.

HTML page has non-empty title

This rule is implemented by Equal Access Accessibility Checker using the page_title_exists:Pass_0,Fail_1,Fail_2,Fail_3 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.

*: 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 Equal Access Accessibility Checker using the imagebutton_alt_exists:Pass_0,Pass_1,Pass_2,Fail, and aria_id_unique:Pass_0,Fail_1 procedures. Failed examples should be failed by at least one of these procedures. 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.

Image has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the img_alt_valid:pass,fail_blank_alt,fail_no_alt,fail_blank_title procedure. The implementation is partially consistent with the Image has non-empty accessible name WCAG 2 rule. It covers 16 of the 18 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Link has non-empty accessible name

This rule is implemented by Equal Access Accessibility Checker using the a_text_purpose:pass,fail_acc_name 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.

Element with presentational children has no focusable content

This rule is implemented by Equal Access Accessibility Checker using the aria_descendant_valid:pass,potential_child_implicit_role,fail_child_explicit_role procedure. The implementation is fully consistent with the Element with presentational children has no focusable content WCAG 2 rule. It covers 5 of the 7 examples. On 2 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.

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 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.

*: 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 Equal Access Accessibility Checker using the meta_redirect_optional:pass,fail,fail_longrefresh, and meta_refresh_delay:Pass_0,Potential_1 procedures. Failed examples should be failed by at least one of these procedures. The implementation is fully consistent with the Meta element has no refresh delay WCAG 2 rule. It covers 14 of the 15 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.

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

This rule is implemented by Equal Access Accessibility Checker using the object_text_exists:pass,fail_no_text_alternative 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.

HTML page has lang attribute

This rule is implemented by Equal Access Accessibility Checker using the html_lang_exists:Pass_0,Fail_3, and html_lang_valid:Pass_0,Fail_1 procedures. Failed examples should be failed by at least one of these procedures. 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.

Scrollable content can be reached with sequential focus navigation

This rule is implemented by Equal Access Accessibility Checker using the element_scrollable_tabbable:pass_tabbable,pass_interactive,fail_scrollable procedure. The implementation is partially consistent with the Scrollable content can be reached with sequential focus navigation WCAG 2 rule. It covers all 10 examples. 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.

Text has minimum contrast

This rule is implemented by Equal Access Accessibility Checker using the text_contrast_sufficient:pass,fail_contrast,potential_same_color,potential_graphic_background,potential_text_shadow procedure. The implementation is fully consistent with the Text has minimum contrast WCAG 2 rule. It covers 26 of the 32 examples. On 6 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.

*: 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 (no exception)

This rule is implemented by Equal Access Accessibility Checker using the meta_refresh_delay:Pass_0,Potential_1 procedure. The implementation is partially consistent with the Meta element has no refresh delay (no exception) WCAG 2 rule. It covers 10 of the 13 examples. On 1 example 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.

ARIA required context role

This rule is implemented by Equal Access Accessibility Checker using the aria_parent_required:Pass_0,Fail_1 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.

ARIA required owned elements

This rule is implemented by Equal Access Accessibility Checker using the aria_child_valid:Pass,Fail_no_child,Fail_invalid_child 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.

ARIA state or property is permitted

This rule is implemented by Equal Access Accessibility Checker using the aria_attribute_valid:Pass,Fail_invalid_role_attr,Fail_invalid_implicit_role_attr 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.

Orientation of the page is not restricted using CSS transforms

This rule is implemented by Equal Access Accessibility Checker using the element_orientation_unlocked:pass,fail_locked procedure. The implementation is partially consistent with the Orientation of the page is not restricted using CSS transforms proposed rule. It covers 11 of the 12 examples. The implementation correctly reports which success criteria are failed 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 aria_attribute_required:pass,fail_missing, and combobox_popup_reference:Pass_1.0_expanded,Pass_1.0_collapsed,Pass_1.2_expanded,Pass_1.2_collapsed,Fail_1.2_missing_controls,Fail_1.2_popup_reference_missing procedures. Failed examples should be failed by at least one of these procedures. 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.

Visible label is part of accessible name

This rule is implemented by Equal Access Accessibility Checker using the label_name_visible:Pass_0,Fail_1 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.