Accessibility · Lesson 6 of 8 · 7 minutes

Accessibility: Status announcements

role="status" communicates non-urgent updates without requiring an interrupting alert or focus change.

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 status announcements
Build this first target: <p> (id="status", role="status"). Inspect the structure before checking the lesson.
Hint & worked example
role="status" communicates non-urgent updates without requiring an interrupting alert or focus change.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<p id="status" role="status"></p>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the status announcements example
Extend your file to include: <p> (id="status", role="status") containing “Notes saved.”. Inspect the structure before checking the lesson.
Hint & worked example
role="status" communicates non-urgent updates without requiring an interrupting alert or focus change.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<p id="status" role="status">Notes saved.</p>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete status announcements pattern
Finish the pattern with: <p> (id="status", role="status") containing “Notes saved.”; <button> (type="button") containing “Keep editing”. Inspect the structure before checking the lesson.
Hint & worked example
role="status" communicates non-urgent updates without requiring an interrupting alert or focus change.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<p id="status" role="status">Notes saved.</p><button type="button">Keep editing</button>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

role="status" communicates non-urgent updates without requiring an interrupting alert or focus change.

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="status" role="status">Notes saved.</p><button type="button">Keep editing</button>

role="status" communicates non-urgent updates without requiring an interrupting alert or focus change.

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 status announcements?A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.role="status" communicates non-urgent updates without requiring an interrupting alert or focus change.

Apply it elsewhere

You reuse status announcements 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: Accessibility: Heading structure 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