Capstone builds · Lesson 5 of 8 · 7 minutes

Capstone builds: Service status page

Status needs a readable state, an observation time, and context that distinguishes an incident from an assumption.

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 service status page
Build this first target: <main>; <h1> inside <main> containing “Training service status”; <p> inside <main> (role="status") containing “Degraded: search is delayed.”. Inspect the structure before checking the lesson.
Hint & worked example
Status needs a readable state, an observation time, and context that distinguishes an incident from an assumption.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<main><h1>Training service status</h1><p role="status">Degraded: search is delayed.</p></main>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the service status page example
Extend your file to include: <main>; <h1> inside <main> containing “Training service status”; <p> inside <main> (role="status") containing “Degraded: search is delayed.”; <p> inside <main> containing “Updated .”; <time> inside <p> (datetime="2026-09-06T10:00:00Z") containing “10:00 UTC”. Inspect the structure before checking the lesson.
Hint & worked example
Status needs a readable state, an observation time, and context that distinguishes an incident from an assumption.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<main><h1>Training service status</h1><p role="status">Degraded: search is delayed.</p><p>Updated <time datetime="2026-09-06T10:00:00Z">10:00 UTC</time>.</p></main>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete service status page pattern
Finish the pattern with: <main>; <h1> inside <main> containing “Training service status”; <p> inside <main> (role="status") containing “Degraded: search is delayed.”; <p> inside <main> containing “Updated .”; <time> inside <p> (datetime="2026-09-06T10:00:00Z") containing “10:00 UTC”; <section> inside <main>; <h2> inside <section> containing “Known impact”; <p> inside <section> containing “Existing saved reports remain readable.”. Inspect the structure before checking the lesson.
Hint & worked example
Status needs a readable state, an observation time, and context that distinguishes an incident from an assumption.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<main><h1>Training service status</h1><p role="status">Degraded: search is delayed.</p><p>Updated <time datetime="2026-09-06T10:00:00Z">10:00 UTC</time>.</p><section><h2>Known impact</h2><p>Existing saved reports remain readable.</p></section></main>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

Status needs a readable state, an observation time, and context that distinguishes an incident from an assumption.

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

<main><h1>Training service status</h1><p role="status">Degraded: search is delayed.</p><p>Updated <time datetime="2026-09-06T10:00:00Z">10:00 UTC</time>.</p><section><h2>Known impact</h2><p>Existing saved reports remain readable.</p></section></main>

Status needs a readable state, an observation time, and context that distinguishes an incident from an assumption.

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 service status page?Status needs a readable state, an observation time, and context that distinguishes an incident from an assumption.A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.

Apply it elsewhere

You reuse service status page 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: Capstone builds: Resource directory 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