Baymard: validation timing

Evidence class: first-party reported observational usability research and practitioner recommendations, not a randomized uplift estimate. Read: 13 September 2026; rechecked 29 October 2026. Coverage: one public article; the paid research corpus and underlying recordings were not independently audited.

Findings and application boundary

Baymard reports that premature errors interrupt entry. For most fields it recommends validating when the user leaves the field. For fixed-length entries such as postal codes, phone numbers and card numbers, it also allows validating once the entry reaches its expected length. An error should disappear on the keystroke that makes the input valid. The examples concern commerce forms. Source: Usability testing of inline form validation, Edward Scott, 9 January 2024, read 2026-10-29.

The article also recommends positive validation. That is an author recommendation, not proof that every field on every website needs a green checkmark. Do not transfer the article's benchmark percentages or historical retailer screenshots into claims about current product quality.

Tension to preserve

GOV.UK instead says not to validate when the user leaves a field, and to wait until they continue or submit. Its research exception covers checking during entry, not field exit. Source: GOV.UK: Recover from validation errors, read 2026-10-29. On field exit the two sources directly disagree. Our synthesis is to keep that disagreement visible, not declare a universal field-exit or keystroke policy. Test interruption and successful correction in the actual task. No new user study was run here.