[html-aam PR 484] contextual role concept proposal #2218
Conversation
This file contains 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
closes #375 The purpose of this proposal is both to resolve the issue that "scoped" was an undefined term that was used to indicate when certain elements would expose particular ARIA roles or not. However, in the year of noodling on this, other activities to revise what "owned" means in ARIA, the idea of a minimum role, as well as the fact there were other elements in HTML that have "scoped" or "contextual roles" that are based on heuristics, rather than defined standards, became relevant. A change to hopefully help simplify the implementations of contextual roles is that this proposal is aiming to tie the role of an element based on its a11y tree ancestry, rather than based on specific HTML elements in the DOM. This PR represents the initial draft of the proposal. Other work to explicitly call out the elements that have contextual roles, what roles they need to adjust to, and other wording revisions to replace "scoped" with the new term would still need to be made.
still working on the exact wording. also changing some placeholder short code so as to hopefully not get more build errors for presently undefined terms
Co-authored-by: James Craig <[email protected]>
Co-authored-by: James Craig <[email protected]>
use computed role in both sentences, rather than switching between terms
Co-authored-by: James Craig <[email protected]>
|
Strangely enough, this merged without conflict -- which makes me doubt the result. |
This position seems to match the original diff
|
@scottaohara I hope I moved the section to the correct position. |
21 tasks
pkra
changed the title
|
Re-adding reviewers @cookiecrook @spectranaut @aleventhal and myself. |
spectranaut
requested changes
Aug 13, 2024
| list item (`li` element) within an unordered list (`ul` element). However, the same element might be used within a different markup pattern and could therefore expose different | ||
| contextually-dependent computed roles, such as a `section` element with an author-provided accessible name (role `region`) versus an unnamed `section` element (role `generic`). | ||
| </p> | ||
| <p>When the conditions for an element's contextual role are not met, it will commonly expose a computed role of `generic` or with a <strong>minimum role</strong>, if applicable.</p> |
There was a problem hiding this comment.
Suggested change
| <p>When the conditions for an element's contextual role are not met, it will commonly expose a computed role of `generic` or with a <strong>minimum role</strong>, if applicable.</p> | |
| <p>When the conditions for an element's contextual role are not met, it will commonly be exposed with a computed role of `generic` or with a <strong>minimum role</strong>, if applicable.</p> |
Grammar ^
| <article> | ||
| ... | ||
| <li>...</li> <!-- computed role `generic`, not `listitem` --> | ||
| ...</code></pre> |
There was a problem hiding this comment.
Maybe we should use a different example than listitem, here and above, given the push back on the orphan roles tests which is partially being discussed here: #2166
But started with the roll back of orphan <li> tests in WPT.
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.
Moved from w3c/html-aam#484