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 Report][2.7.0] v-snackbar is not consistently detected on multiple screen readers #19513

Open
cjoulain opened this issue Mar 29, 2024 · 1 comment
Assignees
Labels
a11y Accessibility issue P: sponsor T: bug Functionality that does not work as intended/expected

Comments

@cjoulain
Copy link

cjoulain commented Mar 29, 2024

Environment

Vuetify Version: 2.7.0
Vue Version: 2.7.7
Browsers: Chrome 123.0.0.0
OS: Mac OS 10.15.7

Steps to reproduce

We use v-snackbar in combination with our event listeners to send live notifications such as "Message sent to [email protected]". Recent WebAIM surveys reveal that JAWS, NVDA, and Voiceover are the most popular screen readers in usage and we conduct our accessibility testing with these voice output technologies. Currently, JAWS and NVDA do not detect v-snackbar. Voiceover is sometimes is able to narrate the contents of v-snackbar and sometimes not. Since we're striving for WCAG compliance (in particular 4.1.3 Status Messages), do you have any suggestions for how to resolve? We currently use Vuetify 2.7 but have also tested the component on Vuetify 3. Please see this Loom: https://www.loom.com/share/ef27ae7640dc479bb7e4fbc7f06ae7c4

Expected Behavior

v-snackbar is narrated across the top 3 screen readers in both Vuetify 2 and 3

Actual Behavior

v-snackbar is inconsistently detected by the top 3 screen readers or not detected at all in either Vuetify 2 and 3

Reproduction Link

https://codepen.io/cj-bc/pen/gOyGveY

Other comments

Please feel free to reach out to me on the Vuetify Discord (cj.here).

@KaelWD
Copy link
Member

KaelWD commented Mar 30, 2024

Apparently screenreaders aren't supposed to read live regions as they're inserted, only on updates: nvaccess/nvda#14591 w3c/aria#1216

@KaelWD KaelWD added T: bug Functionality that does not work as intended/expected a11y Accessibility issue P: sponsor labels Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a11y Accessibility issue P: sponsor T: bug Functionality that does not work as intended/expected
Projects
None yet
Development

No branches or pull requests

3 participants