QualWeb ACT Implementation

Implemented Rules

About QualWeb Results

Results in this page are taken from a public test report published by LASIGE, Faculdade de Ciências da Universidade de Lisboa. Data is published using the EARL+JSON-LD data format.

Implementation Details

Button has non-empty accessible name

This rule is implemented by QualWeb using the Button has accessible name 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 with lang attribute has valid language tag

This rule is implemented by QualWeb using the Element within body has valid lang attribute 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.

Element marked as decorative is not exposed

This rule is implemented by QualWeb using the Element marked as decorative is not exposed 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 QualWeb using the Form control has accessible name 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.

HTML page has lang attribute

This rule is implemented by QualWeb using the HTML has lang attribute procedure. 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.

HTML page lang and xml:lang attributes have matching values

This rule is implemented by QualWeb using the HTML lang and xml:lang match 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 QualWeb using the HTML Page has a 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 QualWeb using the Image button has accessible name 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 QualWeb using the Image has accessible name 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.

Letter spacing in style attributes is not !important

This rule is implemented by QualWeb using the Letter spacing in style attributes is not !important procedure. The implementation is partially consistent with the Letter spacing in style attributes is not !important WCAG 2 rule. It covers all 16 examples. 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 QualWeb using the Link has accessible name 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.

Word spacing in style attributes is not !important

This rule is implemented by QualWeb using the Word spacing in style attributes is not !important procedure. The implementation is partially consistent with the Word spacing in style attributes is not !important WCAG 2 rule. It covers all 16 examples. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

aria-* attribute is defined in WAI-ARIA

This rule is implemented by QualWeb using the aria-* attribute is defined in WAI-ARIA 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.

ARIA required context role

This rule is implemented by QualWeb using the ARIA required context role 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 state or property is permitted

This rule is implemented by QualWeb using the ARIA state or property is permitted 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 no success criteria are failed by this rule. See understanding ACT consistency.

ARIA state or property has valid value

This rule is implemented by QualWeb using the ARIA state or property has valid value procedure. The implementation is fully consistent with the ARIA state or property has valid value proposed rule. It covers all 24 examples. The implementation correctly reports no success criteria are failed by this rule. See understanding ACT consistency.

audio element content has text alternative

This rule is implemented by QualWeb using the audio element content has transcript, audio element content is media alternative for text, and Audio element content has text alternative procedures. Failed examples should be failed by at least one of these procedures. The implementation is partially consistent with the audio element content has text alternative proposed rule. It covers 5 of the 8 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.

Block of repeated content is collapsible

This rule is implemented by QualWeb using the Block of repeated content is collapsible 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 correctly reports no success criteria are failed by this rule. See understanding ACT consistency.

Bypass Blocks of Repeated Content

This rule is implemented by QualWeb using the Document has a landmark with non-repeated content, Document has heading for non-repeated content, Block of repeated content is collapsible, Document has an instrument to move focus to non-repeated content, and Bypass Blocks of Repeated Content procedures. Failed examples should be failed by at least one of these procedures. The implementation is partially consistent with the Bypass Blocks of Repeated Content proposed rule. It covers 1 of the 14 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.

Orientation of the page is not restricted using CSS transform property

This rule is implemented by QualWeb using the Orientation of the page is not restricted using CSS transform property 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.

Document has heading for non-repeated content

This rule is implemented by QualWeb using the Document has heading for non-repeated content procedure. The implementation is partially consistent with the Document has heading for non-repeated content proposed rule. It covers 2 of the 14 examples. On 12 examples 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.

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

This rule is implemented by QualWeb using the Document has an instrument to move focus to non-repeated content procedure. The implementation is partially consistent with the Document has an instrument to move focus to non-repeated content proposed rule. It covers 1 of the 12 examples. On 11 examples 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.

Document has a landmark with non-repeated content

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

svg element with explicit role has non-empty accessible name

This rule is implemented by QualWeb using the svg element with explicit role has accessible name 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.

Heading has non-empty accessible name

This rule is implemented by QualWeb using the Heading has accessible name procedure. The implementation is fully consistent with the Heading has non-empty 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.

id attribute value is unique

This rule is implemented by QualWeb using the `id` attribute value is unique 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 QualWeb using the `iframe` elements with identical accessible names have equivalent purpose procedure. The implementation is partially consistent with the iframe elements with identical accessible names have equivalent purpose proposed rule. It covers 9 of the 23 examples. On 14 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.

iframe element has non-empty accessible name

This rule is implemented by QualWeb using the iframe element has accessible name 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 negative tabindex has no interactive elements

This rule is implemented by QualWeb using the iframe with negative tabindex has no interactive elements procedure. The implementation is partially consistent with the iframe with negative tabindex has no interactive elements proposed rule. It covers all 6 examples. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

Error message describes invalid form field value

This rule is implemented by QualWeb using the Error message describes invalid form field value procedure. The implementation is partially consistent with the Error message describes invalid form field value proposed rule. It covers 1 of the 9 examples. On 8 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.

Links with identical accessible names have equivalent purpose

This rule is implemented by QualWeb using the Links with identical accessible names have equivalent purpose 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.

Menuitem has non-empty accessible name

This rule is implemented by QualWeb using the Menuitem has non-empty accessible name procedure. The implementation is partially consistent with the Menuitem has non-empty accessible name proposed rule. It covers all 8 examples. The implementation reports different success criteria as failed from what is expected by this rule. See understanding ACT consistency.

meta element has no refresh delay

This rule is implemented by QualWeb using the Meta-refresh no delay 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.

meta element has no refresh delay (no exception)

This rule is implemented by QualWeb using the `meta` element has no refresh delay (no exception) 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.

meta viewport allows for zoom

This rule is implemented by QualWeb using the meta viewport does not prevent zoom procedure. The implementation is fully consistent with the meta viewport allows for zoom proposed 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 QualWeb using the Object element has non-empty accessible name 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.

Element with presentational children has no focusable content

This rule is implemented by QualWeb using the Element with presentational children has no focusable content procedure. The implementation is fully consistent with the Element with presentational children has no focusable content proposed rule. It covers all 7 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 QualWeb using the role attribute has valid value 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 QualWeb using the Element with role attribute has required states and properties procedure. The implementation is fully consistent with the Element with role attribute has required states and properties proposed rule. It covers all 8 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 QualWeb using the Scrollable element is keyboard accessible 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 QualWeb using the Element in sequential focus order has visible focus procedure. The implementation is partially consistent with the Element in sequential focus order has visible focus proposed rule. It covers 4 of the 9 examples. On 5 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.

Table header cell has assigned cells

This rule is implemented by QualWeb using the All table header cells have assigned data cells procedure. The implementation is fully consistent with the Table header cell has assigned cells proposed rule. It covers all 16 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 QualWeb using the Headers attribute specified on a cell refers to cells in the same table element 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.

Text has minimum contrast

This rule is implemented by QualWeb using the Text has minimum contrast procedure. The implementation is fully consistent with the Text has minimum contrast proposed rule. It covers 25 of the 28 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.

Text has enhanced contrast

This rule is implemented by QualWeb using the Text has enhanced contrast procedure. The implementation is fully consistent with the Text has enhanced contrast proposed rule. It covers 27 of the 29 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.

video element visual-only content has accessible alternative

This rule is implemented by QualWeb using the video element visual-only content has description track procedure. The implementation is partially consistent with the video element visual-only content has accessible alternative proposed rule. It covers 5 of the 9 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.

Audio and visuals of video element have transcript

This rule is implemented by QualWeb using the Audio and visuals of video element have transcript procedure. The implementation is partially consistent with the Audio and visuals of video element have transcript proposed rule. It covers 1 of the 5 examples. On 4 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.

Visible label is part of accessible name

This rule is implemented by QualWeb using the Visible label is part of accessible name procedure. The implementation is fully consistent with the Visible label is part of accessible name proposed rule. It covers all 13 examples. The implementation correctly reports which success criteria are failed by this rule. See understanding ACT consistency.

Zoomed text node is not clipped with CSS overflow

This rule is implemented by QualWeb using the Zoomed text node is not clipped with CSS overflow procedure. The implementation is partially consistent with the Zoomed text node is not clipped with CSS overflow proposed rule. It covers 5 of the 12 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.