Helpful Error Text

Helpful error text transforms frustrating error experiences into guided recovery by clearly explaining problems and providing actionable solutions. Well-written errors support users rather than blaming them.

What Is Helpful Error Text

Helpful error text is user-facing copy that identifies problems specifically and guides users toward resolution. This differs from technical error messages or generic notices that leave users confused about what went wrong and what to do.

WCAG 3.3.1 requires that errors be identified and described in text. WCAG 3.3.3 suggests that error suggestions be provided when possible. Helpful error text fulfills both requirements.

Components of helpful error text:

• What happened (the specific problem)
• Why it matters (if not obvious)
• How to fix it (actionable steps)

How to Write Helpful Error Text

Specific identification names the exact problem:

Format guidance provides examples of correct input:

Solution focus tells users what to do next:

User-centered framing avoids blame:

Context-appropriate detail provides information users need without overwhelming:

Plain language uses words users understand:

Key Considerations

• Identify the specific problem, not generic “invalid” messages
• Provide examples of correct format when relevant
• Focus on solutions, not problems
• Frame errors without blaming users
• Match detail level to context and user needs
• Use plain language, not technical terms
• Test error text with actual users

Common Questions

How long should error messages be?

Error messages should be as short as possible while providing needed information. Simple validation errors (empty required field) need only a few words. Complex errors (payment processing issues) may need more explanation.

Use progressive disclosure for complex errors: brief inline message with option to see more details.

Should error messages include error codes?

Error codes help support teams diagnose issues but mean nothing to most users. If codes are needed, display them secondarily:

The human-readable message serves users; the code serves support interactions.

How should error messages differ between contexts?

Different contexts warrant different error approaches:

• Form validation: Brief inline messages near fields
• API errors: User-friendly translations of technical failures
• System errors: Apologize, explain limitation, provide alternatives
• Permission errors: Explain why and offer paths forward

Adapt tone and detail to the error type and user context.

Summary

Helpful error text specifically identifies problems, provides format guidance and examples, focuses on solutions, and uses user-centered plain language. Effective error messages transform potential abandonment into successful task completion.