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

Consider adding a 'header' and 'footer' role #1915

Open
scottaohara opened this issue Apr 11, 2023 · 5 comments · May be fixed by #1931
Open

Consider adding a 'header' and 'footer' role #1915

scottaohara opened this issue Apr 11, 2023 · 5 comments · May be fixed by #1931
Assignees
Milestone

Comments

@scottaohara
Copy link
Member

scottaohara commented Apr 11, 2023

A similar topic came up when we had been discussing hgroup and what that could map to (just a group right now), but in working on other updates to the HTML AAM spec today, I thought I'd check the temperature of the working group for roles like these. Especially since the header and footer elements are only exposed as landmarks under certain conditions, and the rest of the time these "semantic" HTML elements are no different than div elements.

Could it not be potentially beneficial to allow AT to expose something beyond a generic or group role for these elements, even if we put a stipulation that the role only be overtly exposed to the user if provided an accessible name?

Note that there are potentially similar existing roles with dpub doc-pageheader and doc-pagefooter

Edit: I should have mentioned that I am aware this is retreading an older issue - #963 - but as that was closed in 2019 before the generic concept was implemented, and now we're also working on defining minimum role to combat generics not being useful, again, maybe we should think about if we should start thinking about rethinking this maybe?

@MarioBatusic
Copy link

I think, that these HTML elements have a clear semantics not only as direct children of body element but also e.g. in the article element. So why lose this semantic putting it to generic in the accessibility tree?

@spectranaut
Copy link
Contributor

This topic was discussed at todays meeting: https://www.w3.org/2023/04/20-aria-minutes#t04

But we realized we needed @scottaohara for it so we punted part way through :)

@cyns
Copy link
Contributor

cyns commented Apr 27, 2023

@domenic @mfreed7 do you have any concerns about this change to ARIA/HTML interaction?

@domenic
Copy link
Contributor

domenic commented Apr 28, 2023

No concerns from me! Please remember to send a PR updating the relevant "Accessibility considerations" links in HTML, which currently say e.g.

If there is an ancestor sectioning content element: for authors; for implementers.
Otherwise: for authors; for implementers.

@jnurthen
Copy link
Member

jnurthen commented May 9, 2023

@scottaohara scottaohara linked a pull request May 9, 2023 that will close this issue
9 tasks
@pkra pkra added this to the ARIA 1.3 milestone Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants