Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with "<summary>": Does it really have an implicit role of button? #13763

Closed
alattalatta opened this issue Mar 11, 2022 · 4 comments
Closed
Assignees
Labels
closed: wontfix Out of scope, too much effort, or working as intended Content:Accessibility Accessibility docs

Comments

@alattalatta
Copy link
Member

MDN URL: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary

What information was incorrect, unhelpful, or incomplete?

Warning: Because the <summary> element has a default role of button (which strips all roles from child elements)...

Specific section or headline?

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/summary#summaries_as_headings

What did you expect to see?

In HTML Accessibility API Mappings 1.0, there's no default role for <summary>, i.e. "No corresponding role". So, no such note at all.

"Implicit ARIA role" should be changed as well.

Did you test this? If so, how?

In both Chrome and Firefox's a11y tree, the heading's heading role is preserved.

MDN Content page report details
@github-actions github-actions bot added the needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. label Mar 11, 2022
@sideshowbarker
Copy link
Collaborator

I think the https://w3c.github.io/html-aria/ spec is what normatively defines the implicit semantics for HTML elements. Anyway, at https://w3c.github.io/html-aria/#el-summary that spec at least does give role=button as the implicit semantics for summary.

Not sure what the AAM and ARIA in HTML specs are out of sync on this. @scottaohara and @stevefaulkner could speak to that.

@sideshowbarker sideshowbarker added needs info Needs more information to review or act on. and removed needs triage Triage needed by staff and/or partners. Automatically applied when an issue is opened. labels Mar 11, 2022
@scottaohara
Copy link
Contributor

it's "mostly" button at the platform api level. it ranges from being exposed as a "button", "disclosure triangle", "summary" and no role depending on the browser/AT used.

Honestly, it's messy and it needs to be fixed. Here are just three issues about it (there are more):

w3c/html-aria#355
whatwg/html#2272
w3c/html-aam#345

was having a bit of discussion about this in the aria wg for awhile. need to pick it back up again sometime... but need to hammer down some proposals of what to do, cause something will have to change.

@sideshowbarker sideshowbarker added Content:Accessibility Accessibility docs and removed needs info Needs more information to review or act on. labels Mar 11, 2022
@estelle estelle self-assigned this Apr 8, 2022
@estelle
Copy link
Member

estelle commented Apr 8, 2022

https://w3c.github.io/html-aria/#el-summary specifies that the implicit role for summary is button.

@estelle estelle added the closed: wontfix Out of scope, too much effort, or working as intended label Apr 8, 2022
@estelle
Copy link
Member

estelle commented Apr 8, 2022

i assume at some point the role will switch to a new "summary" role, but until that point, we should not update the content. Closing.

@estelle estelle closed this as completed Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: wontfix Out of scope, too much effort, or working as intended Content:Accessibility Accessibility docs
Projects
None yet
Development

No branches or pull requests

4 participants