-
Notifications
You must be signed in to change notification settings - Fork 78
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
CalciteButton: aria-expanded not being read by screenreader #6033
Comments
Hello! Checking in to see if there are any updates on this bug? |
@phenderson00 Thanks for re-pinging this! This request seems to be more in line of an enhancement, but in line with the native We'll take a look at an upcoming milestone to determine next steps. cc @brittneytewks Some findings below during triage/next steps:
|
Installed and assigned for verification. |
Verified in |
Summary
Screenreader does not indicate to user that button is expandable despite aria-expanded being properly set on the
calcite-button
component.Actual Behavior
We are using a
calcite-popover
with acalcite-button
as its reference element. When the button gets focus, the button label and "button" are read by the screenreader but "expandable" is not read aloud. I can see in the Dev Tools that the aria-expanded state is being correctly updated on the button.Expected Behavior
The expectation is that after reading the button label and "button", the screenreader will read "expandable" (or something to that effect) to indicate to the user that clicking the button will reveal more content, a
calcite-popover
in this case.Reproduction Sample
https://codesandbox.io/s/calcite-button-aria-expanded-not-read-by-screenreader-oh4y6s?file=/src/App.js
Reproduction Steps
Reproduction Version
0.35.0
Working W3C Example/Tutorial
No response
Relevant Info
Windows 10, Chrome 108.0.5359.99, Narrator, JAWS
Regression?
No response
Esri team
Professional Services - Midwest Delivery Center
The text was updated successfully, but these errors were encountered: