Skip to content

associationlist and related roles have tediously long names #1662

Open

Description

@cookiecrook

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)

Activity

  1. pkra commented on Dec 16, 2021

    @pkra
    Member

    Related: #961

  2. added this to the ARIA 1.3 milestone on Dec 16, 2021
  3. smhigley commented on Dec 16, 2021

    @smhigley
    Contributor

    +1 to the first option

  4. medeaoblongata commented on Feb 1, 2022

    @medeaoblongata
    Contributor

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

  5. pkra commented on Apr 28, 2022

    @pkra
    Member

    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.

  6. self-assigned this
    on May 5, 2022
  7. scottaohara commented on May 5, 2022

    @scottaohara
    Member

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

  8. self-assigned this
    on May 5, 2022
  9. added a commit that references this issue on May 11, 2022
    fda6c4c
  10. added
    featuremay add new concept(s) to ARIA which will require implementations or APG changes
    on Jul 1, 2022
  11. jnurthen commented on Oct 10, 2023

    @jnurthen
    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
  12. cookiecrook commented on Oct 16, 2023

    @cookiecrook
    ContributorAuthor

    +1 for removing association lists [entirely]

  13. jnurthen commented on Oct 26, 2023

    @jnurthen
    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

  14. cookiecrook commented on Aug 15, 2024

    @cookiecrook
    ContributorAuthor

    @aleventhal discovered we have some leftover expectations related to this, including invalid computedrole and invalid name-prohibited computedlabel tests

  15. zcorpan commented on Sep 24, 2026

    @zcorpan
    Contributor

    The current term and definition roles used for dt and dd in html-aam are incorrect per HTML's defined semantics, so it would be good to update them to something else. (See w3c/html-aam#347)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

featuremay add new concept(s) to ARIA which will require implementations or APG changes

Type

No type

Projects

  • Status
    James Nurthen

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions