Fieldset and Legend
`<fieldset>` and `<legend>` are built-in HTML elements for a group of related form controls. The legend states the question they share.
Another example
A tax form puts three radio buttons under the legend “Filing status.” Each choice still has its own label. If there is an error, it appears after the legend so people know which question to fix.
Main parts
- 01Fieldset boundary
- 02Legend question
- 03Labeled controls
Use it when
Use them for radio buttons, checkboxes, or fields that answer one shared question.
Do not use it when
Do not use `<fieldset>` only to style a box. Every control inside still needs its own label.
Name used in code
fieldset > legend + individually labeled controls 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 Fieldset and Legend to solve this user need without losing the current context. User context: A tax form puts three radio buttons under the legend “Filing status.” Each choice still has its own label. If there is an error, it appears after the legend so people know which question to fix. Recommended pattern: Fieldset and Legend. Why it fits: Use them for radio buttons, checkboxes, or fields that answer one shared question. Do not use it when: Do not use `<fieldset>` only to style a box. Every control inside still needs its own label. 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 Fieldset and Legend. Definition: `<fieldset>` and `<legend>` are built-in HTML elements for a group of related form controls. The legend states the question they share. 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.