You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ksparrow-8x8 opened this issue
Feb 17, 2023
· 1 comment
Assignees
Labels
duplicateAn issue closed because it is equivalent to another issueFeedbackIssue raised by or for collecting input from people outside APG task forcequestionIssue asking a question
The short answer is that omitting aria-expanded=false was intentional but the task force is reversing its previous guidance as described in the related issues. Since this is addressed by other issues, closing as duplicate.
mcking65
added
duplicate
An issue closed because it is equivalent to another issue
question
Issue asking a question
Feedback
Issue raised by or for collecting input from people outside APG task force
and removed
agenda
Include in upcoming Authoring Practices Task Force meeting
labels
Oct 10, 2023
duplicateAn issue closed because it is equivalent to another issueFeedbackIssue raised by or for collecting input from people outside APG task forcequestionIssue asking a question
As per Actions Menu Button Example Using element.focus():
The aria-expanded attribute is removed when the menu is closed.
MDN says that the default value for aria-expanded is undefined, which means "The element does not own or control a grouping element that is expandable." Shouldn't the Actions Menu Button always own the dropdown?
Is this a mistake? If not, what is the reasoning behind removing
aria-expanded
rather than usingaria-expanded="false"
?Thanks!
The text was updated successfully, but these errors were encountered: