HTML basics · Lesson 3 of 12 · 7 minutes

HTML basics: Heading hierarchy

Heading levels describe nested sections, not a choice of font size.

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 heading hierarchy
Build this first target: <h1> containing “Workshop handbook”. Inspect the structure before checking the lesson.
Hint & worked example
Heading levels describe nested sections, not a choice of font size.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<h1>Workshop handbook</h1>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the heading hierarchy example
Extend your file to include: <h1> containing “Workshop handbook”; <h2> containing “Before you arrive”. Inspect the structure before checking the lesson.
Hint & worked example
Heading levels describe nested sections, not a choice of font size.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<h1>Workshop handbook</h1>
<h2>Before you arrive</h2>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete heading hierarchy pattern
Finish the pattern with: <h1> containing “Workshop handbook”; <h2> containing “Before you arrive”; <h3> containing “What to bring”; <p> containing “A charged laptop.”. Inspect the structure before checking the lesson.
Hint & worked example
Heading levels describe nested sections, not a choice of font size.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<h1>Workshop handbook</h1>
<h2>Before you arrive</h2>
<h3>What to bring</h3>
<p>A charged laptop.</p>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

Heading levels describe nested sections, not a choice of font size.

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

<h1>Workshop handbook</h1>
<h2>Before you arrive</h2>
<h3>What to bring</h3>
<p>A charged laptop.</p>

Heading levels describe nested sections, not a choice of font size.

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 heading hierarchy?A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.Heading levels describe nested sections, not a choice of font size.

Apply it elsewhere

You reuse heading hierarchy 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: HTML basics: Readable paragraphs 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