Forms and validation · Lesson 8 of 10 · 10 minutes

Forms and validation: Grouped choices

fieldset and legend give a related set of form controls a shared accessible name.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

Current edit

PreviewNo external resources

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Build grouped choices
Build this first target: <fieldset>; <legend> inside <fieldset> containing “Choose a track”. Inspect the structure before checking the lesson.
Hint & worked example
fieldset and legend give a related set of form controls a shared accessible name.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<fieldset><legend>Choose a track</legend></fieldset>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the grouped choices example
Extend your file to include: <fieldset>; <legend> inside <fieldset> containing “Choose a track”; <label> inside <fieldset> containing “UNIX”; <input> inside <label> (type="radio", name="track", value="unix"). Inspect the structure before checking the lesson.
Hint & worked example
fieldset and legend give a related set of form controls a shared accessible name.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<fieldset><legend>Choose a track</legend><label><input type="radio" name="track" value="unix">UNIX</label></fieldset>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete grouped choices pattern
Finish the pattern with: <fieldset>; <legend> inside <fieldset> containing “Choose a track”; <label> inside <fieldset> containing “UNIX”; <input> inside <label> (type="radio", name="track", value="unix"); <label> inside <fieldset> containing “Web”; <input> inside <label> (type="radio", name="track", value="web"). Inspect the structure before checking the lesson.
Hint & worked example
fieldset and legend give a related set of form controls a shared accessible name.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<fieldset><legend>Choose a track</legend><label><input type="radio" name="track" value="unix">UNIX</label><label><input type="radio" name="track" value="web">Web</label></fieldset>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

fieldset and legend give a related set of form controls a shared accessible name.

Misconceptions to reject

A visual appearance alone guarantees the intended HTML meaning.
Replacing semantic elements with generic divs automatically improves accessibility.

The preview is a sanitized subset, not a full browser compatibility test.

Worked example and expected result

<fieldset><legend>Choose a track</legend><label><input type="radio" name="track" value="unix">UNIX</label><label><input type="radio" name="track" value="web">Web</label></fieldset>

fieldset and legend give a related set of form controls a shared accessible name.

Try a variation

Adapt the final example to a different project name while retaining its structure and relationships. A different context still needs a real browser and accessibility check.

Explain it

Which statement correctly explains grouped choices?fieldset and legend give a related set of form controls a shared accessible name.A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.

Apply it elsewhere

You reuse grouped choices in a different project. What must still be verified?Nothing; passing a single exercise guarantees every future use.Only whether the source code has the same number of lines.The meaning, relationships, and accessible names in the new document.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Forms and validation: Confirmation states Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

MDN: HTML structure