Validation errors provide suggestions for correction
Why it matters
Error messages that say 'Invalid' or 'Error' without explaining the constraint leave users — especially those with cognitive disabilities — stuck on forms they cannot fix. WCAG 2.2 SC 3.3.3 (Error Suggestion) is a Level AA requirement: when an input error is detected and suggestions for correction are known, the suggestion must be provided. A password field that says 'Invalid' instead of 'Password must be at least 8 characters with one uppercase letter' causes measurable task abandonment.
Severity rationale
Low because the absence of correction suggestions harms completion rates without completely blocking form access — violating WCAG 2.2 SC 3.3.3 at Level AA rather than the more critical Level A SC 3.3.1.
Remediation
Replace every generic error string with a message that names the constraint and shows the expected format.
// Before — tells users nothing actionable
const errors = {
email: 'Invalid email',
password: 'Error',
phone: 'Required',
}
// After — tells users exactly what to do
const errors = {
email: 'Enter a valid email address (e.g., name@example.com)',
password: 'Password must be at least 8 characters and include one number',
phone: 'Enter a 10-digit US phone number (e.g., 555-867-5309)',
}
Search for error string literals across your form validation logic in src/. Any message under five words — or that only echoes the field name — should be expanded to include the expected format or the correction step.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Accessibility WCAG Compliance Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- wcag:2.2 · 3.3.3 — Error Suggestion
- section-508:2018-refresh · 501.1 — Scope
Taxons
History
- 2026-04-18·v1.0.0·Initial import from accessibility-wcag·automated