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

[Accessibility] Toast notifications not announced by screen readers #12528

Open
1 task done
patrickhlauke opened this issue Dec 21, 2024 · 2 comments
Open
1 task done
Labels
browser Browser Extension bug

Comments

@patrickhlauke
Copy link
Contributor

Steps To Reproduce

  1. Run a screen reader
  2. Perform an action that triggers a toast notification (e.g. trying to unlock a vault with the wrong password)

Expected Result

Toast notification should be announced by the screen reader (using a live region notification).

Actual Result

Toast notification is not announced at all by screen readers.

Screenshots or Videos

bitwarden-toast-notification-not-announced-sr.mp4

Video: Chrome/NVDA, trying to unlock a vault with an empty password - a toast error notification is shown, but NVDA remains fully silent.

Additional Context

Possibly still related to #3487

I also filed an issue ages ago upstream scttcper/ngx-toastr#957 but not sure if anything came from that.

This may be interesting/relevant: https://tetralogical.com/blog/2024/05/01/why-are-my-live-regions-not-working/

Operating System

Windows

Operating System Version

11

Web Browser

Chrome

Browser Version

131.0.6778.205 (Official Build) (64-bit)

Build Version

2024.12.2

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@patrickhlauke patrickhlauke added browser Browser Extension bug labels Dec 21, 2024
@bitwarden-bot
Copy link

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-16294

@SergeantConfused
Copy link

Hello @patrickhlauke,

Thank you for your report. I have flagged this to the Engineering department; please feel free to post additional information, such as screenshots or a screen video recordings, if you wish.

Thank you again,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser Browser Extension bug
Projects
None yet
Development

No branches or pull requests

3 participants