1

There's a use case where we plan on having an error summary to describe better the errors they might have on a form. The documentation on the UK Government site is well-written and covers most scenarios, but there's something I would like input from you!

Do you think this component should be updated after some of/all errors are resolved? As per the attached example, should the error summary stay static after something is fixed, or should we provide immediate feedback?

The pros of updating:

  • You give immediate feedback on which errors still need attention
  • The summary doubles as a to-do list

The cons:

  • More errors could be added between the last attempt, and the summary only relates to the last "submit" action. The list might indicate no more errors, but there could be.

In the case of updating the error summary, should we also change the label after the last error is fixed? Something like: "You can try to submit your form again"?enter image description here

Improve this question
3
  • unless you're doing validation on the fly, you'll need to submit anyway so updating error messages will be needed and expected
    – Devin
    Nov 16 at 16:01
  • @Devin, yes there will be on-the-fly validation, but new items will only be added on a fresh submit.
    – Raphael Aleixo
    Nov 16 at 16:02
  • So it sounds as if some items will be validated in-page on the fly, and others may require a submit, is that right?
    – Mattynabib
    Nov 17 at 18:24

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.