-
Notifications
You must be signed in to change notification settings - Fork 357
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
Accessibility: toasts are "double-announced" in Chrome/NVDA #957
Comments
incidentally, I found some further flakyness (described in bitwarden/clients#3487 (comment)) caused by the |
maybe we could expose a way for you to create the container manually when you want it |
I also got this issue. Chrome + NVDA, toasts are "double-announced". It is because role alert on toast message. How can we fix this issue? |
randomly, this may be of interest https://tetralogical.com/blog/2024/05/01/why-are-my-live-regions-not-working/ |
A follow-up to #934 - there may have been a recent change in timings on how the toasts are now created, or something may have changed in the timing of how Chrome/Windows exposes these, but currently when testing https://ngx-toastr.vercel.app/ in Chrome/NVDA, most toasts are "double-announced" (once because of the
aria-live="polite"
on the toast container, and then again because of therole="alert"
in the actual toast).This does not happen in Firefox/NVDA, which makes me suspect it's possibly some change in Chrome specifically.
Video recording using Chrome/NVDA
toast-double-announcements.mp4
I'm pressed for time at the moment, but over the weekend I can file a follow-up to #934 that further tweaks the output, removing the
role="alert"
itself, leaving the announcement purely down to thearia-live="polite"
.Question though: I assume that if an author does NOT create their custom toast container per https://github.com/scttcper/ngx-toastr#put-toasts-in-your-own-container, that this script generates its own, and that THAT also includes
aria-live="polite"
?src/lib/overlay/overlay-container.ts
makes me think that's the case, but just to be sure...The text was updated successfully, but these errors were encountered: