Correction for HTML element role mapping #550
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
per w3c/aria#2504 - the html element doesn't actually map to the `document` role - rather a parent `document node` to the `html` element is what exposes the `document` role of a web page. This update fixes the spec to match the updated HTML aam mapping / matches reality. The `generic` role is being added as an "allowed" but not recommended role to the `html` element. The `document` role is being kept as an allowed role for the `html` element. The rational there being that this has been in the spec for a long time and even when specified on the html element, from what i can tell, there's no pro/con to its inclusion.
scottaohara
added
HTML AAM Related
pkra
approved these changes
Apr 2, 2025
|
this will merge after w3c/aria#2504 is accepted |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
per w3c/aria#2504 - the html element doesn't actually map to the
documentrole - rather a parentdocument nodeto thehtmlelement is what exposes thedocumentrole of a web page.This update fixes the spec to match the updated HTML aam mapping / matches reality.
The
genericrole is being added as an "allowed" but not recommended role to thehtmlelement. Thedocumentrole is being kept as an allowed role for thehtmlelement. The rational there being that this has been in the spec for a long time and even when specified on the html element, from what i can tell, there's no pro/con to its inclusion.Preview | Diff