Form Label
A Form Label says what an input needs. Code links the label to its matching control.
A real example
A checkout field keeps “Cardholder name” above the box. A hint below explains the expected spelling.
Main parts
- 01Persistent label
- 02Input control
- 03Hint or format
- 04Validation message
Use it when
Give every input a visible label, even when it also has a placeholder or icon.
Do not use it when
Do not use a placeholder as the only label. Nearby text alone does not provide an accessible name.
Name used in code
<label for> / aria-labelledby Before you ship
Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages.
Outcome: Use Form Label to solve this user need without losing the current context. User context: A checkout field keeps “Cardholder name” above the box. A hint below explains the expected spelling. Recommended pattern: Form Label. Why it fits: Give every input a visible label, even when it also has a placeholder or icon. Do not use it when: Do not use a placeholder as the only label. Nearby text alone does not provide an accessible name. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Form Label. Definition: A Form Label says what an input needs. Code links the label to its matching control. Release checks: Give each field a label that code can read. Link hints and errors, and keep entered values. Check autofill, keyboard order, validation timing, submit states, failure recovery, zoom, and languages. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.