Forms and validation · Lesson 5 of 10 · 7 minutes

Forms and validation: Help text relationships

aria-describedby associates a control with help text identified by an existing element id.

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 help text relationships
Build this first target: <label> (for="name") containing “Display name”; <input> (id="name"). Inspect the structure before checking the lesson.
Hint & worked example
aria-describedby associates a control with help text identified by an existing element id.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<label for="name">Display name</label><input id="name">
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the help text relationships example
Extend your file to include: <label> (for="name") containing “Display name”; <input> (id="name"); <p> (id="name-help") containing “Use a name you are comfortable sharing.”. Inspect the structure before checking the lesson.
Hint & worked example
aria-describedby associates a control with help text identified by an existing element id.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<label for="name">Display name</label><input id="name"><p id="name-help">Use a name you are comfortable sharing.</p>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete help text relationships pattern
Finish the pattern with: <label> (for="name") containing “Display name”; <input> (id="name", aria-describedby="name-help"); <p> (id="name-help") containing “Use a name you are comfortable sharing.”. Inspect the structure before checking the lesson.
Hint & worked example
aria-describedby associates a control with help text identified by an existing element id.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<label for="name">Display name</label><input id="name" aria-describedby="name-help"><p id="name-help">Use a name you are comfortable sharing.</p>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

aria-describedby associates a control with help text identified by an existing element id.

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

<label for="name">Display name</label><input id="name" aria-describedby="name-help"><p id="name-help">Use a name you are comfortable sharing.</p>

aria-describedby associates a control with help text identified by an existing element id.

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 help text relationships?aria-describedby associates a control with help text identified by an existing element id.A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.

Apply it elsewhere

You reuse help text relationships 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: Error messages 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