Forms and validation · Lesson 9 of 10 · 7 minutes

Forms and validation: Confirmation states

A status region can announce a completed action while leaving focus on the current control.

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 confirmation states
Build this first target: <p> (id="confirmation", role="status"). Inspect the structure before checking the lesson.
Hint & worked example
A status region can announce a completed action while leaving focus on the current control.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<p id="confirmation" role="status"></p>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the confirmation states example
Extend your file to include: <p> (id="confirmation", role="status") containing “Signup preview ready.”. Inspect the structure before checking the lesson.
Hint & worked example
A status region can announce a completed action while leaving focus on the current control.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<p id="confirmation" role="status">Signup preview ready.</p>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete confirmation states pattern
Finish the pattern with: <p> (id="confirmation", role="status") containing “Signup preview ready.”; <button> (type="button") containing “Edit details”. Inspect the structure before checking the lesson.
Hint & worked example
A status region can announce a completed action while leaving focus on the current control.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<p id="confirmation" role="status">Signup preview ready.</p><button type="button">Edit details</button>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

A status region can announce a completed action while leaving focus on the current control.

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

<p id="confirmation" role="status">Signup preview ready.</p><button type="button">Edit details</button>

A status region can announce a completed action while leaving focus on the current control.

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 confirmation states?A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.A status region can announce a completed action while leaving focus on the current control.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Forms and validation: Validation checkpoint 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