From 127e91ca059f95f4f9d13673250dd133ed179289 Mon Sep 17 00:00:00 2001 From: Sasha Nichols Date: Wed, 16 Apr 2025 16:27:14 -0500 Subject: [PATCH 1/2] summary name, element position clarified --- _rules/summary-non-empty-accessible-name-2t702h.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/summary-non-empty-accessible-name-2t702h.md b/_rules/summary-non-empty-accessible-name-2t702h.md index d0a24bb97f8..f72dc3d76cf 100755 --- a/_rules/summary-non-empty-accessible-name-2t702h.md +++ b/_rules/summary-non-empty-accessible-name-2t702h.md @@ -34,7 +34,7 @@ Each target element has an [accessible name][] that is not empty (`""`), nor jus ## Background -This rule is only applicable to `summary` elements that the browser will use as controls for a `details` element. While this rule is not applicable to `summary` elements with an [explicit role][], most of the time these likely do still require an [accessible name][]. This is covered by other rules, such as the [Button has non-empty accessible name][97a4e1]. +This rule is only applicable to `summary` elements that the browser will use as controls for a `details` element. Even though the [HTML specification - The summary element][https://html.spec.whatwg.org/#the-summary-element] requires the `summary` element to be the first child of `details`, this is not required for WCAG. And while this rule is not applicable to `summary` elements with an [explicit role][], most of the time these likely do still require an [accessible name][]. This is covered by other rules, such as the [Button has non-empty accessible name][97a4e1]. If the `summary` element is not included in the accessibility tree, but is still included in sequential focus navigation, this can result in accessibility issues not tested by this rule. This is covered under [Element with aria-hidden has no content in sequential focus navigation][6cfa84]. From 6d0e1ef43fab26efaa2f793b40a8ed400c835cab Mon Sep 17 00:00:00 2001 From: Sasha Nichols Date: Wed, 16 Apr 2025 16:40:07 -0500 Subject: [PATCH 2/2] fix link --- _rules/summary-non-empty-accessible-name-2t702h.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/summary-non-empty-accessible-name-2t702h.md b/_rules/summary-non-empty-accessible-name-2t702h.md index f72dc3d76cf..9eaf615cb45 100755 --- a/_rules/summary-non-empty-accessible-name-2t702h.md +++ b/_rules/summary-non-empty-accessible-name-2t702h.md @@ -34,7 +34,7 @@ Each target element has an [accessible name][] that is not empty (`""`), nor jus ## Background -This rule is only applicable to `summary` elements that the browser will use as controls for a `details` element. Even though the [HTML specification - The summary element][https://html.spec.whatwg.org/#the-summary-element] requires the `summary` element to be the first child of `details`, this is not required for WCAG. And while this rule is not applicable to `summary` elements with an [explicit role][], most of the time these likely do still require an [accessible name][]. This is covered by other rules, such as the [Button has non-empty accessible name][97a4e1]. +This rule is only applicable to `summary` elements that the browser will use as controls for a `details` element. Even though the [HTML specification - The summary element](https://html.spec.whatwg.org/#the-summary-element) requires the `summary` element to be the first child of `details`, this is not required for WCAG. And while this rule is not applicable to `summary` elements with an [explicit role][], most of the time these likely do still require an [accessible name][]. This is covered by other rules, such as the [Button has non-empty accessible name][97a4e1]. If the `summary` element is not included in the accessibility tree, but is still included in sequential focus navigation, this can result in accessibility issues not tested by this rule. This is covered under [Element with aria-hidden has no content in sequential focus navigation][6cfa84].