Axe DevTools Pro ACT Implementation

Implemented Rules

About Axe DevTools Pro Results

Axe DevTools Pro combines the automated results of axe-core, and results from axe Intelligent Guided Test (IGT) tools. Tools can produced multiple issue types. The ID of each issue type is given as the name of the procedure, with the tool that returns it in brackets. For example alt-text-not-meaningful (Images) is the alt-text-not-meaningful issue type reported by the Images tool.

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

Implementation Details

autocomplete attribute has valid value

This rule is implemented by Axe DevTools Pro using the autocomplete-valid procedure. The implementation is fully consistent with the autocomplete attribute has valid value WCAG 2 rule. It covers all 23 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.

Button has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the button-name, and aria-command-name procedures. Failed examples should be failed by at least one of these procedures. 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 with lang attribute has valid language tag

This rule is implemented by Axe DevTools Pro using the valid-lang 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.

*: 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 Axe DevTools Pro using the presentation-role-conflict 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.

Form field has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the aria-input-field-name, label, and select-name procedures. Failed examples should be failed by at least one of these procedures. 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 has lang attribute

This rule is implemented by Axe DevTools Pro using the html-has-lang procedure. The implementation is fully consistent with the HTML page has lang attribute WCAG 2 rule. It covers all 14 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 Axe DevTools Pro using the html-lang-valid 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 lang and xml:lang attributes have matching values

This rule is implemented by Axe DevTools Pro using the html-xml-lang-mismatch 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.

HTML page has non-empty title

This rule is implemented by Axe DevTools Pro using the document-title 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.

Image button has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the input-image-alt 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.

Image has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the image-alt, and role-img-alt procedures. Failed examples should be failed by at least one of these procedures. 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.

Letter spacing in style attributes is not !important

This rule is implemented by Axe DevTools Pro using the avoid-inline-spacing 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.

Link has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the link-name, and area-alt procedures. Failed examples should be failed by at least one of these procedures. 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.

Word spacing in style attributes is not !important

This rule is implemented by Axe DevTools Pro using the avoid-inline-spacing 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.

SVG element with explicit role has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the svg-img-alt 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.

Element with presentational children has no focusable content

This rule is implemented by Axe DevTools Pro using the nested-interactive 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.

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

This rule is implemented by Axe DevTools Pro using the td-headers-attr 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.

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

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

This rule is implemented by Axe DevTools Pro using the aria-hidden-focus procedure. The implementation is fully consistent with the Element with aria-hidden has no content in sequential focus navigation WCAG 2 rule. It covers 13 of the 15 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.

Line height in style attributes is not !important

This rule is implemented by Axe DevTools Pro using the avoid-inline-spacing procedure. The implementation is fully consistent with the Line height in style attributes is not !important WCAG 2 rule. It covers all 21 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Meta element has no refresh delay

This rule is implemented by Axe DevTools Pro using the meta-refresh 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.

Meta viewport allows for zoom

This rule is implemented by Axe DevTools Pro using the meta-viewport procedure. The implementation is fully consistent with the Meta viewport allows for zoom WCAG 2 rule. It covers all 11 examples. 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 Axe DevTools Pro using the object-alt 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.

ARIA attribute is defined in WAI-ARIA

This rule is implemented by Axe DevTools Pro using the aria-valid-attr 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 which success criteria are failed by this rule. See understanding ACT consistency.

ARIA required context role

This rule is implemented by Axe DevTools Pro using the aria-required-children, and aria-required-parent procedures. Failed examples should be failed by at least one of these procedures. 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 Axe DevTools Pro using the aria-required-children 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 Axe DevTools Pro using the aria-allowed-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 which success criteria are failed by this rule. See understanding ACT consistency.

ARIA state or property has valid value

This rule is implemented by Axe DevTools Pro using the aria-valid-attr-value procedure. The implementation is partially consistent with the ARIA state or property has valid value proposed rule. It covers 22 of the 24 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.

Block of repeated content is collapsible

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Block of repeated content is collapsible proposed rule. It covers 1 of the 8 examples. On 7 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.

Bypass Blocks of Repeated Content

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Bypass Blocks of Repeated Content proposed rule. It covers 9 of the 14 examples. On 5 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.

Orientation of the page is not restricted using CSS transforms

This rule is implemented by Axe DevTools Pro using the css-orientation-lock procedure. The implementation is partially consistent with the Orientation of the page is not restricted using CSS transforms proposed rule. It covers 10 of the 12 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.

Document has heading for non-repeated content

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Document has heading for non-repeated content proposed rule. It covers 10 of the 14 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.

Document has an instrument to move focus to non-repeated content

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Document has an instrument to move focus to non-repeated content proposed rule. It covers 8 of the 12 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.

Document has a landmark with non-repeated content

This rule is implemented by Axe DevTools Pro using the bypass procedure. The implementation is partially consistent with the Document has a landmark with non-repeated content proposed rule. It covers 5 of the 8 examples. On 3 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.

Form field label is descriptive

This rule is implemented by Axe DevTools Pro using the label-visible-not-descriptive (forms) procedure. The implementation is fully consistent with the Form field label is descriptive proposed rule. It covers all 14 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Heading has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the empty-heading 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.

HTML page title is descriptive

This rule is implemented by Axe DevTools Pro using the title-not-meaningful (structure) procedure. The implementation is fully consistent with the HTML page title is descriptive proposed 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.

Id attribute value is unique

This rule is implemented by Axe DevTools Pro using the duplicate-id-aria 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.

Iframe elements with identical accessible names have equivalent purpose

This rule is implemented by Axe DevTools Pro using the frame-title-unique procedure. The implementation is partially consistent with the Iframe elements with identical accessible names have equivalent purpose proposed rule. It covers 11 of the 23 examples. On 10 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.

Iframe element has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the frame-title procedure. The implementation is fully consistent with the Iframe element 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.

Iframe with interactive elements is not excluded from tab-order

This rule is implemented by Axe DevTools Pro using the frame-focusable-content procedure. The implementation is fully consistent with the Iframe with interactive elements is not excluded from tab-order proposed rule. It covers all 7 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Image accessible name is descriptive

This rule is implemented by Axe DevTools Pro using the alt-text-short-text-not-meaningful (Images) procedure. The implementation is fully consistent with the Image accessible name is descriptive proposed rule. It covers all 16 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Image not in the accessibility tree is decorative

This rule is implemented by Axe DevTools Pro using the alt-text-missing + semantic-hidden (images) procedure. The implementation is partially consistent with the Image not in the accessibility tree is decorative proposed rule. It covers 17 of the 20 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Error message describes invalid form field value

This rule is implemented by Axe DevTools Pro using the form-error-required-unclear + instructions-not-included (forms) procedure. The implementation is partially consistent with the Error message describes invalid form field value proposed rule. It covers 8 of the 9 examples. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Links with identical accessible names have equivalent purpose

This rule is implemented by Axe DevTools Pro using the identical-links-same-purpose procedure. The implementation is partially consistent with the Links with identical accessible names have equivalent purpose proposed rule. It covers 10 of the 21 examples. On 11 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.

Menuitem has non-empty accessible name

This rule is implemented by Axe DevTools Pro using the button-name 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.

Meta element has no refresh delay (no exception)

This rule is implemented by Axe DevTools Pro using the meta-refresh-no-exceptions, and meta-refresh 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 (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.

Role attribute has valid value

This rule is implemented by Axe DevTools Pro using the aria-roles 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.

Element with role attribute has required states and properties

This rule is implemented by Axe DevTools Pro using the aria-required-attr 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.

Scrollable element is keyboard accessible

This rule is implemented by Axe DevTools Pro using the scrollable-region-focusable 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.

Element in sequential focus order has visible focus

This rule is implemented by Axe DevTools Pro using the focus-indicator-missing (keyboard) procedure. The implementation is fully consistent with the Element in sequential focus order has visible focus proposed rule. It covers all 7 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Table header cell has assigned cells

This rule is implemented by Axe DevTools Pro using the th-has-data-cells procedure. The implementation is partially consistent with the Table header cell has assigned cells proposed rule. It covers 13 of the 16 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.

Text has minimum contrast

This rule is implemented by Axe DevTools Pro using the color-contrast procedure. The implementation is fully consistent with the Text has minimum contrast proposed rule. It covers 25 of the 32 examples. On 7 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.

Text has enhanced contrast

This rule is implemented by Axe DevTools Pro using the color-contrast-enhanced, and color-contrast procedures. Failed examples should be failed by at least one of these procedures. The implementation is fully consistent with the Text has enhanced contrast proposed rule. It covers 27 of the 34 examples. On 7 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.

Visible label is part of accessible name

This rule is implemented by Axe DevTools Pro using the label-content-name-mismatch procedure. The implementation is fully consistent with the Visible label is part of accessible name proposed rule. It covers 12 of the 13 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.