Semantic structure · Lesson 8 of 10 · 10 minutes

Semantic structure: Contact information

address marks contact information for its nearest article or body, not every postal address mentioned in text.

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 contact information
Build this first target: <article>; <h1> inside <article> containing “Workshop notes”. Inspect the structure before checking the lesson.
Hint & worked example
address marks contact information for its nearest article or body, not every postal address mentioned in text.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<article><h1>Workshop notes</h1></article>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.
2
Extend the contact information example
Extend your file to include: <article>; <h1> inside <article> containing “Workshop notes”; <address> inside <article> containing “Prepared by the library team.”. Inspect the structure before checking the lesson.
Hint & worked example
address marks contact information for its nearest article or body, not every postal address mentioned in text.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<article><h1>Workshop notes</h1><address>Prepared by the library team.</address></article>
```
Common mistake to avoid: Replacing semantic elements with generic divs automatically improves accessibility.
3
Verify the complete contact information pattern
Finish the pattern with: <article>; <h1> inside <article> containing “Workshop notes”; <address> inside <article> containing “Prepared by the library team. Contact the front desk.”; <p> inside <article> containing “The event takes place in Room 2.”. Inspect the structure before checking the lesson.
Hint & worked example
address marks contact information for its nearest article or body, not every postal address mentioned in text.
The requested elements, attributes, content, and hierarchy exist outside comments.
```
<article><h1>Workshop notes</h1><address>Prepared by the library team. Contact the front desk.</address><p>The event takes place in Room 2.</p></article>
```
Common mistake to avoid: A visual appearance alone guarantees the intended HTML meaning.

Understand the pattern

address marks contact information for its nearest article or body, not every postal address mentioned in text.

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

<article><h1>Workshop notes</h1><address>Prepared by the library team. Contact the front desk.</address><p>The event takes place in Room 2.</p></article>

address marks contact information for its nearest article or body, not every postal address mentioned in text.

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 contact information?address marks contact information for its nearest article or body, not every postal address mentioned in text.A visual appearance alone guarantees the intended HTML meaning.Replacing semantic elements with generic divs automatically improves accessibility.

Apply it elsewhere

You reuse contact information 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: Semantic structure: Nested heading 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