Skip to content

Commit b4e371c

Browse files
authored
summary name, element position clarified (#2323)
* summary name, element position clarified * fix link
1 parent b0d82c7 commit b4e371c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

_rules/summary-non-empty-accessible-name-2t702h.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Each target element has an [accessible name][] that is not empty (`""`), nor jus
3434

3535
## Background
3636

37-
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].
37+
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].
3838

3939
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].
4040

0 commit comments

Comments
 (0)