You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error field within Flux doesn't announce to screenreaders when an error is triggered. It just pops into visibility onto the page, which is works for the average user, but anyone using a screenreader doesn't know that the error was triggered.
You can recreate this by using any <flux:error name="foo" /> component on the page then attempting to move through a form using a screenreader. Anytime you try to validate the screenreader won't announce the errors when they're triggered.
How do you expect it to work?
I expect that any errors that are triggered within a Livewire form are alerted to screenreaders automatically.
e.g. in flux/error.blade.php
I published this component then added the following aria-live and aria-atomatic in my code to make this accessible within the site I'm working on!
Flux version
1.0.23
Livewire version
3.5.12
What is the problem?
The error field within Flux doesn't announce to screenreaders when an error is triggered. It just pops into visibility onto the page, which is works for the average user, but anyone using a screenreader doesn't know that the error was triggered.
Originally reported in this discussion #441 by @lonebadger99
Code snippets
You can recreate this by using any
<flux:error name="foo" />
component on the page then attempting to move through a form using a screenreader. Anytime you try to validate the screenreader won't announce the errors when they're triggered.How do you expect it to work?
I expect that any errors that are triggered within a Livewire form are alerted to screenreaders automatically.
e.g. in
flux/error.blade.php
I published this component then added the following
aria-live
andaria-atomatic
in my code to make this accessible within the site I'm working on!Please confirm (incomplete submissions will not be addressed)
The text was updated successfully, but these errors were encountered: