-
Notifications
You must be signed in to change notification settings - Fork 23
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
Accordion and Detail: When expanded the body content isn't read by screen readers #1868
Comments
🎉 This issue has been resolved in version 1.17.0-alpha.65 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 1.21.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 4.21.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 4.17.0-alpha.31 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.0.0-alpha.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 3.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Info
A screen reader will happily read the
heading
property and anything in theheadingcontent
slot. It will also read the status of the accordion, open or closed. However, when an Accordion is opened, the body content is not read at all.Acceptance Criteria:
More Info
Current working theory is to apply
aria-expanded
to the contentdiv
and set it to true or false based on the open and closed state.The text was updated successfully, but these errors were encountered: