-
Notifications
You must be signed in to change notification settings - Fork 9
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
Notifications should be read by screen reader #255
Comments
Reading:
My suggestion would be to either use As far as I can see toastify-js does not allow this. So either we need to deal with it upstream or have to look for another library |
Sure it's important, as it means you can not chat nor join the call. But yeah as per above, I would default to:
and expose it as a prop so apps can overwrite. |
Lib currently used https://github.com/apvarun/toastify-js |
Reported upstream at apvarun/toastify-js#105 with a link to our workaround |
I think toast notifications should be read by screen readers when they appears.
Maybe there's a way to integrate this into the component.
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_alert_role
The "polite" attribute could be set depending whether it's an error or warnings.
In some cases like in Talk, not sure if messages like "connection to signaling server is taking longer" is worth reading out. Maybe need an extra flag to prevent reading those ?
The text was updated successfully, but these errors were encountered: