summary name, element position clarified#2323
Conversation
|
|
✅ Deploy Preview for act-rules ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
| ## 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]. |
There was a problem hiding this comment.
(1) WCAG can't override HTML 5; (2) per ARIA in HTML, a 'summary' element neither has an implicit nor explicit role; and (3) a "summary" represent a summary, caption, or legend for its parent "details" element, rather than "use as control for a 'details' element".
Suggest changing into: "This rule is only applicable to a summary element that is a child of a details element. An accessible name is required for a "summary" element because the details element are often presented by browsers as a disclosure widget from which the user can obtain additional information or controls.
There was a problem hiding this comment.
I don't really understand your point here. We're not testing HTML, or HTML in ARIA in this rule. I like Sasha's suggestion better.
| ## 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]. |
There was a problem hiding this comment.
I don't really understand your point here. We're not testing HTML, or HTML in ARIA in this rule. I like Sasha's suggestion better.
5 participants
Adds clarification on how the
summaryelement can be used since HTML specification requires thesummaryelement to be the first child ofdetails, while WCAG does not.This will not require a Call for Review : editorial changes to background
How to Review And Approve