Skip to main content
All CollectionsFAQAccessibility
Accessibility Checks Update
Accessibility Checks Update

This article gives the details about the new and replaced accessibility checks

Updated over a week ago

Article Navigation


Introduction

The initiative for the update of the accessibility rules that we check for and to improve the guidance we provide consists of 3 practical improvement areas:

  1. We reduced the number of review checks and eliminated outdated checks.

    • Smaller number of checks so that you can handle them more effectively.

    • Clarification of complex checks.

    • Easier review process.

  2. We added 59 new checks that are either completely new or improved versions of old checks. This enables our scan to test for them more accurately. This project includes a change to our testing approach that aims for higher accuracy and a decreased amount of false positives, and improves our existing checks. Whenever possible, we introduced new checks for formerly unsupported WCAG success criteria, which increases our testing coverage. These checks are mainly review checks.

  3. We introduced 25 new Accessibility Conformance Testing (ACT) rules. ACT is the W3C published standard for automated testing. ACT Rules are designed to harmonize how WCAG and other accessibility guidance are tested. This means that we are able to provide more transparent and reliable testing results that are aligned with how other organizations, including digital authorities, monitor compliance.

Affected Success Criteria:

  • SC 1.1.1: Non-text Content

  • SC 1.2.1: Audio-only and Video-only (Prerecorded)

  • SC 1.2.2: Captions (Prerecorded)

  • SC 1.2.3: Audio Description or Media Alternative (Prerecorded)

  • SC 1.2.4: Captions (Live)

  • SC 1.2.6: Sign Language (Prerecorded)

  • SC 1.2.7: Extended Audio Description (Prerecorded)

  • SC 1.2.8: Media Alternative (Prerecorded)

  • SC 1.2.9: Audio-only (Live)

  • SC 1.3.1: Info and Relationships

  • SC 1.3.2: Meaningful Sequence

  • SC 1.4.1: Use of Color

  • SC 1.4.3: Contrast (Minimum)

  • SC 1.4.6: Contrast (Enhanced)

  • SC 2.1.1: Keyboard

  • SC 2.1.2: No Keyboard Trap

  • SC 2.1.3: Keyboard (No Exception)

  • SC 2.2.1: Timing Adjustable

  • SC 2.4.2: Page Titled

  • SC 2.4.6: Headings and Labels

  • SC 2.4.7: Focus Visible

  • SC 3.3.2: Labels or Instructions

  • SC 4.1.2: Name, Role, Value.

How this Affects your Score

As a part of the update, your accessibility scores may change. The update is communicated on the progress graphic as a vertical orange line, to indicate that the change in compliance is caused by an update to the rules.

A vertical orange line in the chart timeline that indicates when the new accessibility checks came into affect.

For more information, see the user guide article:


New Checks

New checks related to 1.1.1 Non text content (A)

  1. SVG element with explicit role has non-empty accessible name (error)

    • This rule is an ACT rule.

    • This rule checks that each SVG image element that is explicitly included in the accessibility tree has a non-empty accessible name.

  2. Image has non-empty accessible name (Error)

    • This rule is an ACT rule.

    • This rule checks that each image either has a non-empty accessible name or is marked up as decorative.

    • This rule replaces old checks 1, 6, 7, 16 (see list of deprecated checks below.)

  3. <code>object</code> element rendering non-text content has non-empty accessible name (Error)

    • This rule is an ACT rule.

    • This rule checks that each object element rendering non-text content has a non-empty accessible name.

    • This rule replaces old check number 80 (see list of deprecated checks below.)

  4. Image not in the accessibility tree is decorative (Warning)

    • This rule is an ACT rule.

    • This rule checks that visible img svg and canvas elements that are ignored by assistive technologies are decorative.

    • This rule replaces old check number 239 (see list of deprecated checks below)

  5. Image not in the accessibility tree is decorative (Error)

    • This rule is an ACT rule.

    • This rule checks that visible img svg and canvas elements that are ignored by assistive technologies are decorative.

    • This rule replacers old checks 3, 8, 23, 178, 357 (see list of deprecated checks below.)

  6. Image button has non-empty accessible name (Error)

    • This rule is an ACT rule.

    • This rule checks that each image button element has a non-empty accessible name.

    • This rule is an updated version of old check number 238 (see list of deprecated checks below.)

New checks related to 1.2.1 Audio-only and Video-only (Prerecorded) (A)

  1. Video element visual-only content has accessible alternative. (Warning)

    • This rule checks that video elements without audio have an alternative available.

  2. Audio element content has text alternative. (Warning)

    • This rule checks that audio elements have a text alternative available.

New checks related to 1.2.2 Captions (Prerecorded) (A)

  1. Video element auditory content has accessible alternative. (Warning)

    • This rule checks that video elements have an alternative for information conveyed through audio.

New checks related to 1.2.3 Audio Description or Media Alternative (Prerecorded) (A)

  1. <code>object</code> link to multimedia file require equivalent alternatives (e.g. captions or auditory descriptions of the visual track). (Review)

    • This rule checks if <code>object</code> element contains a <code>type</code> attribute value of a "video" and asks you to review if alternative is correctly provided.

    • This check replaces old check 146 (see list of deprecated checks below.)

  2. Video element visual content has accessible alternative. (Warning)

    • This rule checks that video elements with audio have an alternative for the video content as audio or as text.

New checks related to 1.2.4 Captions (Live) (AA)

  1. Captions (Live) (Warning)

    • This rule asks user to review if live video has captions.

New checks related to 1.2.6 Sign Language (Prerecorded) (AAA)

  1. Sign Language (Prerecorded) (Warning)

    • This rule asks user to review if sign language interpretation is provided for all prerecorded audio content in synchronized media.

New checks related to 1.2.7 Extended Audio Description (Prerecorded) (AAA)

  1. Extended Audio Description (Warning)

    • This rule requires users to evaluate situations where pauses in the foreground audio are too brief to allow audio descriptions to effectively convey the video's meaning. In such cases, extended audio descriptions must be provided for all prerecorded video content in synchronized media.

New checks related to 1.2.8 Media Alternative (Prerecorded) (AAA)

  1. Media Alternative (Prerecorded) (Warning)

    • This rule requires users to evaluate if alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media.

New checks related to 1.2.9 Audio Only (Live) (AAA)

  1. Audio Only (Live) (Warning)

    • This check requires users to evaluate if live audio has a media alternative.

New checks related to 1.3.1 Info and Relationships (A)

  1. ARIA attribute is defined in WAI-ARIA (Error)

    • This rule checks that each aria- attribute specified is defined in ARIA 1.2.

  2. ARIA state or property has valid value (Error)

    • This rule checks that each ARIA state or property has a valid value type.

  3. ARIA required context role (Error)

    • This rule checks that an element with an explicit semantic role exists inside its required context.

  4. ARIA required ID references exist (Error)

    • This rule checks that every ID reference required by WAI-ARIA exists

  5. Use a quote element to mark up quotations. (Warning)

    • This check requires user to review that the quotations in your text are within relevant quote elements to ensure that users of assistive technology can easily identify quotations.

  6. Non-decorative content in pseudo classes (Error)

    • The rule checks if “::before” and “::after” pseudo classes contains non-decorative content.

  7. Headers attribute specified on a cell refers to cells in the same table element (Error)

    • This rule checks that all headers attributes in cells of a given table refers to ids of cells within that same table.

  8. Aria required owned elements (Error)

    • This rule checks that an element with an explicit semantic role has at least one of its required owned elements.

  9. Table header cell has assigned cells (Error)

    • This rule checks that each table header has assigned cells in a table element.

  10. Element needs to have the right semantic role (Warning)

    • This rule requires user to check that the rlements you can click touch or navigate have the right semantic role.

  11. Heading has non-empty accessible name (Error)

    • This rule checks that each heading element in the document has an accessible name which is not empty.

New checks related to 1.3.2 Meaningful Sequence (A)

  1. HTML layout tables should make sense when linearized (Warning)

    • This rule requires user to investigate that content in layout tables makes sense when linearized.

  2. Using white space characters to control spacing within a word (Error)

    • This rule checks that white space characters such as space tab line break or carriage return are not used to format individual words visually.

  3. Using white space characters to create multiple columns or to format tables in plain text content (Error)

    • This rule checks that white space characters such as space tab line break or carriage return are not used to create columns or format tables in plain text.

  4. Changing the meaning of content by positioning information with CSS. (Review)

    • This rule requires users to verify that CSS, rather than structural markup, is used to alter the visual layout of the content, and that these layout changes do not affect the content's meaning.

New checks related to 1.4.1 Use of color (A)

  1. Use of Color (Review)

    • This check requires user to review that Color is not used as the only visual means of conveying information indicating an action prompting a response or distinguishing a visual element.

    • This check replaces following checks 14, 21, 55, 73, 86, 221-224, 252 (See list of deprecated checks below.)

  2. Links inside text are sufficiently distinguishable (Error)

    • This rule looks for links that have adjacent text and compares it to various criteria to determine if is sufficiently distinguishable from the text.

    • This check replaces check 404 (See list of deprecated checks below.)

New checks related to 1.4.3 Contrast (Minimum) (AA)

  1. Text has minimum contrast (Error)

    • This rule checks that the highest possible contrast of every text character with its background meets the minimal contrast requirement.

    • This rule replaces check 353 (See list of deprecated checks below.)

New checks related to 1.4.6 Contrast (Enhanced) (AAA)

  1. Text has enhanced contrast (Error)

    • This rule checks that the highest possible contrast of every text character with its background meets the enhanced contrast requirement.

    • This rule replaces check 355 (See list of deprecated checks below.)

New checks related to 2.1.1 Keyboard (A)

  1. All functionality of the content is operable through a keyboard interface (Review)

    • This rule requires user to Review that all functionality can be operated by keyboard.

  2. Scrollable content can be reached with sequential focus navigation (Error)

    • This rule is an ACT rule.

    • This rule checks that an element with an explicit semantic role exists inside its required context.

  3. Iframe with interactive elements is not excluded from tab-order (Error)

    • This rule is an ACT rule.

    • This rule checks that iframe elements which contain an interactive (tabbable) element are not excluded from sequential focus navigation.

    • This rule replaces old checks 26, 76, 89, 103-108 (See list of deprecated checks below.)

New checks related to 2.1.2 No Keyboard Trap (A)

  1. Keyboard Trap (Review)

    • Review that the keyboard focus is not trapped by any component on the web page.

    • This rule replaces old check(s) 258, 259, 260 (See list of deprecated checks below.)

New checks related to 2.1.3 Keyboard (No Exception) (AAA)

  1. Scrollable content can be reached with sequential focus navigation (Error)

    • This rule is an ACT rule.

    • This rule checks that scrollable elements or their descendants can be reached with sequential focus navigation so that they can be scrolled by keyboard.

New checks related to 2.2.1 Timing adjustable (A)

  1. Meta element has no refresh delay (Error)

    • This rule is an ACT rule.

    • This rule checks that the first valid meta refresh element on the page is either an instant redirect or has a very long delay (20 hours.)

New checks related to 2.4.2 Page Titled (A)

  1. HTML page has non-empty title (Error)

    • This rule is an ACT rule.

    • This rule checks that a non-embedded HTML page has a non-empty title.

    • This check replaces checks 50-54 (See list of deprecated checks below.)

  2. HTML page title is descriptive (Review)

    • This rule is an ACT rule.

    • This rule checks that the first title in an HTML web page describes the topic or purpose of that page.

New checks related to 2.4.3 Focus order (A)

  1. The tab order specified by <code>tabindex</code> attributes follows a logical order (Review)

    • This review check requires users to validate that there is a logical tab order when the default tab order does not suffice.

    • This review check replaces old check 265 (See list of deprecated checks below.)

New checks related to 2.4.6 Headings and Labels (AA)

  1. Heading is descriptive (Review)

    • This rule is an ACT rule.

    • This rule checks that headings describe the topic or purpose of the content.

    • This rule replaces checks 37-41 (See list of deprecated checks below.)

  2. Each label describes its associated <code>input</code> element. (Review)

    • This check requires user to review if each label describes its associated <code>input</code> element.

    • This check replaces old check 189 (See list of deprecated checks below.)

New checks related to 2.4.7 Focus visible (AA)

  1. Element in sequential focus order has visible focus (Warning)

    • This check is an ACT rule.

    • This warning type check requires user to review if the keyboard focus indicator is visible.

New checks related to 3.3.2 Labels or instructions (A)

  1. Each label associated with an <code>input</code> element contains text. (Error)

    • This rule checks that a label contains text.

    • This rule replaces old check 188 (See below for list of deprecated checks.)

New checks related to 4.1.2 Name, Rule Value (A)

  1. Element with role attribute has required states and properties

    • This rule is an ACT rule.

    • This rule checks that elements that have an explicit role also specify all required states and properties.

  2. Form field has non-empty accessible name (Error)

    • This rule is an ACT rule.

    • This rule checks that each form field element has a non-empty accessible name.

  3. Menuitem has non-empty accessible name (Error)

    • This rule is an ACT rule.

    • This rule checks that each menu item element has a non-empty accessible name.

  4. Element with aria-hidden has no content in sequential focus navigation (Error)

    • This rule is an ACT rule.

    • This rule checks that no content marked with aria-hidden=true is part of the accessibility tree.

  5. Iframe elements with identical accessible names have equivalent purpose (Warning)

    • This rule is an ACT rule.

    • This rule checks that iFrames with the same accessible name have essentially the same purpose and function.

  6. Link has non-empty accessible name (Error)

    • This rule is an ACT rule.

    • This rule checks that each link element has a non-empty accessible name.

  7. Iframe element has non-empty accessible name (Error)

    • This rule is an ACT rule.

    • This rule checks that each iFrame element has a non-empty accessible name.

  8. Element with presentational children has no focusable content (Error)

    • This rule is an ACT rule.

    • This rule checks that each element which should be treated as having only presentational children has no focusable children.

  9. Button has non-empty accessible name (Error)

    • This rule is an ACT rule.

    • This rule checks that each button element has a non-empty accessible name.

  10. ARIA state or property is permitted (Error)

    • This rule is an ACT rule.

    • This rule checks that WAI-ARIA states or properties are allowed for the element they are specified on.

  11. Role attribute has valid value (Error)

    • This rule is an ACT rule.

    • This rule checks that each role attribute has a valid value.


Deprecated Checks

  • Check 1 All <code>img</code> elements have an <code>alt</code> attribute.

  • Check 3 Image Alt text is short.

  • Check 6 Alt text for all <code>img</code> elements is not placeholder text unless author has confirmed it is correct.

  • Check 7 Alt text for all <code>img</code> elements used as source anchors is not empty when there is no other text in the anchor.

  • Check 8 A long description is used for each <code>img</code> element that does not have Alt text conveying the same information as the image.

  • Check 14 For all <code>img</code> elements, text does not refer to the image by color alone.

  • Check 16 Alt text for all <code>img</code> elements is the empty string ("") if the image is decorative.

  • Check 21 <code>applet</code> should not use color alone.

  • Check 23 <code>applet</code> contains a text equivalent in the <code>alt</code> attribute of the <code>applet</code>.

  • Check 24 Text equivalents for <code>applet</code> must be updated if <code>applet</code> changes.

  • Check 25 <code>applet</code> contains a text equivalent in the body of the <code>applet</code>.

  • Check 55 <code>input</code> should not use color alone.

  • Check 73 <code>object</code> must not use color alone.

  • Check 80 All <code>objects</code> contain a text equivalent of the <code>object</code>.

  • Check 86 Color alone should not be used in the <code>script</code>.

  • Check 145 Links to multimedia have a link to text alternative.

  • Check 146 <code>object</code> link to multimedia file require equivalent alternatives (e.g., captions or auditory descriptions of the visual track).

  • Check 160 <code>object</code> may require a long description.

  • Check 163 All <code>embed</code> elements have an associated <code>noembed</code> element that contains a text equivalent to the <code>embed</code> element.

  • Check 178 Alt text for all <code>img</code> elements that are not used as source anchors conveys the same information as the image.

  • Check 188 Each label associated with an <code>input</code> element contains text.

  • Check 189 Each label describes its associated <code>input</code> element.

  • Check 221 The luminosity contrast ratio between text and background color is at least 5:1.

  • Check 222 The luminosity contrast ratio between link text and background color is at least 5:1.

  • Check 223 The luminosity contrast ratio between active link text and background color is at least 5:1.

  • Check 224 The luminosity contrast ratio between visited link text and background color is at least 5:1.

  • Check 238 All <code>input</code> elements, except those with with a <code>type</code> attribute value of "image", do not have an <code>alt</code> attribute.

  • Check 239 <code>title</code> attribute for all <code>img</code> elements is absent or the empty string ("") if the image is decorative.

  • Check 252 All text colors or no text colors are set.

  • Check 270 Unicode right-to-left marks or left-to-right marks are used whenever the HTML bidirectional algorithm produces undesirable results.

  • Check 271 All changes in text direction are marked using the <code>dir</code> attribute.

  • Check 353 Provide sufficient contrast between text and background colours.

  • Check 355 Text colour must provide high contrast with its background colour.

  • Check 357 Alt text should not be part of the filename.

  • Check 131 Use the <code>blockquote</code> element to mark-up block quotations.

  • check 111 All complex data tables have a summary.

  • check 136 All data tables contain <code>th</code> elements.

  • check 137 All layout tables do not contain <code>th</code> elements.

  • check 151 All data tables contain a <code>caption</code> unless the table is identified within the document.

  • check 168 All radio button groups are marked using <code>fieldset</code> and <code>legend</code> elements.

  • check 230 Use <code>thead</code> to group repeated table headers, <code>tfoot</code> for repeated table footers, and <code>tbody</code> for other groups of rows.

  • check 231 Use <code>colgroup</code> and <code>col</code> elements to group columns.

  • check 247 All checkbox groups are marked using <code>fieldset</code> and <code>legend</code> elements.

  • check 349 Data tables that contain both row and column headers use the <code>scope</code> attribute, or id and headers, to identify cells.

  • Check 26 <code>applet</code> user interface must be accessible.

  • Check 76 <code>object</code> user interface must be accessible - (codebase).

  • Check 89 User interface for <code>script</code> must be accessible.

  • Check 103 All <code>ondblclick</code> event handlers have corresponding keyboard-specific functions.

  • Check 104 All <code>onmousedown</code> event handlers have an associated <code>onkeydown</code> event handler.

  • Check 105 All <code>onmousemove</code> event handlers have corresponding keyboard-specific functions.

  • Check 106 All <code>onmouseout</code> event handlers have an associated <code>onblur</code> event handler.

  • Check 107 All <code>onmouseover</code> event handlers have an associated <code>onfocus</code> event handler.

  • Check 108 All <code>onmouseup</code> event handlers have an associated <code>onkeyup</code> event handler.

  • Check 22 <code>applets</code> cause screen flicker.

  • Check 30 All <code>objects</code> do not flicker.

  • Check 87 <code>script</code> should not cause screen flicker.

  • Check 50 Document contains a <code>title</code> element.

  • Check 51 <code>title</code> contains text.

  • Check 52 <code>title</code> is short.

  • Check 53 <code>title</code> is not placeholder text.

  • Check 54 <code>title</code> describes the document.

  • Check 37 The header following an <code>h1</code> is <code>h1</code> or <code>h2</code>.

  • Check 38 The header following an <code>h2</code> is <code>h1</code>, <code>h2</code> or <code>h3</code>.

  • Check 39 The header following an <code>h3</code> is <code>h1</code>, <code>h2</code>, <code>h3</code> or <code>h4</code>.

  • Check 40 The header following an <code>h4</code> is <code>h1</code>, <code>h2</code>, <code>h3</code>, <code>h4</code> or <code>h5</code>.

  • Check 41 The header following an <code>h5</code> is <code>h6</code> or any header less than <code>h6</code>.

  • Check 265 The tab order specified by <code>tabindex</code> attributes follows a logical order.


Additional Resources

For more information, see the following articles:

Did this answer your question?