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

Clarification on aria-haspopup and aria-expanded Attributes #2808

Closed
AccessibilityEnthusiastic opened this issue Sep 20, 2023 · 3 comments
Closed

Comments

@AccessibilityEnthusiastic

I am reaching out to seek clarification on the usage of the aria-haspopup attribute in combination with the aria-expanded attribute.

My specific question pertains to whether it is still necessary to include the aria-expanded attribute with a value of "false" in the default state of the element when aria-haspopup is used. To provide some context, I am wondering if the presence of aria-haspopup alone adequately conveys the intended user interaction, or if aria-expanded must be used.

With aria-haspopup indicating the presence of a popup and aria-expanded providing its state (open or closed). However, I'm seeking clarification on whether aria-expanded with a default value of "false" is redundant when aria-haspopup is present.

@mcking65
Copy link
Contributor

mcking65 commented Oct 2, 2023

@AccessibilityEnthusiastic wrote:

I am reaching out to seek clarification on the usage of the aria-haspopup attribute in combination with the aria-expanded attribute.

My specific question pertains to whether it is still necessary to include the aria-expanded attribute with a value of "false" in the default state of the element when aria-haspopup is used.

We have some precedent for considering it optional. However, people have found this confusing and potentially problematic for users. See #697.

To provide some context, I am wondering if the presence of aria-haspopup alone adequately conveys the intended user interaction, or if aria-expanded must be used.

Problems arise for users of touch-based screen readers. If aria-expanded is not set, then it may not be clear to users whether a menubutton is expanded or collapsed. By consistently specifying both states, the user can easily determine which button will close a currently expanded menu and which buttons will not.

With aria-haspopup indicating the presence of a popup and aria-expanded providing its state (open or closed). However, I'm seeking clarification on whether aria-expanded with a default value of "false" is redundant when aria-haspopup is present.

Net: experience is telling us aria--expanded=false is not redundant when aria-haspopup is true.

I'm closing this issue, but please feel free to re-open if you believe the issue deserves more discussion.

I'm also going to resurrect work on #697.

@mcking65
Copy link
Contributor

mcking65 commented Oct 3, 2023

@AccessibilityEnthusiastic, as a follow up, the task force has decided to move forward with #2829 and update the 3 menu button examples accordingly.

@mcking65
Copy link
Contributor

Change to be published on December 19, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants