Skip to content

Issues with aria-expanded on tabpanel/tablist/tab #1032

Closed

Description

@zcorpan

I found this when researching for writing a new section in aria-practices for Controlling Widget States.

Here are the issues me and @spectranaut found:

  • tabpanel - what is the advantage of using aria-expanded when aria-selected already indicates which tabs are selected?
  • The spec is inconsistent about whether aria-expanded should go on tabpanel, tablist, or tab.

For a multi-selectable tablist, authors SHOULD ensure each visible tabpanel has its aria-expanded attribute set to true, and that the remaining hidden tabpanel elements have their aria-expanded attributes set to false.

https://w3c.github.io/aria/#tab

For a multi-selectable tablist, authors SHOULD ensure each visible tabpanel has its aria-expanded attribute set to true, and that the remaining hidden tabpanel elements have their aria-expanded attributes set to false.

https://w3c.github.io/aria/#tablist

...but aria-expanded is a supported state on tab, not tabpanel or tablist

Originally posted by @zcorpan in #681 (comment)

Activity

  1. added this to the ARIA 1.3 milestone on Aug 15, 2019
  2. added
    F2FCandidateCandidate topics for F2F (or Virtual F2F) meeting
    and removed
    F2FCandidateCandidate topics for F2F (or Virtual F2F) meeting
    on Aug 15, 2019
  3. carmacleod commented on Feb 18, 2021

    @carmacleod
    Contributor

    This issue will be fixed by PR #1403.

    To answer the question:

    what is the advantage of using aria-expanded when aria-selected already indicates which tabs are selected?

    please see: w3c/aria-practices#341

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions