Accessibility Checklist: Forms Error Handling
Bobby Bailey
How to Provide Clear and Usable Error Messages
Proper error handling helps people complete forms efficiently, especially those using screen readers or assistive technologies. Use this checklist to ensure errors are accessible and easy to understand.
10-Point Accessible Forms Error Handling Checklist
Number one: Errors are clearly identified and easy to find
Error messages appear near the affected field and not only at the top of the page. Errors should not disappear before they can be read.
Number two: Error messages are descriptive
Instead of “Invalid input,” specify what is wrong (e.g., “Password must be at least 8 characters”). Messages should help people fix the issue, not just state that something is wrong.
Number three: Errors are programmatically associated with fields
Use aria-describedby to link error messages to form inputs. Screen readers should announce errors when the field is focused.
Number four: Do not rely on color alone to indicate errors
Use icons, text, or additional cues along with color changes. Example: A red border with “This field is required” below the input.
Number five: Provide real-time validation when appropriate
Allow people to fix mistakes before submitting the form. Example: Show “Username is already taken” before the person submits.
Number six: Allow people to review and correct errors easily
Highlight all errors at once rather than revealing them one at a time. Provide a summary at the top of the form for quick review.
Number seven: Forms can be submitted without a mouse
All error-handling interactions must be keyboard accessible. Ensure the Tab key moves logically between error messages and form fields.
Number eight: Use accessible confirmation messages
When the form is successfully submitted, provide a clear, visible, and screen reader-friendly confirmation message. Avoid using only pop-ups or modals that disappear quickly.
Number nine: Ensure required fields are clearly labeled
Include “(Required)” or aria-required="true" instead of just an asterisk *. Clearly state what is needed for successful submission.
Number ten: Test with assistive technologies
Use screen readers like NVDA, JAWS, or VoiceOver to verify error messages are properly read aloud. Test with keyboard navigation to ensure fixing errors is seamless.