21. Semantic HTML
Module 5 · About 20 minutes · Lesson 20; review earlier concepts as needed
Open Interactive LessonDiscover
What changes when you use semantic html, and how can you prove it?
- Explain semantic html using the example source
- Predict the visual or structural effect of one controlled change
- Repair the supplied fault and verify actual output
Predict
Record the expected structure or visual change before rendering. Name one thing that should remain unchanged.
Understand
Semantic elements describe purpose. main identifies the principal content; nav identifies navigation; article identifies a self-contained composition. A generic div remains appropriate when no more specific meaning applies. Do not select an element merely because its default display looks convenient. Review the landmark and heading outline together to understand the page.
Important source lines
- index.html:1 <main><h1>Field Notes</h1><article><h2>Designing a small page</h2><p>Start with the content.</p></article></main>
- The document’s principal content, normally one visible instance. Attribute guidance: id useful for skip links.
The first example teaches this lesson’s primary contract. Additional examples are optional related references or applications, each with its own purpose and source; an example without an authored check requires the stated visual/manual review.
Example 1: Semantic HTML
A self-contained article is placed inside the principal content landmark.
index.html
<main><h1>Field Notes</h1><article><h2>Designing a small page</h2><p>Start with the content.</p></article></main>
styles.css
script.js
Expected: A self-contained article is placed inside the principal content landmark.
Edit and Render This ExampleExample 2: Element: article
An independently meaningful composition.
index.html
<article><h2>Layout field note</h2><p>This note stands on its own.</p><footer>By Alex</footer></article>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: An independently meaningful composition. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 3: Element: h2
A second-level heading for a major subsection.
index.html
<h1>Handbook</h1><section><h2>Getting started</h2><p>A named section.</p></section>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: A second-level heading for a major subsection. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 4: Element: h1
The highest-level heading for a page topic.
index.html
<h1>Workshop handbook</h1><p>A principal heading introduces the page.</p>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: The highest-level heading for a page topic. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleExample 5: Element: p
A paragraph of prose.
index.html
<p>One idea belongs in a coherent paragraph.</p><p>A second paragraph develops another idea.</p>
styles.css
body { font:18px/1.6 system-ui; margin:1.5rem; color:#17324d; } img,video,svg { max-width:100%; height:auto; } th,td { padding:.5rem; border:1px solid #a8b8c8; } :focus-visible { outline:3px solid #a44322; outline-offset:3px; }script.js
Expected: A paragraph of prose. Review its real DOM and native behavior; structural/media-only examples are labeled.
Edit and Render This ExampleBuild and test
A self-contained article is placed inside the principal content landmark. Repair the current exercise without removing necessary content. Checks inspect the stated structural/computed/stylesheet contract, not exact source text.
Starter index.html
<main><h1>Field Notes</h1><div><h2>Designing a small page</h2><p>Start with the content.</p></article></main>
Starter styles.css
Objective contract
[
{
"type": "count",
"selector": "main article",
"value": 1,
"label": "Include 1 matching main article element(s)"
}
]Hint 1
Locate the first difference between the intended result and the real preview. Inspect matching elements and computed styles.
Hint 2
The relevant source uses <article>. The exercise instead uses <div>. Identify its effect before changing it.
Hint 3
Restore the intended <article> operation or implement an equivalent structure/style. Run the actual checks and explain why it works.
Complete reference solution
index.html
<main><h1>Field Notes</h1><article><h2>Designing a small page</h2><p>Start with the content.</p></article></main>
styles.css
Explain, reflect and extend
Which part of the actual preview or inspector proves this result? Explain one boundary case and name what automated checks do not verify.
Apply this concept to a different realistic piece of content. Predict its structure or visual behavior, test narrow and wide widths where relevant, then record one invalid case and its repair.
Troubleshooting and professional practice
If nothing changes, confirm that you edited the active file and ran Run Preview, or enabled Auto Preview. Inspect the actual DOM because the browser may repair invalid nesting. For CSS, check selector matches, valid declarations, active queries and computed values. Preserve local asset paths and inspect warnings. A self-contained article is placed inside the principal content landmark.
Knowledge check
Explain why the stated result follows from the source. Predict a second input or width and test it independently. Automated contracts and written explanations are reviewed separately.
Optional AI prompts
- Explain this lesson’s source line by line using the actual objective above.
- Help implement one small extension and define normal, boundary and failure tests.
- Review/debug the source against actual preview observations; verify standards and never claim rendering without evidence.