Red is not an error message.
When a form fails and the only signal is a red border, many actual users get no signal at all. Screen reader users may never hear what went wrong. Keyboard users may be returned to the top of the page with no explanation. People who cannot perceive color are left guessing which field to fix.
WCAG calls this Error Identification and Error Suggestion. In plain English: say what went wrong, in text, right where the problem is, and when a correction is known, suggest it.
Good errors name the field, describe the problem in plain language, preserve everything already entered, and move focus to a clear summary that links back to each field. That is not extra polish. That is whether a service can be completed at all.
Design errors to be heard, read, and acted on — not just seen.
#Accessibility #A11y #WCAG #UX
-
Desarae Veit
Senior UI/UX web designer at a large-scale IT contractor for defense, intelligence, and civilian government solutions. Adventurist and certified Yoga / Barre Instructor. Love aviation, books, and travel.Prefer long light hearted series in mystery, comedy, fantasy, and romance.
More About the AuthorShare This Post
No comments:
Post a Comment
Backlinks will be hidden. Crude comments may be removed.