Interaction testing
Test a Form's Error Recovery Path
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Evaluate the process from an invalid submission to a successful correction. Choose representative errors that the form actually supports, and preserve valid information between attempts. Use a test environment so a successful submission has no unwanted real-world effect.
A practical example
A grant application contains a missing required answer and an attachment in an unsupported format.
How to check it
- Submit the form with the planned invalid values. Check that the feedback identifies the affected fields and describes the problems in text.
- Navigate from the error summary or announcement to each field. Verify that labels and instructions still provide enough context to make a correction.
- Correct one error at a time and resubmit. Check that resolved messages disappear appropriately, remaining errors stay accurate and valid entries are retained.
What can be missed
Red borders alone do not explain an error. A message that only appears visually after submission can be missed when focus stays far away.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.