-
Notifications
You must be signed in to change notification settings - Fork 13
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 - Error message for missing fields #3950
Comments
I think this falls under a "grey" area in WCAG where interpretations may vary. The success criteria (SC) requires that an error is identified and described. This is done. If two errors have the same error message text, each is distinguishable by following the related link back to the original error. |
IMO it would be helpful if this was implemented. (will look into the lift) |
Noting so I don't forget: |
I have a rough prototype working. The lift won't be that big. |
Thanks for the initial scoping Pete! Added the user story above and flagged that it's ready for design input. Moving this back to the product backlog. |
User story
As a form filler using a screen reader
I need to know how many errors I have on the page
I need to be able to connect the error announced to me with the form question I need to update, without using any visual cues.
So that I can complete the error and submit my form
There are two scenarios this user story should cover:
Description
For any forms with several required fields, if the user submit without any data, all the issues for missing required fields have the same label "Please complete the required field to continue". This is a failure of accessibility SC 3.3.1.
The error message should provide the label of the inputs.
Steps to reproduce
Expected behaviour
Like in https://wet-boew.github.io/v4.0-ci/demos/formvalid/formvalid-en.html, Title and First name are added in the error message.
It should look like this:
Additional context
Reported in Freshdesk ticket 18068.
The text was updated successfully, but these errors were encountered: