Skip to content

selectedcontent element and other updates related to customizable select #2333

Open

Description

@scottaohara

The new customizable select updates have landed in the HTML specification, and with that landing ARIA in HTML is updating to account for the new selectedcontent element as well as a new rule for the button element when it is used as the button part to a customized select.

Essentially, when the selectedcontent element is correctly used as a child of the button part of a customizable select, then no ARIA roles or attributes can be used. Similarly, the button part of the customizable select also does not allow ARIA roles or attributes to be set.

However, if someone uses the selectedcontent element incorrectly outside of the context of the button part, then authors may correct for this misuse by specifying ARIA attributes without restriction, since in this invalid context it is merely a role=generic element.

A reduced test case was created to illustrate the updated rules.

Activity

  1. added
    user-reportedIssues identified outside of the core team
    engine-rulesIssues in the accessibility-checker-engine component
    on Jul 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Spec changeWhen specs/versions are updated or changeT71engine-rulesIssues in the accessibility-checker-engine componentuser-reportedIssues identified outside of the core team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions