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

Screen reader not announcing errors on Web forms #1284

Open
bsw2112 opened this issue Nov 4, 2024 · 6 comments
Open

Screen reader not announcing errors on Web forms #1284

bsw2112 opened this issue Nov 4, 2024 · 6 comments

Comments

@bsw2112
Copy link

bsw2112 commented Nov 4, 2024

When some required fields are left empty on a form and I press submit the screen reader in JAWS does not automatically read
the heading: The form could not be submitted because 2 errors were found.

I must first press the arrow down key once at which point it will read it. If should read it as soon as the form is submitted.
It works correctly here https://wet-boew.github.io/wet-boew/demos/formvalid/formvalid-en.html but not when WET is loaded via CTDS
Thanks

[email protected]

@ahmad-shahid
Copy link
Contributor

Hello, I'll investigate this. Do you have a link to a site that has this issue?

@bsw2112
Copy link
Author

bsw2112 commented Nov 8, 2024

Hello Ahmad

Here is a sample: https://www.sac-isc.gc.ca/eng/1585664064807/1585678941114

I am running JAWS version 2023.2311.34
When I leave the two fields empty and press submit I see the error message but I need to press the arrow down key once to hear the heading: The form could not be submitted because 2 errors were found

However when I go to the WET examples here: https://wet-boew.github.io/wet-boew/demos/formvalid/formvalid-en.html#wb-cont
The screen reader reads the error out right away. "The form could not be submitted because 9 errors were found."

This is affecting all our Internal forms.

Thanks
[email protected]

@ahmad-shahid
Copy link
Contributor

Thank you

@ahmad-shahid
Copy link
Contributor

@bsw2112
Copy link
Author

bsw2112 commented Nov 15, 2024

Hi Ahmad

I have sent the links to our visually impaired employee to review each of the three links. As soon as I hear back I will reply with the results

Thanks!

@bsw2112
Copy link
Author

bsw2112 commented Nov 20, 2024

Hi Ahmad

From what I am told the links you provided have not rectified the issue
I had a visually impaired user test it and one of the developers too
The dev provided a video recording of what he hears - https://www.youtube.com/watch?v=cR26Pw4GV24

The dev created a hack to fix this for our Intranet so if you wanted to know more about what he did please let me know

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

No branches or pull requests

2 participants