From 1346e2231358d6275816f18ed8c7411e8eb14e77 Mon Sep 17 00:00:00 2001 From: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> Date: Mon, 13 Jul 2026 11:51:01 +0200 Subject: [PATCH 1/5] Remove redundant "so this fails the rule". --- _rules/visible-label-in-accessible-name-2ee8b8.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_rules/visible-label-in-accessible-name-2ee8b8.md b/_rules/visible-label-in-accessible-name-2ee8b8.md index 2a0c11338c..f7025334c9 100755 --- a/_rules/visible-label-in-accessible-name-2ee8b8.md +++ b/_rules/visible-label-in-accessible-name-2ee8b8.md @@ -254,7 +254,7 @@ This button has [visible inner text][] that is only partially contained within t #### Failed Example 3 -This button has [visible inner text][] that is fully contained within the [accessible name][] when viewed as a character-by-character substring. But that does not satisfy the [label in name algorithm][], which works on full words. So this fails the rule. +This button has [visible inner text][] that is fully contained within the [accessible name][] when viewed as a character-by-character substring. But that does not satisfy the [label in name algorithm][], which works on full words. ```html Discover It @@ -310,7 +310,7 @@ This button's accessible name contains the word "the" in the middle of it, which #### Failed Example 10 -This link's accessible name contains the same digits that are in the visible label, and in the same order. But they have different spaces and punctuation between them, so they are considered separate tokens. So this fails the rule. +This link's accessible name contains the same digits that are in the visible label, and in the same order. But they have different spaces and punctuation between them, so they are considered separate tokens. ```html 123.555.0123 From 7b865fe81110ecb7e122ec81064ef83f21732796 Mon Sep 17 00:00:00 2001 From: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com> Date: Mon, 13 Jul 2026 12:05:04 +0200 Subject: [PATCH 2/5] More polishing of example descriptions --- _rules/visible-label-in-accessible-name-2ee8b8.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/_rules/visible-label-in-accessible-name-2ee8b8.md b/_rules/visible-label-in-accessible-name-2ee8b8.md index f7025334c9..1523a5bbf4 100755 --- a/_rules/visible-label-in-accessible-name-2ee8b8.md +++ b/_rules/visible-label-in-accessible-name-2ee8b8.md @@ -262,7 +262,7 @@ This button has [visible inner text][] that is fully contained within the [acces #### Failed Example 4 -This link's [accessible name][] contains two tokens (according to the[label in name algorithm][]) and the [visible inner text][] contains one token. So it fails the rule. +This link's [accessible name][] contains two tokens (according to the[label in name algorithm][]) and the [visible inner text][] contains one token. ```html justice @@ -294,7 +294,7 @@ This rule has no special handling for converting mathematical symbols into words #### Failed Example 8 -This button's accessible name contains the same tokens that are in the visible label. But they aren't in the same order, so it fails the [contiguous subsequence][] check part of the [label in name algorithm][], and so it fails the rule. +This button's accessible name contains the same tokens that are in the visible label. But they aren't in the same order, so it fails the [contiguous subsequence][] check part of the [label in name algorithm][]. ```html @@ -302,7 +302,7 @@ This button's accessible name contains the same tokens that are in the visible l #### Failed Example 9 -This button's accessible name contains the word "the" in the middle of it, which causes the [contiguous subsequence][] check of the [label in name algorithm][] (in particular: the "contiguous" requirement) to fail. So it fails the rule. +This button's accessible name contains the word "the" in the middle of it, which causes the [contiguous subsequence][] check of the [label in name algorithm][] (in particular: the "contiguous" requirement) to fail. ```html @@ -350,7 +350,7 @@ This rule has no special handling for converting digits into words, or vice vers #### Failed Example 15 -The [label in name algorithm][] works on full words. That is: it requires that each full word in the visible label ("1" in this case) is equal to a full word in the accessible name ("1a" in this case). Those two words - "1" and "1a" - are not equal, so this element fails the rule. +The [label in name algorithm][] works on full words. That is: it requires that each full word in the visible label ("1" in this case) is equal to a full word in the accessible name ("1a" in this case). Those two words - "1" and "1a" - are not equal. ```html 1 @@ -358,7 +358,7 @@ The [label in name algorithm][] works on full words. That is: it requires that e #### Failed Example 16 -The definition of [visible inner text][] doesn't treat text any differently if it's excluded from the accessibility tree with aria-hidden. So this rule effectively ignores aria-hidden. So this element fails the rule. +The definition of [visible inner text][] doesn't treat text any differently if it's excluded from the accessibility tree with aria-hidden. This rule effectively ignores aria-hidden. ```html Download specification @@ -403,7 +403,7 @@ This link has no [visible text content][]. #### Inapplicable Example 5 -This link's label contains an abbreviation, so it is not applicable. +This link's label contains an abbreviation. ```html University Ave. @@ -411,7 +411,7 @@ This link's label contains an abbreviation, so it is not applicable. #### Inapplicable Example 6 -This word - non-standard / nonstandard - appears in both the element's accessible name and its visible label, using different hyphenation. So it's not applicable. +This word - non-standard / nonstandard - appears in both the element's accessible name and its visible label, using different hyphenation. ```html nonstandard From af9c1e23bb112ae73d1e0d05f373044208b6cbbe Mon Sep 17 00:00:00 2001 From: Daniel Date: Mon, 13 Jul 2026 13:56:04 +0200 Subject: [PATCH 3/5] Another instance --- .../presentational-children-no-focusable-content-307n5z.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_rules/presentational-children-no-focusable-content-307n5z.md b/_rules/presentational-children-no-focusable-content-307n5z.md index 6c2d285c77..868ed38857 100755 --- a/_rules/presentational-children-no-focusable-content-307n5z.md +++ b/_rules/presentational-children-no-focusable-content-307n5z.md @@ -97,7 +97,7 @@ This element with the `menuitemcheckbox` role has an `input` element as a descen #### Passed Example 4 -This ` @@ -139,7 +139,7 @@ This element with the `menuitemcheckbox` role has a checkbox as a child. Because #### Failed Example 4 -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][]. (This tablist implementation is non-functional for users. It's not meant to function - it's only meant to show roles.) ```html