Error Summary
An error summary is a short list at the top of a form. Each item explains an error and links to its field.
submit -> validate -> focus summary -> link each message to its invalid field#email · Enter a complete email address#password · Use at least 12 charactersname@••••••••submit -> validate -> focus summary -> link each message to its invalid fieldA11YAnother example
A form has two errors. Submit moves focus to the summary. Choosing Email moves focus to the email field.
Main parts
- 01Summary heading
- 02Error count
- 03Linked error item
- 04Field identifier
- 05Inline field message
- 06Focus path
Use it when
Use it after a submit attempt finds several errors. Keep an inline message beside every affected field.
Do not use it when
Do not replace field messages with one vague banner. Do not clear the person's valid input after validation fails.
Name used in code
submit -> validate -> focus summary -> link each message to its invalid field Before you ship
Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages.
Outcome: Use Error Summary to solve this user need without losing the current context. User context: A form has two errors. Submit moves focus to the summary. Choosing Email moves focus to the email field. Recommended pattern: Error Summary. Why it fits: Use it after a submit attempt finds several errors. Keep an inline message beside every affected field. Do not use it when: Do not replace field messages with one vague banner. Do not clear the person's valid input after validation fails. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): It is official for that source. Other platforms or teams may use the term in another way. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Error Summary. Definition: An error summary is a short list at the top of a form. Each item explains an error and links to its field. Release checks: Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.