Error Message

Concept facts

An error message is user-facing feedback that explains a problem, identifies where it happened, and helps the user recover or correct the issue.

Also known as: Validation error, form error, error feedback, input error message.
Used in: Forms, checkout flows, application systems, account creation, KYC, dashboards, document upload, payments, and service portals.
Interpret with: Error prevention, input validation, help text, status message, form usability, cognitive accessibility, accessibility, and task success.

Plain-language explanation

An error message helps users understand what went wrong and what to do next. It should be specific, visible, accessible, and close to the relevant field or action.

A weak error message says “Invalid input.” A stronger error message says “Enter the date in day/month/year format, for example 14/06/2026.”

In high-friction services, error messages are part of service quality. They help users recover instead of abandoning the task.

Why it matters

Poor error messages increase failure, support burden, frustration, and incorrect submissions. Users may not know what to fix, may repeat the same mistake, or may believe the service is broken.

In public-service, banking, health, education, and development-sector systems, an error can affect eligibility, account access, payment, appointment booking, or data quality.

Error messages also affect accessibility because assistive-technology users need errors to be announced and associated with the correct fields.

Use contexts

Error messages are used in:

required fields and form validation
document upload and file-format checks
identity verification and KYC flows
payment and transaction errors
login, account recovery, and password reset
eligibility and application systems
staff dashboards and case-management tools
accessibility and release-readiness testing

Application guidance

State the problem clearly and tell the user how to fix it. Avoid blame.

Place the error near the affected field and provide an error summary for longer forms where appropriate.

Use plain language. Do not expose technical codes unless they are needed for support.

Make errors accessible. Link summaries to fields, ensure programmatic relationships, and communicate changes to assistive technologies where needed.

Review error messages with real task scenarios. The message should help users recover in context.

Practical example

A digital bank asks users to update KYC information. When a national ID date is entered in the wrong format, the form says “Invalid value.” Many users retry several times and then call support.

A better error message says: “Enter the date of birth in day/month/year format, for example 09/04/1988.” The UX consequence is fewer failed submissions, lower call-center load, better verification data quality, and less risk of account-restriction anxiety.

Interpretive boundaries

An error message is not a substitute for error prevention. If many users make the same error, the field, label, instruction, validation rule, or service policy may need review.

Not all errors should be shown the same way. Critical errors, field-level errors, system failures, and status delays need different handling.

An error message should not reveal sensitive security information or misrepresent what happened.

Applied at Userhub

Userhub reviews error messages when evaluating forms, transactional flows, accessibility, and high-friction digital services.

In UX Lab work, error-message analysis helps connect content, validation, task success, and support burden.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

Government Digital Service. (n.d.). Error message. GOV.UK Design System. https://design-system.service.gov.uk/components/error-message/

Government Digital Service. (n.d.). Error summary. GOV.UK Design System. https://design-system.service.gov.uk/components/error-summary/

Home Office. (n.d.). Error messages. Home Office User-Centred Design Manual. https://design.homeoffice.gov.uk/accessibility/interactivity/error-messages

World Wide Web Consortium. (2024). Web Content Accessibility Guidelines (WCAG) 2.2. W3C Recommendation. https://www.w3.org/TR/WCAG22/

World Wide Web Consortium. (n.d.). Understanding Success Criterion 3.3.1: Error identification. https://www.w3.org/WAI/WCAG22/Understanding/error-identification.html

World Wide Web Consortium. (n.d.). ARIA19: Using ARIA role=alert or live regions to identify errors. W3C Web Accessibility Initiative. https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA19

Inal, Y. (2016). An eye-tracking study of different types of error messages in web forms. Journal of Eye Movement Research, 9(5). https://doi.org/10.16910/jemr.9.5.1

Userhub. (2026). Error Message. UX Reference. https://userhub.com.bd/reference/error-message/

Reference entry content