+ Web Content Accessibility Guidelines (WCAG) 2.1 covers a wide range of recommendations for making Web content more + accessible. Following these guidelines will make content more accessible to a wider range of people with + disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, + speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities + and cognitive limitations; but will not address every user need for people with these disabilities. These guidelines + address accessibility of web content on desktops, laptops, tablets, and mobile devices. Following these guidelines + will also often make Web content more usable to users in general. + +
+Rule Identifier: 047fe0
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Jean-Yves Moyen. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
@@ -22,7 +22,7 @@ rule_meta: original_file: document-has-headings-for-non-repeated-content-047fe0.md description: | This rule checks that the non-repeated content contains a heading - last_modified: 8 July 2025 + last_modified: 7 October 2025 --- ## Applicability @@ -54,7 +54,7 @@ Neither this rule, nor technique [H69: Providing heading elements at the beginni - Having a heading for the non-repeated content is sufficient to pass [Success Criterion 2.4.1 Bypass blocks][sc241]. However, if headings are used for that goal, they will only benefit users who can actually navigate from heading to heading (such a functionality can be provided by browsers, browsers plugins, screen readers or other assistive technologies). Users without any possibility for headings navigation will be left without way of bypassing blocks of repeated content and will still experience accessibility issues. Therefore, it is recommended to provide other ways of bypassing blocks. - When headings are rendered without sufficient visual cues, they are not perceived as headings by sighted users. In this case, passing this rule might still fail [Technique H69: Providing heading elements at the beginning of each section of content][h69] and [Success Criterion 2.4.1 Bypass blocks][sc241]. Additionally, this is likely a failure of [Success Criterion 1.3.1 Info and Relationships][sc131]. -### Bibliography +### Other Resources - [Understanding Success Criterion 2.4.1: Bypass Blocks][usc241] - [H69: Providing heading elements at the beginning of each section of content][h69] @@ -85,7 +85,7 @@ The following aspects are required in using this rule. - [CSS Styling](https://www.w3.org/TR/act-rules-aspects/#input-aspects-css) - [DOM Tree](https://www.w3.org/TR/act-rules-aspects/#input-aspects-dom) -## Test Cases +## ExamplesRule Identifier: 09o5cg
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Jean-Yves Moyen. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
proposed: true @@ -20,7 +20,7 @@ rule_meta: original_file: text-contrast-enhanced-09o5cg.md description: | This rule checks that the highest possible contrast of every text character with its background meets the enhanced contrast requirement. - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Contrast (Enhanced) num: 1.4.6 @@ -61,7 +61,7 @@ This rule is closely related to [success criterion 1.4.3 Contrast (Minimum)][sc1 - Different browsers have different levels of support for CSS. This can cause contrast issues in one browser that do not appear in another. Because of that, this rule can produce different results depending on the browser that is used. For example, a text that is positioned using CSS transform may be on a different background in a browser that does not support CSS transform. - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have a [semantic role][] of `none` and fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.4.6: Contrast (Enhanced)](https://www.w3.org/WAI/WCAG22/Understanding/contrast-enhanced.html) - [G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG22/Techniques/general/G17) @@ -129,7 +129,7 @@ The following aspects are required in using this rule. - [CSS Styling](https://www.w3.org/TR/act-rules-aspects/#input-aspects-css) - [Language](https://www.w3.org/TR/act-rules-aspects/#input-aspects-text) -## Test Cases +## Examples ### Passed @@ -619,7 +619,7 @@ The _explicit semantic role_ of an element is determined by its [role attribute] The [role attribute][] takes a list of tokens. The explicit semantic role is the first valid role in this list. The valid roles are all non-abstract roles from [WAI-ARIA Specifications][]. If the element has no [role attribute][], or if it has one with no valid role, then this element has no explicit semantic role. -Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the [accessibility support base line][]. For the purposes of executing test cases in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. +Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the [accessibility support base line][]. For the purposes of executing examples in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. ### Focusable {#focusable} diff --git a/content/rules/0ssw9k/proposed.md b/content/rules/0ssw9k/proposed.md index 2446487e0..7410ab7d5 100644 --- a/content/rules/0ssw9k/proposed.md +++ b/content/rules/0ssw9k/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |Rule Identifier: 0ssw9k
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Wilco Fiers. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
proposed: true @@ -20,7 +20,7 @@ rule_meta: original_file: scrollable-element-keyboard-accessible-0ssw9k.md description: | This rule checks that scrollable elements or their descendants can be reached with sequential focus navigation so that they can be scrolled by keyboard - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Keyboard num: 2.1.1 @@ -39,8 +39,9 @@ This rule applies to any [HTML element][] that has [visible][] [children][] in t ## Expectation -For each target element, at least one of the following is true: -- the element is included in [sequential focus navigation][]; or +For each target element, at least one of the following is true: + +- the element is included in [sequential focus navigation][]; or - the element has a [descendant][] in the [flat tree][] that is included in [sequential focus navigation][]; or - the element is [inert][]. @@ -60,7 +61,7 @@ Some browsers will automatically make any [scrollable element][scrollable] focus Some browsers restrict scrolling to the [content box](https://drafts.csswg.org/css-box-4/#content-box) of elements; while others allow to scroll the full [border box](https://drafts.csswg.org/css-box-4/#border-box), hence including the element's padding. This results in some elements being scrollable with a browser but not with another. -### Bibliography +### Other Resources - [Understanding Success Criterion 2.1.1: Keyboard](https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html) - [G202: Ensuring keyboard control for all functionality](https://www.w3.org/WAI/WCAG22/Techniques/general/G202) @@ -113,7 +114,7 @@ The following aspects are required in using this rule. - [DOM Tree](https://www.w3.org/TR/act-rules-aspects/#input-aspects-dom) - [CSS Styling](https://www.w3.org/TR/act-rules-aspects/#input-aspects-css) -## Test Cases +## Examples ### Passed @@ -165,14 +166,14 @@ This [scrollable][] `section` element contains a link that is included in [seque #### Passed Example 3 -Open in a new tab +Open in a new tab This [scrollable][] `section` element is [inert][] because of the modal dialog, so neither the `section` nor its [descendant][] elements are included in [sequential focus navigation][]. ```htmlRule Identifier: 0va7u6
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Carlos Duarte, Wilco Fiers. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
@@ -22,7 +22,7 @@ rule_meta: original_file: image-no-text-0va7u6.md description: | This rule checks that images of text are not used - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Images of Text num: 1.4.5 @@ -57,7 +57,7 @@ This rule is designed specifically for [SC 1.4.5 Images of Text][sc1.4.5]. There There are no accessibility support issues known. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.4.5: Images of Text][sc1.4.5] - [Understanding Success Criterion 1.4.9: Images of Text (No Exception)][sc1.4.9] @@ -99,7 +99,7 @@ The following aspects are required in using this rule. - [CSS Styling](https://www.w3.org/TR/act-rules-aspects/#input-aspects-css) - [Language](https://www.w3.org/TR/act-rules-aspects/#input-aspects-text) -## Test Cases +## Examples ### Passed diff --git a/content/rules/1a02b0/proposed.md b/content/rules/1a02b0/proposed.md index fef945637..c0820dd11 100644 --- a/content/rules/1a02b0/proposed.md +++ b/content/rules/1a02b0/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |Rule Identifier: 1a02b0
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Brian Bors, Wilco Fiers. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
@@ -22,7 +22,7 @@ rule_meta: original_file: video-transcript-1a02b0.md description: | This rule checks that non-streaming `video` elements have all audio and visual information available in a transcript. - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Media Alternative (Prerecorded) num: 1.2.8 @@ -49,7 +49,7 @@ This rule assumes that a mechanism is available to start the video and that the There are no accessibility support issues known. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-or-media-alternative-prerecorded) - [Understanding Success Criterion 1.2.8: Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/media-alternative-prerecorded) @@ -96,7 +96,7 @@ The following aspects are required in using this rule. - Visual output (no link available) - [Language](https://www.w3.org/TR/act-rules-aspects/#input-aspects-text) -## Test Cases +## ExamplesRule Identifier: 1ea59c
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Brian Bors, Wilco Fiers. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
@@ -22,7 +22,7 @@ rule_meta: original_file: video-audio-description-1ea59c.md description: | This rule checks that non-streaming `video` elements have all visual information also contained in the audio. - last_modified: 8 July 2025 + last_modified: 7 October 2025 --- ## Applicability @@ -43,7 +43,7 @@ This rule assumes that a mechanism is available to start the video and that the There are only a few implementations of video players (without third party technologies) that support audio description tracks at the time of writing. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-or-media-alternative-prerecorded) - [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G78) @@ -101,7 +101,7 @@ The following aspects are required in using this rule. - Visual output (no link available) - [Language](https://www.w3.org/TR/act-rules-aspects/#input-aspects-text) -## Test Cases +## Examples ### Passed diff --git a/content/rules/1ec09b/proposed.md b/content/rules/1ec09b/proposed.md index 8c7e04785..99d1e7c5f 100644 --- a/content/rules/1ec09b/proposed.md +++ b/content/rules/1ec09b/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |Rule Identifier: 1ec09b
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Brian Bors, Wilco Fiers. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
@@ -22,7 +22,7 @@ rule_meta: original_file: video-strict-alternative-for-visual-1ec09b.md description: | This rule checks that `video` elements with audio have audio description. - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Audio Description (Prerecorded) num: 1.2.5 @@ -51,7 +51,7 @@ For each test target, the [outcome](#outcome) of at least one of the following r The HTML `video` element can also have a `track` element that provides an audio description. This should provide assistive technologies with a timed text description of visual information in a video. However, there is no native support in any major browser for this technique. Technique [H96: Using the track element to provide audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/html/H96) can not be relied upon to conform to [1.2.5: Audio Description (Prerecorded)](https://www.w3.org/TR/WCAG22/#audio-description-prerecorded). -### Bibliography +### Other Resources - [Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-description-prerecorded.html) - [G78: Providing a second, user-selectable, audio track that includes audio descriptions](https://www.w3.org/WAI/WCAG22/Techniques/general/G78) @@ -118,7 +118,7 @@ Outcomes of the following rules are required as input for this rule. - [Video element visual content has audio description](/standards-guidelines/act/rules/video-audio-description-1ea59c/) - [Video element content is media alternative for text](/standards-guidelines/act/rules/video-as-media-alternative-ab4d13/) -## Test Cases +## ExamplesRule Identifier: 23a2a8
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Wilco Fiers. Previous Authors: Anne Thyme Nørregaard, Stein Erik Skotkjerra. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
proposed: true @@ -20,7 +20,7 @@ rule_meta: original_file: image-non-empty-accessible-name-23a2a8.md description: | This rule checks that each image either has a non-empty accessible name or is marked up as decorative. - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Non-text Content num: 1.1.1 @@ -47,7 +47,7 @@ There are no assumptions. - Images can have their role set to `presentation` through an empty `alt` attribute. [Presentational Roles Conflict Resolution][] does not specify what to do if such an image is [focusable][] (it only specifies what to do in case of explicit `role="none"` or `role="presentation"`). Some browsers expose these images and some don't. Thus, this rule may fail for technologies that expose these without creating an accessibility issue for users of other technologies. - `svg` elements have an [implicit role][] of `graphics-document` in [svg-aam](https://www.w3.org/TR/svg-aam-1.0/#details-id-66). There are popular browsers that do not follow [svg-aam](https://www.w3.org/TR/svg-aam-1.0/#details-id-66) and instead expose SVG elements with a different [semantic role][], such as `image`, `generic` or `SvgRoot`. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) - [G94: Providing short text alternative for non-text content that serves the same purpose and presents the same information as the non-text content](https://www.w3.org/WAI/WCAG22/Techniques/general/G94) @@ -108,7 +108,7 @@ The following aspects are required in using this rule. - [DOM Tree](https://www.w3.org/TR/act-rules-aspects/#input-aspects-dom) - [CSS Styling](https://www.w3.org/TR/act-rules-aspects/#input-aspects-css) -## Test Cases +## Examples ### Passed @@ -327,7 +327,7 @@ The _explicit semantic role_ of an element is determined by its [role attribute] The [role attribute][] takes a list of tokens. The explicit semantic role is the first valid role in this list. The valid roles are all non-abstract roles from [WAI-ARIA Specifications][]. If the element has no [role attribute][], or if it has one with no valid role, then this element has no explicit semantic role. -Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the [accessibility support base line][]. For the purposes of executing test cases in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. +Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the [accessibility support base line][]. For the purposes of executing examples in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. ### Focusable {#focusable} diff --git a/content/rules/24afc2/proposed.md b/content/rules/24afc2/proposed.md index aa64d6e54..ff92d9cc1 100644 --- a/content/rules/24afc2/proposed.md +++ b/content/rules/24afc2/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |Rule Identifier: 24afc2
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Jean-Yves Moyen. Previous Authors: Jey Nandakumar. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
proposed: true @@ -20,7 +20,7 @@ rule_meta: original_file: important-letter-spacing-wide-enough-24afc2.md description: | This rule checks that the `style` attribute is not used to prevent adjusting `letter-spacing` by using `!important`, except if it's at least 0.12 times the font size. - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Text Spacing num: 1.4.12 @@ -60,15 +60,15 @@ CSS specifications define each declaration as being either [important][] (if it While some assistive technologies are able to set [user origin][] or [user agent origin][] styles, others, such as browser extensions, are only able to set styles with the [author origin][]. Such assistive technologies cannot create styles "winning" the [cascade sort][] over a `style` attribute with an [important][] declaration. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.4.12: Text Spacing](https://www.w3.org/WAI/WCAG22/Understanding/text-spacing.html) - [CSS Text Module Level 3 - Spacing](https://www.w3.org/TR/css-text-3/#spacing) - [CSS Visual formatting model details](https://drafts.csswg.org/css2/visudet.html) -### About test cases +### About examples -Test cases descriptions abusively refer to the CSS properties of text nodes, meaning the one of their parent. +Example descriptions abusively refer to the CSS properties of text nodes, meaning the one of their parent. ## Accessibility Requirements Mapping @@ -94,7 +94,7 @@ The following aspects are required in using this rule. - [DOM Tree](https://www.w3.org/TR/act-rules-aspects/#input-aspects-dom) - [CSS Styling](https://www.w3.org/TR/act-rules-aspects/#input-aspects-css) -## Test Cases +## Examples ### Passed diff --git a/content/rules/2779a5/proposed.md b/content/rules/2779a5/proposed.md index 49ea1f0b3..310f1a41e 100644 --- a/content/rules/2779a5/proposed.md +++ b/content/rules/2779a5/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |Rule Identifier: 2779a5
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Anne Thyme Nørregaard, Bryn Anderson, Jey Nandakumar, Stein Erik Skotkjerra, Wilco Fiers. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
proposed: true @@ -20,7 +20,7 @@ rule_meta: original_file: html-page-non-empty-title-2779a5.md description: | This rule checks that a non-embedded HTML page has a non-empty title. - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Page Titled num: 2.4.2 @@ -57,7 +57,7 @@ There are no accessibility support issues known. - [HTML page title is descriptive](https://www.w3.org/WAI/standards-guidelines/act/rules/c4a8a4/) -### Bibliography +### Other Resources - [Understanding Success Criterion 2.4.2: Page Titled](https://www.w3.org/WAI/WCAG22/Understanding/page-titled) - [G88: Providing descriptive titles for Web pages](https://www.w3.org/WAI/WCAG22/Techniques/general/G88) @@ -111,7 +111,7 @@ The following aspects are required in using this rule. - [DOM Tree](https://www.w3.org/TR/act-rules-aspects/#input-aspects-dom) -## Test Cases +## ExamplesRule Identifier: 2eb176
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Brian Bors, Wilco Fiers. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
@@ -22,7 +22,7 @@ rule_meta: original_file: audio-transcript-2eb176.md description: | This rule checks that `audio` elements have a transcript that includes all auditory information. - last_modified: 8 July 2025 + last_modified: 7 October 2025 --- ## Applicability @@ -48,7 +48,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [Understanding SC 1.2.1:Audio-only and Video-only (Prerecorded)](https://www.w3.org/WAI/WCAG22/Understanding/audio-only-and-video-only-prerecorded) - [G158: Providing an alternative for time-based media for audio-only content](https://www.w3.org/WAI/WCAG22/Techniques/general/G158) @@ -66,7 +66,7 @@ The following aspects are required in using this rule. - [Audio output](https://www.w3.org/TR/act-rules-aspects/#input-aspects-audio-out) - [Language](https://www.w3.org/TR/act-rules-aspects/#input-aspects-text) -## Test Cases +## ExamplesRule Identifier: 2ee8b8
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Anne Thyme Nørregaard, Bryn Anderson, Jey Nandakumar. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
proposed: true @@ -20,7 +20,7 @@ rule_meta: original_file: visible-label-in-accessible-name-2ee8b8.md description: | This rule checks that interactive elements labeled through content have their visible label as part of their accessible name. - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Label in Name num: 2.5.3 @@ -53,7 +53,7 @@ This rule assumes that all resources needed for rendering the page are properly Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some elements can have one of the applicable [semantic roles][semantic role] and fail this rule with some technology but users of other technologies would not experience any accessibility issue. -### Bibliography +### Other Resources - [Understanding Success Criterion 2.5.3: Label in Name][understand253] - [G208: Including the text of the visible label as part of the accessible name](https://www.w3.org/WAI/WCAG22/Techniques/general/G208) @@ -95,7 +95,7 @@ The following aspects are required in using this rule. - [DOM Tree](https://www.w3.org/TR/act-rules-aspects/#input-aspects-dom) - [CSS Styling](https://www.w3.org/TR/act-rules-aspects/#input-aspects-css) -## Test Cases +## Examples ### Passed @@ -284,7 +284,7 @@ The _explicit semantic role_ of an element is determined by its [role attribute] The [role attribute][] takes a list of tokens. The explicit semantic role is the first valid role in this list. The valid roles are all non-abstract roles from [WAI-ARIA Specifications][]. If the element has no [role attribute][], or if it has one with no valid role, then this element has no explicit semantic role. -Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the [accessibility support base line][]. For the purposes of executing test cases in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. +Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the [accessibility support base line][]. For the purposes of executing examples in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. ### Focusable {#focusable} diff --git a/content/rules/2t702h/proposed.md b/content/rules/2t702h/proposed.md index 7cf3b1bbb..df75d48cf 100644 --- a/content/rules/2t702h/proposed.md +++ b/content/rules/2t702h/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |Rule Identifier: 2t702h
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Wilco Fiers. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
proposed: true @@ -20,7 +20,7 @@ rule_meta: original_file: summary-non-empty-accessible-name-2t702h.md description: | This rule checks that each `summary` element has a non-empty accessible name. - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Name, Role, Value num: 4.1.2 @@ -55,7 +55,7 @@ The rule assumes that all `summary` elements are [user interface components as d There is a difference in how user agents expose the triangle indicating the control's expand state. As a result, some user agents include the triangle in the accessible name of the summary element. -### Bibliography +### Other Resources - [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) - [ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA14) @@ -87,7 +87,7 @@ The following aspects are required in using this rule. - [DOM Tree](https://www.w3.org/TR/act-rules-aspects/#input-aspects-dom) - [CSS Styling](https://www.w3.org/TR/act-rules-aspects/#input-aspects-css) -## Test Cases +## Examples ### Passed @@ -275,7 +275,7 @@ The _explicit semantic role_ of an element is determined by its [role attribute] The [role attribute][] takes a list of tokens. The explicit semantic role is the first valid role in this list. The valid roles are all non-abstract roles from [WAI-ARIA Specifications][]. If the element has no [role attribute][], or if it has one with no valid role, then this element has no explicit semantic role. -Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the [accessibility support base line][]. For the purposes of executing test cases in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. +Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the [accessibility support base line][]. For the purposes of executing examples in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support. ### Focusable {#focusable} diff --git a/content/rules/307n5z/proposed.md b/content/rules/307n5z/proposed.md index 2deb4a878..59115ec2c 100644 --- a/content/rules/307n5z/proposed.md +++ b/content/rules/307n5z/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |Rule Identifier: 307n5z
-Date: Updated 8 July 2025
+Date: Updated 7 October 2025
Authors: Wilco Fiers. Contributors: Participants of the ACT Rules Community Group (CG).
This rule was written in the ACT Rules Community Group. It is written as part of the EU-funded WAI-Tools Project. Implementations are part of the EU funded WAI-CooP Project. It will be reviewed by the Accessibility Guidelines Working Group (AG WG).
proposed: true @@ -20,7 +20,7 @@ rule_meta: original_file: presentational-children-no-focusable-content-307n5z.md description: | This rule checks that elements with a role that makes its children presentational do not contain focusable elements. - last_modified: 8 July 2025 + last_modified: 7 October 2025 scs_tested: - handle: Name, Role, Value num: 4.1.2 @@ -49,13 +49,13 @@ This rule assumes that elements that are part of [sequential focus navigation][] Several major browsers ignore the WAI-ARIA requirements on [presentational children][] for most or sometimes all roles, or in presence of focusable content. Since some browsers implement presentational children while others do not, pages failing this rule may only be problematic with some browsers. -This rule is often misunderstood as applying to elements with an _explicit_ role of `presentation`. In fact, this rule only applies to elements which have been given an _implicit_ role of `presentation` through the [presentational children][] mechanism. Similarly, this rule does not apply to elements with `aria-hidden="true"`. +This rule is often misunderstood as applying to elements with an _explicit_ role of `presentation`. In fact, this rule only applies to elements which have been given an _implicit_ role of `presentation` through the [presentational children][] mechanism. Similarly, this rule does not apply to elements with `aria-hidden="true"`. ### Related rules - [Element with aria-hidden has no content in sequential focus navigation](https://www.w3.org/WAI/standards-guidelines/act/rules/6cfa84/) -### Bibliography +### Other Resources - [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships) - [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) @@ -85,7 +85,7 @@ The following aspects are required in using this rule. - [DOM Tree](https://www.w3.org/TR/act-rules-aspects/#input-aspects-dom) - [CSS Styling](https://www.w3.org/TR/act-rules-aspects/#input-aspects-css) -## Test Cases +## Examples ### Passed @@ -135,7 +135,7 @@ This element with the `menuitemcheckbox` role has an `input` element as a descen Open in a new tab -This `