Accessibility · Cluster
Forms and Errors
Labels, validation, and recovery.
- 01 Label Association and the Accessible Name of a Form Control How the for attribute and implicit nesting bind a label to a control, how that binding becomes an accessible name, and what an unassociated label leaves behind.
- 02 Fieldset and Legend Group Semantics How fieldset and legend give a set of controls one shared name, how the browser exposes that grouping, and where the element falls short of what a group needs.
- 03 Autofill Tokens and the Purpose of an Input How the autocomplete attribute encodes what a field means, how browsers and assistive technology consume it, and why the token set is a closed vocabulary.
- 04 Placeholders as a Fallback Name and Why They Fail How the placeholder attribute enters the accessible name computation, why it ranks last, and the concrete failures that follow from using it as a label.
- 05 Native Constraint Validation and the ValidityState Object How the browser evaluates required, pattern, min, and max attributes, what each ValidityState flag means, and where the built-in validation loop breaks down.
- 06 Wiring Error Messages to Their Fields How aria-describedby, aria-invalid, and aria-errormessage bind a message to a control, and how the accessibility tree orders what the user hears.
- 07 Error Summaries and Focus Placement on Failed Submission Where focus goes when a form rejects a submission, why a summary block beats a browser bubble, and how to make the summary navigable.
- 08 Inline Validation Timing and When Errors Should Speak How validation on blur, on input, and on submit differ in what they interrupt, how debouncing and politeness control announcement, and why premature feedback degrades entry.
- 09 Multi-Step Form State and What Survives a Step What a wizard loses between steps when each step is a fresh document, how a step boundary changes validation, and how to make back navigation non-destructive.
- 10 Preventing Irreversible Errors in Consequential Submissions How confirmation, review, and reversal mechanisms trade friction against irreversibility, and where each mechanism fails for users who cannot see the mistake.