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

[BUG]: Contents of Toast component are not announced in screen reader #3338

Open
2 tasks
o-hook opened this issue Jun 11, 2024 · 0 comments
Open
2 tasks

[BUG]: Contents of Toast component are not announced in screen reader #3338

o-hook opened this issue Jun 11, 2024 · 0 comments
Labels
a11y bug Something isn't working code component Adds or changes of the components to be refined issue has to be refined
Milestone

Comments

@o-hook
Copy link
Contributor

o-hook commented Jun 11, 2024

Scope

Though the Toast component was developed with accessibility best practices in mind (including the usage of role="status", the contents of the rendered Toast component are not announced in screen reader. This is due to the insufficient implementation of role="status" attribute.

Out of Scope

Notes

  • ARIA live attributes should always be rendered initially to have the best support for assistive technologies.
  • Possible solution: try to add role="status" to the host element.

Acceptance criteria

  • Contents of Toast component get announced in screen reader

Subtasks

  • Task
@o-hook o-hook added bug Something isn't working component Adds or changes of the components to be refined issue has to be refined code a11y labels Jun 11, 2024
@o-hook o-hook added this to the Accessibility milestone Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y bug Something isn't working code component Adds or changes of the components to be refined issue has to be refined
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant