Em linha, ao perder o foco ou ao enviar: o momento importa

The same error message can help or annoy depending on when it appears. Timing is its own accessibility decision. ⏱️

Checking everything on submit is predictable and never interrupts. It is the safest default for almost every form.

Validating on every keystroke flags a field as wrong before the user finishes typing. That inline nagging frustrates everyone.

Checking when the user leaves a field, on blur, lets them finish typing first, then gives feedback at a natural pause.

An error that pops mid-typing can hijack a screen reader. Wait for a real moment, like blur or submit, before announcing.

Once a field has failed and the user is fixing it, re-validating as they type is welcome. It confirms the error is clearing.

WCAG asks you not to rush users. Avoid timeouts that clear input, and let people complete a field at their own pace.

Mark required fields up front with required and a visible note, so users know the rule before they submit, not after.

Whatever the timing, say what is wrong and how to fix it. A clear message beats a vague one fired at the perfect moment.

Native HTML validation fires on submit by default. Built-in attributes like type and required give you sane timing for free.

Pick one timing strategy and apply it across the form. Predictable behavior lets users learn the pattern and trust it.

Which validation timing is the most accessible default?

Validate on blur or submit, not every keystroke, re-check inline once fixing, state rules early, and stay consistent. ✅