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

Validate fields when user presses continue/submit #130

Closed
mrmjprice opened this issue Apr 15, 2020 · 3 comments · Fixed by #327
Closed

Validate fields when user presses continue/submit #130

mrmjprice opened this issue Apr 15, 2020 · 3 comments · Fixed by #327
Assignees
Labels
accessibility post-release fix Not release critical, however next up to fix

Comments

@mrmjprice
Copy link
Contributor

mrmjprice commented Apr 15, 2020

Validate fields when the user clicks continue/submit; rather than as they go through the page

If validation fails:

  • User is returned to top of the page (Must have)
  • Static error summary box added under the section title (Must have)
  • Dynamic error summary box text explaining the problem and linking to the field (Should have)
  • Add "Error:" before page name in <title>; but remove "Error:" when the user goes to the next stage

Static error summary text:

There is a problem

Please check your answers again

Dynamic error summary text:

There is a problem

<validation error text, with link to that field>

@mrmjprice mrmjprice changed the title Changes to validation Validate fields when user presses continue/submit Apr 15, 2020
@mrmjprice mrmjprice added accessibility post-release fix Not release critical, however next up to fix labels Apr 15, 2020
@mrmjprice
Copy link
Contributor Author

Screenshot 2020-04-15 at 11 59 14

@mrmjprice
Copy link
Contributor Author

Error message component: https://wmnetwork.netlify.com/components/message/

@daylesalmon
Copy link
Contributor

So the first error message has been implemented via PR #133

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility post-release fix Not release critical, however next up to fix
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants