[go: nahoru, domu]

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.

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

Open
cookiecrook opened this issue Dec 16, 2021 · 8 comments
Open

associationlist and related roles have tediously long names #1662

cookiecrook opened this issue Dec 16, 2021 · 8 comments
Assignees
Labels
feature may add new concept(s) to ARIA which will require implementations or APG changes
Projects
Milestone

Comments

@cookiecrook
Copy link
Contributor
cookiecrook commented Dec 16, 2021

associationlist and related roles have tediously long names. These look like ObjC naming conventions: associationlist:item:value: ;-)

associationlist: A section containing associationlistitemkey and associationlistitemvalue elements.
associationlistitemkey: A single key item in an association list.
associationlistitemvalue: A single value item in an association list.

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:

  1. Remove associationlist entirely. I don't think there needs to be any distinction between list and associationlist in the Accessibility APIs.
  2. listitemkey and listitemvalue may be sufficient. It's possible listitemvalue could be an alias of listitem… 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)
@pkra
Copy link
Member
pkra commented Dec 16, 2021

Related: #961

@jnurthen jnurthen added this to the ARIA 1.3 milestone Dec 16, 2021
@smhigley
Copy link
Contributor

+1 to the first option

@brennanyoung
Copy link
Contributor
brennanyoung commented Feb 1, 2022

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).

@pkra
Copy link
Member
pkra commented Apr 28, 2022

I'm in favor of the OP.

I have a slight preference for keeping listitemvalue (or whatever name we come up with) separate from listitem because of the different (possible) structure of 1 DT followed by multiple DDs.

@jnurthen jnurthen self-assigned this May 5, 2022
@jnurthen jnurthen removed the Agenda label May 5, 2022
@scottaohara
Copy link
Member

@jnurthen going to add myself here as a second assignee. we can discuss / i can do the associated HTML AAM stuffs.

@scottaohara scottaohara self-assigned this May 5, 2022
@spectranaut spectranaut added this to James Nurthen in ARIA 1.3 Jun 7, 2022
@scottaohara scottaohara added the feature may add new concept(s) to ARIA which will require implementations or APG changes label Jul 1, 2022
@jnurthen
Copy link
Member

Lets discuss 3 options:

  • remove assocaitionlists from 1.3 - what problem do they solve?
  • keep as-is
  • change the names and make them shorter

@cookiecrook
Copy link
Contributor Author
cookiecrook commented Oct 16, 2023

+1 for removing association lists [entirely]

@jnurthen
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature may add new concept(s) to ARIA which will require implementations or APG changes
Projects
ARIA 1.3
James Nurthen
Development

Successfully merging a pull request may close this issue.

7 participants