-
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
associationlist and related roles have tediously long names #1662
Comments
Related: #961 |
+1 to the first option |
It would simplify matters to permit the key/value roles inside list, whatever they may be called. (I agree the currently suggested names are too long). What happens if people use key & value elements and plain listitem elements in the same list? Is that a problem? If this is about parity with HTML, it should not be allowed, but I can imagine cases where it would be useful to do so. (e.g. if there is a placeholder listitem for an as-yet-unknown key-value pair). |
I'm in favor of the OP. I have a slight preference for keeping |
@jnurthen going to add myself here as a second assignee. we can discuss / i can do the associated HTML AAM stuffs. |
Lets discuss 3 options:
|
+1 for removing association lists [entirely] |
As discussed in https://www.w3.org/2023/10/26-aria-minutes.html#t07 will remove for now but may re-add a subset later on |
@aleventhal discovered we have some leftover expectations related to this, including invalid computedrole and invalid name-prohibited computedlabel tests |
associationlist
and related roles have tediously long names. These look like ObjC naming conventions:associationlist:item:value:
;-)I don't have a particular preference other than "not what's there" but in the interest of forwarding the discussion, I'd suggest the following:
associationlist
entirely. I don't think there needs to be any distinction betweenlist
andassociationlist
in the Accessibility APIs.listitemkey
andlistitemvalue
may be sufficient. It's possiblelistitemvalue
could be an alias oflistitem
… I'm not certain, but the existence of a key may be all that's needed to distinguish between standard lists (~html:ol/html:ul
) and these (~html:dl
)The text was updated successfully, but these errors were encountered: