Choose against the task constraints
A synthetic eight-field project enquiry has three invalid fields after submission: a missing project name, an unsupported date and an unchosen service mode. The budget field is optional and blank, which is not a fourth error. The user’s valid text must remain available for correction.
| Condition | Field-only messages | Linked summary plus field messages |
|---|---|---|
| Several errors far apart | User must locate each field | Summary links give direct routes to the errors |
| One short field | Local message may be enough | Extra summary can repeat the same information |
| Explain a correction | Name the problem near its input | Use matching field labels in both places |
For this long form, use a linked summary together with concise field messages. Do not erase correct answers or show only a generic submission failure. The summary identifies the correction work; it does not repeat the form’s entire instructions.
Count actual errors
| Field | Submitted value | Result |
|---|---|---|
| Project name | Blank; required | Error |
| Date | 31 November; real date required | Error |
| Service mode | Empty; one choice required | Error |
| Budget | Blank; optional | Accepted |
How many links belong in the error summary?
Show the worked answer
Three: project name, date and service mode. Budget is optional in the stated rules and should not be listed as an error.
Check the chosen interaction
- Each summary link reaches its actual input.
- Field feedback remains available to assistive technology.
- Correcting one field does not erase other valid values.