From 328cf1b955ea76c27c5132c213cfb0f7a158028d Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Tue, 30 Sep 2025 18:51:41 +0000 Subject: [PATCH 1/7] Bump nokogiri from 1.18.8 to 1.18.9 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.18.8 to 1.18.9. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.18.8...v1.18.9) --- updated-dependencies: - dependency-name: nokogiri dependency-version: 1.18.9 dependency-type: direct:production ... Signed-off-by: dependabot[bot] --- Gemfile.lock | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Gemfile.lock b/Gemfile.lock index aafec8dcd..31e0c9f3a 100644 --- a/Gemfile.lock +++ b/Gemfile.lock @@ -99,9 +99,9 @@ GEM mercenary (0.4.0) net-http (0.6.0) uri - nokogiri (1.18.8-arm64-darwin) + nokogiri (1.18.9-arm64-darwin) racc (~> 1.4) - nokogiri (1.18.8-x86_64-linux-gnu) + nokogiri (1.18.9-x86_64-linux-gnu) racc (~> 1.4) octokit (6.1.1) faraday (>= 1, < 3) From 66fc1992ef99e558230fd2f79b5e478517678cb8 Mon Sep 17 00:00:00 2001 From: Wilco Fiers Date: Thu, 2 Oct 2025 17:07:58 +0200 Subject: [PATCH 2/7] Add Useful links to approved rules --- _layouts/act_rule.html | 2 -- 1 file changed, 2 deletions(-) diff --git a/_layouts/act_rule.html b/_layouts/act_rule.html index 89508eac6..3d3e77262 100644 --- a/_layouts/act_rule.html +++ b/_layouts/act_rule.html @@ -163,7 +163,6 @@

Implementations

{%- endunless %} {%- endif %} -{%- if ruleId and page.github.path contains "/proposed.md" %}

Useful Links

-{%- endif %} From 18a9ea188eafecfd22d2098acfecfcd7f4bef055 Mon Sep 17 00:00:00 2001 From: WilcoFiers Date: Mon, 6 Oct 2025 16:30:28 +0000 Subject: [PATCH 3/7] Change bibliography to other resources (#2350) --- content-assets/wcag-act-rules/testcases.json | 82 ++++++++++++++++--- ...7b58829c18976ac66f3874f40c5be712fe64b.html | 41 ++++++++++ ...2ef64b86fcd30dadeea664029af028382d1b4.html | 14 ++++ ...160492f9d0a309b4f8624e51d3380b318b046.html | 9 ++ ...6be0bc987f29ac92355ed781fe06ae8e57176.html | 9 ++ ...917e0b17ba9ddbd9fe01239a94519b5bc0458.html | 48 +++++++++++ content/rules/047fe0/proposed.md | 8 +- content/rules/09o5cg/proposed.md | 8 +- content/rules/0ssw9k/proposed.md | 23 +++--- content/rules/0va7u6/proposed.md | 8 +- content/rules/1a02b0/proposed.md | 8 +- content/rules/1ea59c/proposed.md | 8 +- content/rules/1ec09b/proposed.md | 8 +- content/rules/23a2a8/proposed.md | 8 +- content/rules/24afc2/proposed.md | 8 +- content/rules/2779a5/proposed.md | 8 +- content/rules/2eb176/proposed.md | 8 +- content/rules/2ee8b8/proposed.md | 8 +- content/rules/2t702h/proposed.md | 8 +- content/rules/307n5z/proposed.md | 20 ++--- content/rules/36b590/proposed.md | 8 +- content/rules/3e12e1/proposed.md | 8 +- content/rules/3ea0c8/proposed.md | 8 +- content/rules/46ca7f/proposed.md | 6 +- content/rules/4b1c6c/proposed.md | 8 +- content/rules/4c31df/proposed.md | 8 +- content/rules/4e8ab6/proposed.md | 16 ++-- content/rules/59796f/proposed.md | 8 +- content/rules/59br37/proposed.md | 8 +- content/rules/5b7ae0/proposed.md | 8 +- content/rules/5c01ea/proposed.md | 8 +- content/rules/5effbb/proposed.md | 8 +- content/rules/5f99a7/proposed.md | 8 +- content/rules/674b10/proposed.md | 12 +-- content/rules/6a7281/proposed.md | 8 +- content/rules/6cfa84/proposed.md | 8 +- content/rules/73f2c2/proposed.md | 8 +- content/rules/7677a9/proposed.md | 8 +- content/rules/78fd32/proposed.md | 8 +- content/rules/7d6734/proposed.md | 8 +- content/rules/80af7b/proposed.md | 8 +- content/rules/80f0bf/proposed.md | 8 +- content/rules/8fc3b6/proposed.md | 8 +- content/rules/97a4e1/proposed.md | 8 +- content/rules/9bd38c/proposed.md | 8 +- content/rules/9e45ec/proposed.md | 8 +- content/rules/9eb3f6/proposed.md | 8 +- content/rules/a1b64e/proposed.md | 70 ++++++++-------- content/rules/a25f45/proposed.md | 8 +- content/rules/aaa1bf/proposed.md | 8 +- content/rules/ab4d13/proposed.md | 8 +- content/rules/ac7dc6/proposed.md | 8 +- content/rules/afb423/proposed.md | 8 +- content/rules/afw4f7/proposed.md | 8 +- content/rules/aizyf1/proposed.md | 8 +- content/rules/akn7bn/proposed.md | 8 +- content/rules/b20e66/proposed.md | 8 +- content/rules/b33eff/proposed.md | 8 +- content/rules/b40fd1/proposed.md | 8 +- content/rules/b49b2e/proposed.md | 8 +- content/rules/b4f0c3/proposed.md | 8 +- content/rules/b5c3f8/proposed.md | 8 +- content/rules/bc4a75/proposed.md | 8 +- content/rules/bc659a/proposed.md | 8 +- content/rules/bf051a/proposed.md | 8 +- content/rules/bisz58/proposed.md | 8 +- content/rules/c249d5/proposed.md | 8 +- content/rules/c3232f/proposed.md | 8 +- content/rules/c487ae/proposed.md | 8 +- content/rules/c4a8a4/proposed.md | 8 +- content/rules/c5a4ea/proposed.md | 8 +- content/rules/cae760/proposed.md | 8 +- content/rules/cc0f0a/proposed.md | 8 +- content/rules/cf77f2/proposed.md | 8 +- content/rules/d0f69e/proposed.md | 8 +- content/rules/d7ba54/proposed.md | 8 +- content/rules/de46e4/proposed.md | 8 +- content/rules/e086e5/proposed.md | 8 +- content/rules/e6952f/proposed.md | 8 +- content/rules/e7aa44/proposed.md | 8 +- content/rules/e88epe/proposed.md | 8 +- content/rules/eac66b/proposed.md | 8 +- content/rules/ebe86a/proposed.md | 8 +- content/rules/ee13b5/proposed.md | 8 +- content/rules/efbfc7/proposed.md | 8 +- content/rules/f196ce/proposed.md | 8 +- content/rules/f51b46/proposed.md | 8 +- content/rules/fd26cf/proposed.md | 8 +- content/rules/fd3a94/proposed.md | 8 +- content/rules/ff89c9/proposed.md | 8 +- content/rules/ffbc54/proposed.md | 8 +- content/rules/ffd0e9/proposed.md | 8 +- content/rules/in6db8/proposed.md | 8 +- content/rules/m6b1q3/proposed.md | 8 +- content/rules/off6ek/proposed.md | 8 +- content/rules/oj04fd/proposed.md | 8 +- content/rules/qt1vmo/proposed.md | 8 +- content/rules/ucwvc8/proposed.md | 8 +- content/rules/ye5d6e/proposed.md | 8 +- 99 files changed, 615 insertions(+), 431 deletions(-) create mode 100644 content-assets/wcag-act-rules/testcases/0ssw9k/fa27b58829c18976ac66f3874f40c5be712fe64b.html create mode 100644 content-assets/wcag-act-rules/testcases/4e8ab6/8122ef64b86fcd30dadeea664029af028382d1b4.html create mode 100644 content-assets/wcag-act-rules/testcases/4e8ab6/cde160492f9d0a309b4f8624e51d3380b318b046.html create mode 100644 content-assets/wcag-act-rules/testcases/674b10/bd56be0bc987f29ac92355ed781fe06ae8e57176.html create mode 100644 content-assets/wcag-act-rules/testcases/a1b64e/dcf917e0b17ba9ddbd9fe01239a94519b5bc0458.html diff --git a/content-assets/wcag-act-rules/testcases.json b/content-assets/wcag-act-rules/testcases.json index 4282ce91f..cb1a66bb8 100644 --- a/content-assets/wcag-act-rules/testcases.json +++ b/content-assets/wcag-act-rules/testcases.json @@ -3,7 +3,7 @@ "website": "https://www.w3.org/WAI/standards-guidelines/act/rules/", "license": "https://act-rules.github.io/pages/license/", "description": "Accessibility conformance testing rules for HTML", - "count": 1184, + "count": 1186, "testcases": [ { "ruleId": "674b10", @@ -20069,10 +20069,10 @@ "ruleName": "Focusable element has no keyboard trap via standard navigation", "ruleAccessibilityRequirements": null, "expected": "passed", - "testcaseId": "6ee6cdfc0ae79ec72379b9ee4df9c1920b09ba15", + "testcaseId": "dcf917e0b17ba9ddbd9fe01239a94519b5bc0458", "testcaseTitle": "Passed Example 4", - "relativePath": "testcases/a1b64e/6ee6cdfc0ae79ec72379b9ee4df9c1920b09ba15.html", - "url": "https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/a1b64e/6ee6cdfc0ae79ec72379b9ee4df9c1920b09ba15.html", + "relativePath": "testcases/a1b64e/dcf917e0b17ba9ddbd9fe01239a94519b5bc0458.html", + "url": "https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/a1b64e/dcf917e0b17ba9ddbd9fe01239a94519b5bc0458.html", "rulePage": "https://www.w3.org/WAI/standards-guidelines/act/rules/a1b64e/proposed/" }, { @@ -25012,12 +25012,74 @@ } }, "expected": "inapplicable", - "testcaseId": "351e4bd097e4e1217d64a6c32ae09987c8d4db4a", + "testcaseId": "bd56be0bc987f29ac92355ed781fe06ae8e57176", "testcaseTitle": "Inapplicable Example 4", - "relativePath": "testcases/674b10/351e4bd097e4e1217d64a6c32ae09987c8d4db4a.html", - "url": "https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/674b10/351e4bd097e4e1217d64a6c32ae09987c8d4db4a.html", + "relativePath": "testcases/674b10/bd56be0bc987f29ac92355ed781fe06ae8e57176.html", + "url": "https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/674b10/bd56be0bc987f29ac92355ed781fe06ae8e57176.html", "rulePage": "https://www.w3.org/WAI/standards-guidelines/act/rules/674b10/proposed/" }, + { + "ruleId": "4e8ab6", + "ruleName": "Element with role attribute has required states and properties", + "ruleAccessibilityRequirements": { + "wcag-technique:ARIA5": { + "forConformance": false, + "failed": "not satisfied", + "passed": "further testing needed", + "inapplicable": "further testing needed" + }, + "aria12:requiredState": { + "title": "ARIA 1.2, 5.2.2 Required States and Properties", + "forConformance": true, + "failed": "not satisfied", + "passed": "satisfied", + "inapplicable": "satisfied" + }, + "wcag20:1.3.1": { + "secondary": "This success criterion is **less strict** than this rule. This is because browsers and assistive technologies will often fall back on a non-standard default value, which may be sufficient. Some of the failed examples may satisfy this success criterion." + }, + "wcag20:4.1.2": { + "secondary": "This success criterion is **less strict** than this rule. This is because browsers and assistive technologies will often fall back on a non-standard default value, which may be sufficient. Some of the failed examples may satisfy this success criterion." + } + }, + "expected": "passed", + "testcaseId": "8122ef64b86fcd30dadeea664029af028382d1b4", + "testcaseTitle": "Passed Example 6", + "relativePath": "testcases/4e8ab6/8122ef64b86fcd30dadeea664029af028382d1b4.html", + "url": "https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/4e8ab6/8122ef64b86fcd30dadeea664029af028382d1b4.html", + "rulePage": "https://www.w3.org/WAI/standards-guidelines/act/rules/4e8ab6/proposed/" + }, + { + "ruleId": "4e8ab6", + "ruleName": "Element with role attribute has required states and properties", + "ruleAccessibilityRequirements": { + "wcag-technique:ARIA5": { + "forConformance": false, + "failed": "not satisfied", + "passed": "further testing needed", + "inapplicable": "further testing needed" + }, + "aria12:requiredState": { + "title": "ARIA 1.2, 5.2.2 Required States and Properties", + "forConformance": true, + "failed": "not satisfied", + "passed": "satisfied", + "inapplicable": "satisfied" + }, + "wcag20:1.3.1": { + "secondary": "This success criterion is **less strict** than this rule. This is because browsers and assistive technologies will often fall back on a non-standard default value, which may be sufficient. Some of the failed examples may satisfy this success criterion." + }, + "wcag20:4.1.2": { + "secondary": "This success criterion is **less strict** than this rule. This is because browsers and assistive technologies will often fall back on a non-standard default value, which may be sufficient. Some of the failed examples may satisfy this success criterion." + } + }, + "expected": "inapplicable", + "testcaseId": "cde160492f9d0a309b4f8624e51d3380b318b046", + "testcaseTitle": "Inapplicable Example 2", + "relativePath": "testcases/4e8ab6/cde160492f9d0a309b4f8624e51d3380b318b046.html", + "url": "https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/4e8ab6/cde160492f9d0a309b4f8624e51d3380b318b046.html", + "rulePage": "https://www.w3.org/WAI/standards-guidelines/act/rules/4e8ab6/proposed/" + }, { "ruleId": "0ssw9k", "ruleName": "Scrollable content can be reached with sequential focus navigation", @@ -25072,10 +25134,10 @@ } }, "expected": "passed", - "testcaseId": "c5f649f91ebe4979270972db7c42279a74efc6c5", + "testcaseId": "fa27b58829c18976ac66f3874f40c5be712fe64b", "testcaseTitle": "Passed Example 3", - "relativePath": "testcases/0ssw9k/c5f649f91ebe4979270972db7c42279a74efc6c5.html", - "url": "https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/0ssw9k/c5f649f91ebe4979270972db7c42279a74efc6c5.html", + "relativePath": "testcases/0ssw9k/fa27b58829c18976ac66f3874f40c5be712fe64b.html", + "url": "https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/0ssw9k/fa27b58829c18976ac66f3874f40c5be712fe64b.html", "rulePage": "https://www.w3.org/WAI/standards-guidelines/act/rules/0ssw9k/proposed/" }, { diff --git a/content-assets/wcag-act-rules/testcases/0ssw9k/fa27b58829c18976ac66f3874f40c5be712fe64b.html b/content-assets/wcag-act-rules/testcases/0ssw9k/fa27b58829c18976ac66f3874f40c5be712fe64b.html new file mode 100644 index 000000000..dee16fdff --- /dev/null +++ b/content-assets/wcag-act-rules/testcases/0ssw9k/fa27b58829c18976ac66f3874f40c5be712fe64b.html @@ -0,0 +1,41 @@ + + + + Passed Example 3 + + + +
+

WCAG 2.1 Abstract

+

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

+
+ +

WCAG 2.2

+

+ WCAG 2.2 +

+ + + + + \ No newline at end of file diff --git a/content-assets/wcag-act-rules/testcases/4e8ab6/8122ef64b86fcd30dadeea664029af028382d1b4.html b/content-assets/wcag-act-rules/testcases/4e8ab6/8122ef64b86fcd30dadeea664029af028382d1b4.html new file mode 100644 index 000000000..fa7d2f55d --- /dev/null +++ b/content-assets/wcag-act-rules/testcases/4e8ab6/8122ef64b86fcd30dadeea664029af028382d1b4.html @@ -0,0 +1,14 @@ + + + + Passed Example 6 + + + + + + + \ No newline at end of file diff --git a/content-assets/wcag-act-rules/testcases/4e8ab6/cde160492f9d0a309b4f8624e51d3380b318b046.html b/content-assets/wcag-act-rules/testcases/4e8ab6/cde160492f9d0a309b4f8624e51d3380b318b046.html new file mode 100644 index 000000000..7c3b9a407 --- /dev/null +++ b/content-assets/wcag-act-rules/testcases/4e8ab6/cde160492f9d0a309b4f8624e51d3380b318b046.html @@ -0,0 +1,9 @@ + + + + Inapplicable Example 2 + + + + + \ No newline at end of file diff --git a/content-assets/wcag-act-rules/testcases/674b10/bd56be0bc987f29ac92355ed781fe06ae8e57176.html b/content-assets/wcag-act-rules/testcases/674b10/bd56be0bc987f29ac92355ed781fe06ae8e57176.html new file mode 100644 index 000000000..041aa6f4d --- /dev/null +++ b/content-assets/wcag-act-rules/testcases/674b10/bd56be0bc987f29ac92355ed781fe06ae8e57176.html @@ -0,0 +1,9 @@ + + + + Inapplicable Example 4 + + + + + \ No newline at end of file diff --git a/content-assets/wcag-act-rules/testcases/a1b64e/dcf917e0b17ba9ddbd9fe01239a94519b5bc0458.html b/content-assets/wcag-act-rules/testcases/a1b64e/dcf917e0b17ba9ddbd9fe01239a94519b5bc0458.html new file mode 100644 index 000000000..f3ac8fe12 --- /dev/null +++ b/content-assets/wcag-act-rules/testcases/a1b64e/dcf917e0b17ba9ddbd9fe01239a94519b5bc0458.html @@ -0,0 +1,48 @@ + + + + Passed Example 4 + + +
Main page content with some link
+ + + + + + \ No newline at end of file diff --git a/content/rules/047fe0/proposed.md b/content/rules/047fe0/proposed.md index bb111876a..ed3c87609 100644 --- a/content/rules/047fe0/proposed.md +++ b/content/rules/047fe0/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

Rule Identifier: 047fe0

-

Date: Updated 8 July 2025

+

Date: Updated 6 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: 6 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 +## Examples
These HTML and CSS files are used in several examples: diff --git a/content/rules/09o5cg/proposed.md b/content/rules/09o5cg/proposed.md index 1759fd6a9..1fb997ad8 100644 --- a/content/rules/09o5cg/proposed.md +++ b/content/rules/09o5cg/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

Rule Identifier: 09o5cg

-

Date: Updated 8 July 2025

+

Date: Updated 6 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: 6 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 diff --git a/content/rules/0ssw9k/proposed.md b/content/rules/0ssw9k/proposed.md index 2446487e0..c1c9591d5 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 6 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: 6 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][]. ```html
@@ -197,11 +198,11 @@ This [scrollable][] `section` element is [inert][] because of the modal dialog, ``` diff --git a/content/rules/0va7u6/proposed.md b/content/rules/0va7u6/proposed.md index c368f34b5..825bb346f 100644 --- a/content/rules/0va7u6/proposed.md +++ b/content/rules/0va7u6/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

Rule Identifier: 0va7u6

-

Date: Updated 8 July 2025

+

Date: Updated 6 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: 6 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..9ab118fce 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 6 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: 6 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 +## Examples
These HTML files are used in several examples: diff --git a/content/rules/1ea59c/proposed.md b/content/rules/1ea59c/proposed.md index d0ae2300d..a87371417 100644 --- a/content/rules/1ea59c/proposed.md +++ b/content/rules/1ea59c/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

Rule Identifier: 1ea59c

-

Date: Updated 8 July 2025

+

Date: Updated 6 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: 6 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..0eb725a72 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 6 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: 6 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 +## Examples
This HTML file is used in several examples: diff --git a/content/rules/23a2a8/proposed.md b/content/rules/23a2a8/proposed.md index 16b081d56..588c873cb 100644 --- a/content/rules/23a2a8/proposed.md +++ b/content/rules/23a2a8/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

Rule Identifier: 23a2a8

-

Date: Updated 8 July 2025

+

Date: Updated 6 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: 6 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 diff --git a/content/rules/24afc2/proposed.md b/content/rules/24afc2/proposed.md index aa64d6e54..78f96d532 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 6 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: 6 October 2025 scs_tested: - handle: Text Spacing num: 1.4.12 @@ -60,7 +60,7 @@ 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) @@ -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..7b74e54ad 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 6 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: 6 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 +## Examples
These HTML files are used in several examples: diff --git a/content/rules/2eb176/proposed.md b/content/rules/2eb176/proposed.md index 3bb58ed26..a02634ef6 100644 --- a/content/rules/2eb176/proposed.md +++ b/content/rules/2eb176/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

Rule Identifier: 2eb176

-

Date: Updated 8 July 2025

+

Date: Updated 6 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: 6 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 +## Examples
These HTML files are used in several examples: diff --git a/content/rules/2ee8b8/proposed.md b/content/rules/2ee8b8/proposed.md index c04f44030..ebc17d847 100644 --- a/content/rules/2ee8b8/proposed.md +++ b/content/rules/2ee8b8/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

Rule Identifier: 2ee8b8

-

Date: Updated 8 July 2025

+

Date: Updated 6 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: 6 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 diff --git a/content/rules/2t702h/proposed.md b/content/rules/2t702h/proposed.md index 7cf3b1bbb..e97c0c529 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 6 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: 6 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 diff --git a/content/rules/307n5z/proposed.md b/content/rules/307n5z/proposed.md index 2deb4a878..455354683 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 6 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: 6 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 ` @@ -185,7 +185,7 @@ This element with the `menuitemcheckbox` role has a checkbox as a child. Because Open in a new tab -This element with the `tab` role contains an `a` element. The `tab` role has [presentational children][]. The `a` element is included in [sequential focus navigation][]. So the element with the `tab` role fails the rule. (This tablist implementation is non-functional for users. It's not meant to function - it's only meant to show roles.) +This element with the `tab` role contains an `a` element. The `tab` role has [presentational children][]. The `a` element is included in [sequential focus navigation][]. So the element with the `tab` role fails the rule. (This tablist implementation is non-functional for users. It's not meant to function - it's only meant to show roles.) ```html
    @@ -199,7 +199,7 @@ This element with the `tab` role contains an `a` element. The `tab` role has [p Open in a new tab -This element with the `img` role contains an `a` element. The `img` role has [presentational children][]. The `a` element is included in [sequential focus navigation][]. So the element with the `img` role fails the rule. +This element with the `img` role contains an `a` element. The `img` role has [presentational children][]. The `a` element is included in [sequential focus navigation][]. So the element with the `img` role fails the rule. ```html ****** This ASCII art ******* contains a link. @@ -211,7 +211,7 @@ This element with the `img` role contains an `a` element. The `img` role has [p Open in a new tab -None of the roles that build this semantic table structure (`table` for `table`, `row` for `tr`, `columnheader` for `th`, and `cell` for `td`) have [presentational children][]. So this rule does not apply to them. +None of the roles that build this semantic table structure (`table` for `table`, `row` for `tr`, `columnheader` for `th`, and `cell` for `td`) have [presentational children][]. So this rule does not apply to them. ```html @@ -232,7 +232,7 @@ None of the roles that build this semantic table structure (`table` for `table`, Open in a new tab -This `a` element has a `link` role, which does not have [presentational children][]. So this `a` element does not fail this rule, because it's inapplicable. To have a "focusable element within a focusable element" like this is a bad practice, but this rule doesn't directly check for it. +This `a` element has a `link` role, which does not have [presentational children][]. So this `a` element does not fail this rule, because it's inapplicable. To have a "focusable element within a focusable element" like this is a bad practice, but this rule doesn't directly check for it. ```html W3C Website diff --git a/content/rules/36b590/proposed.md b/content/rules/36b590/proposed.md index d18985d1b..1c35ff896 100644 --- a/content/rules/36b590/proposed.md +++ b/content/rules/36b590/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

    Rule Identifier: 36b590

    -

    Date: Updated 8 July 2025

    +

    Date: Updated 6 October 2025

    Authors: Carlos Duarte, João Vicente, 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: invalid-form-field-value-36b590.md description: | This rule checks that text error messages provided when the user completes a form field with invalid values or using an invalid format, identify the cause of the error or how to fix the error. - last_modified: 8 July 2025 + last_modified: 6 October 2025 scs_tested: - handle: Error Identification num: 3.3.1 @@ -86,7 +86,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [Understanding Success Criterion 3.3.1: Error Identification](https://www.w3.org/WAI/WCAG22/Understanding/error-identification) - [G84: Providing a text description when the user provides information that is not in the list of allowed values](https://www.w3.org/WAI/WCAG22/Techniques/general/G84) @@ -117,7 +117,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/3e12e1/proposed.md b/content/rules/3e12e1/proposed.md index 40ed1f92e..c5ad7aedb 100644 --- a/content/rules/3e12e1/proposed.md +++ b/content/rules/3e12e1/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

    Rule Identifier: 3e12e1

    -

    Date: Updated 8 July 2025

    +

    Date: Updated 6 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: block-collapsible-3e12e1.md description: | This rule checks that repeated blocks of content are collapsible - last_modified: 8 July 2025 + last_modified: 6 October 2025 --- ## Applicability @@ -48,7 +48,7 @@ Usually the same [instrument][] removes both [visibility][visible] and [inclusio There are no accessibility support issues known. -### Bibliography +### Other Resources - [Technique SCR28: Using an expandable and collapsible menu to bypass block of content][tech scr28] @@ -77,7 +77,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 +## Examples
    These HTML, Javascript, and CSS files are used in several examples: diff --git a/content/rules/3ea0c8/proposed.md b/content/rules/3ea0c8/proposed.md index 81514868f..082760e37 100644 --- a/content/rules/3ea0c8/proposed.md +++ b/content/rules/3ea0c8/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

    Rule Identifier: 3ea0c8

    -

    Date: Updated 8 July 2025

    +

    Date: Updated 6 October 2025

    Authors: Anne Thyme Nørregaard, Bryn Anderson. 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 @@ -25,7 +25,7 @@ rule_meta: original_file: id-value-unique-3ea0c8.md description: | This rule checks that all `id` attribute values on a single page are unique. - last_modified: 8 July 2025 + last_modified: 6 October 2025 scs_tested: - handle: Parsing num: 4.1.1 @@ -52,7 +52,7 @@ There are no assumptions. There are no accessibility support issues known. -### Bibliography +### Other Resources - [Understanding Success Criterion 4.1.1: Parsing](https://www.w3.org/WAI/WCAG22/Understanding/parsing) - [H93: Ensuring that id attributes are unique on a Web page](https://www.w3.org/WAI/WCAG22/Techniques/html/H93) @@ -92,7 +92,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 +## Examples ### Passed diff --git a/content/rules/46ca7f/proposed.md b/content/rules/46ca7f/proposed.md index 7ddc57b57..44c3607c9 100644 --- a/content/rules/46ca7f/proposed.md +++ b/content/rules/46ca7f/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

    Rule Identifier: 46ca7f

    -

    Date: Updated 8 July 2025

    +

    Date: Updated 6 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: element-marked-decorative-is-not-exposed-46ca7f.md description: | This rule checks that elements marked as decorative either are not included in the accessibility tree, or have a presentational role. - last_modified: 8 July 2025 + last_modified: 6 October 2025 --- ## Applicability @@ -67,7 +67,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 +## Examples ### Passed diff --git a/content/rules/4b1c6c/proposed.md b/content/rules/4b1c6c/proposed.md index ca60404d1..dbfb8e50c 100644 --- a/content/rules/4b1c6c/proposed.md +++ b/content/rules/4b1c6c/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

    Rule Identifier: 4b1c6c

    -

    Date: Updated 8 July 2025

    +

    Date: Updated 6 October 2025

    Authors: Audrey Maniez, Jean-Yves Moyen, 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: iframe-identical-name-equivalent-purpose-4b1c6c.md description: | This rule checks that `iframe` elements with identical accessible names embed the same resource or equivalent resources. - last_modified: 8 July 2025 + last_modified: 6 October 2025 scs_tested: - handle: Name, Role, Value num: 4.1.2 @@ -51,7 +51,7 @@ This rule assumes that, within the context of the test subject, the description This rule assumes that assistive technologies are exposing all `iframe` elements on the page in the same way no matter which [document tree](https://dom.spec.whatwg.org/#document-trees) they are in. If an assistive technology requires the user to "enter" an `iframe` or a [shadow tree][] before exposing its content (notably nested `iframe`), then it is possible for two `iframe` to have identical name but embed different resources without failing [Success Criterion 4.1.2: Name, Role, Value][sc412] (if said `iframe` are in separate [documents][document] or [shadow trees][shadow tree]) -### Bibliography +### Other Resources - [CSS Scoping Module Level 1 (editor's draft)](https://drafts.csswg.org/css-scoping/) - [H64: Using the title attribute of the frame and iframe elements](https://www.w3.org/WAI/WCAG22/Techniques/html/H64) @@ -82,7 +82,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
    These HTML files are used in several examples: diff --git a/content/rules/4c31df/proposed.md b/content/rules/4c31df/proposed.md index c53858fdb..1d3b2afbf 100644 --- a/content/rules/4c31df/proposed.md +++ b/content/rules/4c31df/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

    Rule Identifier: 4c31df

    -

    Date: Updated 8 July 2025

    +

    Date: Updated 6 October 2025

    Authors: Anne Thyme Nørregaard, Bryn Anderson. 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: auto-play-audio-has-control-mechanism-4c31df.md description: | audio or video that plays automatically must have a control mechanism. - last_modified: 8 July 2025 + last_modified: 6 October 2025 --- ## Applicability @@ -52,7 +52,7 @@ There are no assumptions. The native `video` and `audio` controls in several browser and assistive technology combinations are not keyboard accessible and the `video` or `audio` element itself may not be announced. Authors are recommended to use custom controls for keyboard navigation and cross browser accessibility support in general. -### Bibliography +### Other Resources - [Understanding Success Criterion 1.4.2: Audio Control](https://www.w3.org/WAI/WCAG22/Understanding/audio-control.html) - [Failure of Success Criterion 1.4.2 for absence of a way to pause or stop an HTML5 media element that autoplays](https://www.w3.org/WAI/WCAG22/Techniques/failures/F93) @@ -84,7 +84,7 @@ The following aspects are required in using this rule. - [Audio output](https://www.w3.org/TR/act-rules-aspects/#input-aspects-audio-out) - Visual output (no link available) -## Test Cases +## Examples
    This Javascript file is used in several examples: diff --git a/content/rules/4e8ab6/proposed.md b/content/rules/4e8ab6/proposed.md index 7f0f684cd..a5079bb87 100644 --- a/content/rules/4e8ab6/proposed.md +++ b/content/rules/4e8ab6/proposed.md @@ -9,7 +9,7 @@ github: feedbackmail: public-wcag-act@w3.org footer: |

    Rule Identifier: 4e8ab6

    -

    Date: Updated 8 July 2025

    +

    Date: Updated 6 October 2025

    Authors: Anne Thyme Nørregaard, Tom Brunet. 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: role-required-states-and-properties-4e8ab6.md description: | This rule checks that elements that have an explicit role also specify all required states and properties. - last_modified: 8 July 2025 + last_modified: 6 October 2025 --- ## Applicability @@ -47,7 +47,7 @@ This rule relies on browsers and assistive technologies to support leaving out [ **Note:** The required states and properties with implicit values can be found in the Core Accessibility API Mappings 1.1 [Overview of default values for missing required attributes](https://www.w3.org/TR/core-aam-1.1/#authorErrorDefaultValuesTable). -### Bibliography +### Other Resources - [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA5) - [WAI-ARIA required states and properties](https://www.w3.org/TR/wai-aria-1.2/#requiredState) @@ -99,7 +99,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 +## Examples ### Passed @@ -165,13 +165,13 @@ This `separator` is not a `widget` because it is not [focusable][]. The `separat #### Passed Example 6 -Open in a new tab +Open in a new tab This `combobox` has the required properties `aria-controls` and `aria-expanded`. ```html - +