Form Field
A full input unit with a visible label, a control, optional help, validation state, and a linked error message.
A real example
A tax ID field keeps its label visible. It explains the format before typing and links to a clear error after validation.
Main parts
- 01Persistent label
- 02Input control
- 03Hint or format
- 04Validation message
Use it when
Give every value a complete field with an accessible name and a consistent place for help and errors.
Do not use it when
Do not use placeholder text as the only label. Do not show an error through color alone.
Name used in code
label + input + aria-describedby + error message 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 Field to solve this user need without losing the current context. User context: A tax ID field keeps its label visible. It explains the format before typing and links to a clear error after validation. Recommended pattern: Form Field. Why it fits: Give every value a complete field with an accessible name and a consistent place for help and errors. Do not use it when: Do not use placeholder text as the only label. Do not show an error through color alone. 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): It is official for that source. Other platforms or teams may use the term in another way. 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 Field. Definition: A full input unit with a visible label, a control, optional help, validation state, and a linked error message. 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.