-
Notifications
You must be signed in to change notification settings - Fork 126
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
CORE-AAM: term role mappings restrict use to list item #455
Comments
Thanks @jasonkiss. As you can see, I've opened issues #617 and #618 for UIA and MSAA/IA2 respectively since we need input from each platform. And a given platform may decide to punt for now, pending better platform roles being added to their API. |
It's no longer a listitem for IA2. At this point, UIA is the only platform which has a listitem mapping. |
Closing this as a duplicate of #617 and #618. As a result of those issues being fixed, https://w3c.github.io/aria/core-aam/core-aam.html#role-map-term no longer has any list-item-related mappings. |
* add allowed role for aside element - related to, w3c/html-aria#411 but does not resolve the issue. * update change log
Just want to confirm that the CORE-AAM mappings for role="term" are intended to restrict it to list items as patterned by the
dt
element in HTML.The ARIA 1.1 descriptions of the term role and the definition role are more general, and don't imply, at least to me, their restriction to a list structure.
I'm looking at this because I was thinking/hoping that the mappings for the term role might make it a good match for the
dfn
element, which is described as "the defining instance of a term". That seems to overlap with the description of the term role as "a word or phrase with a corresponding definition".If the current CORE-AAM mappings for the term role are as intended, then the description of the term role (and the definition role?) needs to be narrowed in the ARIA spec. Otherwise, any use of the term role around a word or phrase with a definition will pick up list item semantics, which won't be appropriate in all sorts of cases.
The text was updated successfully, but these errors were encountered: