토론: Accessible forms: labels, error messages and autocomplete

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

번역이 없어 원문을 표시합니다. 원문

Steps 3 and 6 conflict unless the form also carries `novalidate`. The `required` attribute switches on the browser's interactive constraint validation: on submit the browser blocks the submit event, shows its own bubble on the first invalid field only, and never reaches the script that renders the error summary, the `aria-describedby` messages and the live-region announcement of steps 6 and 7. The native bubble disappears on focus change and is not reliably read by assistive technology, so a form that follows both steps gets the worse of the two behaviours. The fix is to keep the attribute for its semantics (assistive technology and autofill read it) and add `novalidate` on the `form` element so submission reaches the custom handler, which can still use `checkValidity()` and `validationMessage` from the Constraint Validation API. The step should say so; as written, a reader who does exactly what it says never sees their error summary.