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.

Sign up for GitHub

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

Jump to bottom

Update guidance for aria-level when html-aam#123 (hgroup) is fixed #1157

Open
zcorpan opened this issue Aug 30, 2019 · 0 comments
Open

Update guidance for aria-level when html-aam#123 (hgroup) is fixed #1157

zcorpan opened this issue Aug 30, 2019 · 0 comments

Comments

@zcorpan
Copy link
Member

zcorpan commented Aug 30, 2019

This issue depends on w3c/html-aam#123 (Change mapping of h1-h6 and hgroup)

When that issue is fixed, check if the aria-level section (introduced by #1109) needs to be updated.
@zcorpan zcorpan mentioned this issue Aug 30, 2019
Open
@JAWS-test JAWS-test mentioned this issue Jan 22, 2020
Closed
scottaohara added a commit to w3c/html-aam that referenced this issue Apr 28, 2022
@scottaohara
indicate what to do with multiple headings in hgroup
a570e0f 
Related to whatwg/html#7829.

Assuming this PR lands, an `hgroup` will only allow a single heading and paragraph elements <small>(and script-supporting elements, but that's not relevant here)</small> to represent sub-heading information.

However, as there are _lots_ of instances of `hgroup` in the wild where multiple headings are used - as this was allowed prior to the HTML PR, these will become invalid markup patterns, and indicating that the headings of lower level be treated as `p` elements will at least mitigate for this change.

For additional discussion:
- should `hgroup` be exposed as a 'heading group' or even just a 'group' to define the boundaries of where the hgroup content starts/stops
- should `p` elements or errant extra `h#` elements be exposed as 'sub headings'.  `doc-subtitle` could potentially be used - though I'm not sure if that is actually appropriate, as we _don't_ want the subheadings to be exposed as 'headings' as some of the mappings for `doc-subtitle` would seem to indicate might be the result of mapping to this role.  This could potentially be related to what dpub ARIA roles should be brought back into ARIA proper - e.g., `role=subheading` 

this effectively resolves #123
this may well help resolving w3c/aria-practices#1157
@scottaohara scottaohara mentioned this issue Apr 28, 2022
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zcorpan