Forms and validation · Lesson 7 of 10 · 7 minutes

Forms and validation: Input descriptions

A placeholder is not a replacement for a visible label or persistent help text.

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 input descriptions
Build this first target: <label> (for="handle") containing “Handle”; <input> (id="handle"). Inspect the structure before checking the lesson.
Hint & worked example
A placeholder is not a replacement for a visible label or persistent help text.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<label for="handle">Handle</label><input id="handle">
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the input descriptions example
Extend your file to include: <label> (for="handle") containing “Handle”; <input> (id="handle", placeholder="terminal-scout"). Inspect the structure before checking the lesson.
Hint & worked example
A placeholder is not a replacement for a visible label or persistent help text.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<label for="handle">Handle</label><input id="handle" placeholder="terminal-scout">
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete input descriptions pattern
Finish the pattern with: <label> (for="handle") containing “Handle”; <input> (id="handle", placeholder="terminal-scout", aria-describedby="handle-help"); <p> (id="handle-help") containing “Letters and hyphens only.”. Inspect the structure before checking the lesson.
Hint & worked example
A placeholder is not a replacement for a visible label or persistent help text.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<label for="handle">Handle</label><input id="handle" placeholder="terminal-scout" aria-describedby="handle-help"><p id="handle-help">Letters and hyphens only.</p>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

A placeholder is not a replacement for a visible label or persistent help text.

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="handle">Handle</label><input id="handle" placeholder="terminal-scout" aria-describedby="handle-help"><p id="handle-help">Letters and hyphens only.</p>

A placeholder is not a replacement for a visible label or persistent help text.

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 input descriptions?Replacing semantic elements with generic divs automatically improves accessibility.A placeholder is not a replacement for a visible label or persistent help text.A visual appearance alone guarantees the intended HTML meaning.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Forms and validation: Grouped choices 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