Accessibility · Lesson 3 of 8 · 7 minutes

Accessibility: Landmark labels

Distinct names help people differentiate multiple navigation landmarks.

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 landmark labels
Build this first target: <nav> (aria-label="Primary"); <a> inside <nav> (href="/web/") containing “Web”. Inspect the structure before checking the lesson.
Hint & worked example
Distinct names help people differentiate multiple navigation landmarks.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<nav aria-label="Primary"><a href="/web/">Web</a></nav>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the landmark labels example
Extend your file to include: <nav> (aria-label="Primary"); <a> inside <nav> (href="/web/") containing “Web”; <nav> (aria-label="This lesson"); <a> inside <nav> (href="#practice") containing “Practice”. Inspect the structure before checking the lesson.
Hint & worked example
Distinct names help people differentiate multiple navigation landmarks.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<nav aria-label="Primary"><a href="/web/">Web</a></nav><nav aria-label="This lesson"><a href="#practice">Practice</a></nav>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete landmark labels pattern
Finish the pattern with: <nav> (aria-label="Primary"); <a> inside <nav> (href="/web/") containing “Web”; <nav> (aria-label="This lesson"); <a> inside <nav> (href="#practice") containing “Practice”; <main> (id="practice"); <h1> inside <main> containing “Landmark practice”. Inspect the structure before checking the lesson.
Hint & worked example
Distinct names help people differentiate multiple navigation landmarks.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<nav aria-label="Primary"><a href="/web/">Web</a></nav><nav aria-label="This lesson"><a href="#practice">Practice</a></nav><main id="practice"><h1>Landmark practice</h1></main>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

Distinct names help people differentiate multiple navigation landmarks.

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

<nav aria-label="Primary"><a href="/web/">Web</a></nav><nav aria-label="This lesson"><a href="#practice">Practice</a></nav><main id="practice"><h1>Landmark practice</h1></main>

Distinct names help people differentiate multiple navigation landmarks.

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 landmark labels?A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.Distinct names help people differentiate multiple navigation landmarks.

Apply it elsewhere

You reuse landmark labels 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: Keyboard order 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