Accessibility Kiwi insights
What accessible form errors need to do
Make form problems identifiable, understandable, and correctable without relying on color or repeated failed submissions.
A form error should help someone continue, not merely signal failure. If a system detects a problem, people need to know which field is affected, what went wrong, and—when known—how to correct it.
Describe the error in text
Do not rely on a red border, icon, or position alone. Name the field and explain the issue: “Email address is missing” or “Enter an email address in the format [email protected].” Connect the message to the field programmatically where the implementation supports it.
Make correction efficient
When several fields fail, provide a clear summary and inline messages, move focus intentionally, and preserve the valid information the person already entered. Give a correction suggestion when one is known and it does not compromise security.
Test the failure path
Submit the form with missing, invalid, and edge-case values. Check keyboard behavior, screen-reader announcements where possible, zoomed layouts, and the successful confirmation. Native browser validation can help, but its messages may not always be specific or persistent enough for the whole experience.
Kiwi can help design and test a request flow with clear recovery; data handling, legal obligations, and sector requirements remain project-specific.