What happens with errors after submit
Most people have filled a long form, tapped submit and hunted for five red messages at the top. In Wroblewski's (2009) tests, inline validation cut completion time and improved errors and satisfaction. People notice errors through feedback (Sellen, 1994), so feedback belongs beside the error. This is core to mobile form usability.
When to validate
Bargas-Avila et al. (2007) found errors shown while typing hinder users; an email error after one letter feels like a scolding. Validate on leaving the field, and clear an existing error as soon as it is fixed. For rule-based fields such as passwords, show requirements upfront and tick them off. Combine with error prevention design.
Good error copy and accessibility
Per Krause (2019), place errors near the field and say what is wrong and how to fix it, such as 'Enter your birth date as eight digits'. Seckler et al. (2014) found such guidelines speed correction. Avoid blaming users (Norman, 1983). WCAG 2.2 (W3C, 2023) requires text identification (3.3.1) and suggestions (3.3.3); pair red with icons and text, check colour contrast and expose errors to screen readers.
FAQ
- Shouldn't you validate on every keystroke?
- Most fields should validate on blur; keystroke checks suit progress such as password rules.
- Are success indicators needed?
- Useful for uncertain fields such as username availability, unnecessary for obvious ones.
Sources reviewed: 2026-10-27
References
- Wroblewski, L. (2009, September 1). Inline validation in web forms. A List Apart. Usability test showing benefits of inline validation.
- Bargas-Avila, J. A., Oberholzer, G., Schmutz, P., de Vito, M., & Opwis, K. (2007). Usable error message presentation in the World Wide Web: Do not show errors right away. Interacting with Computers, 19(3), 330–341. Showing errors while typing hinders users.
- Seckler, M., Heinz, S., Bargas-Avila, J. A., Opwis, K., & Tuch, A. N. (2014). Designing usable web forms: Empirical evaluation of web form improvement guidelines. In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (pp. 1275–1284). ACM. Validates form guidelines including error messages.
- Krause, R. (2019, February 3). 10 design guidelines for reporting errors in forms. Nielsen Norman Group. Ten guidelines for reporting form errors.
- World Wide Web Consortium. (2023). Web Content Accessibility Guidelines (WCAG) 2.2. Criteria 3.3.1 and 3.3.3 on identifying and suggesting fixes.
- Norman, D. A. (1983). Design rules based on analyses of human error. Communications of the ACM, 26(4), 254–258. Frames errors as design problems.
- Sellen, A. J. (1994). Detection of everyday errors. Applied Psychology, 43(4), 475–498. People detect errors through feedback.