All work
02Fictional studyForm states

Formcheck

Problem

A summary of errors at the top of a long form tells people something is wrong without telling them where. They scroll, guess, and often lose what they already typed. Screen reader users get the summary read once and then have to hunt for the field.

Approach

  • Validate on blur and on submit, never on every keystroke, so the form does not argue while someone is typing.
  • Place the message directly under its field and tie it to the input with aria-describedby and aria-invalid.
  • Write messages that say how to fix the problem, not just that the value is invalid.
  • Keep entered values after a failed submit; only the errors change.

Outcome

Errors now appear where the correction happens, and the fix is described in the message itself. The form keeps its content on failure, so a mistake costs one edit rather than a re-entry.

No client, product data or performance figure is represented in this study.

Try it

All checks run in the browser on fictional values. This demo never submits data or stores a password.

At least 8 characters.

Talk about a project