A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
“When this goes wrong, the browser usually keeps rendering. That is what makes the bug easy to miss: recovery can hide a broken source document. In this lesson, the focus is anchors, destinations, fragments, downloads, and navigation semantics. That matters because HTML is interpreted by a parser and then exposed to browser features such as navigation, accessibility tooling, form controls, media handling, and script APIs. A correct-looking screenshot can still hide a poor document model.”
Start with the smallest meaningful example. The working snippet demonstrates the core syntax, but the important part is what each piece contributes: the element supplies semantics or behavior, attributes refine that meaning, and surrounding structure gives the browser context. Don't add markup just because a framework or copied example happens to include it.
| Decision | Why it matters |
|---|---|
| Native element | Carries browser semantics and default behavior. |
| Attribute | Refines the element without replacing its meaning. |
| CSS/JS hook | Adds presentation or behavior around the existing structure. |
Implementation note: Build primary navigation and an in-page table of contents while keeping link text meaningful. Keep the browser behavior observable while you work.
<nav><a href="/products">Products</a><a href="#faq">FAQ</a></nav>
Now put the same idea under pressure. A realistic failure is: Build primary navigation and an in-page table of contents while keeping link text meaningful. The browser may recover, ignore an invalid combination, or leave the user with a control that appears visually fine but behaves differently than expected. That is why source inspection and keyboard testing belong in the workflow.
<a href="docs/start.html">Start</a><!-- On /products/2026/, this resolves differently than /docs/start.html. -->
The browser's defaults are part of the behavior you are learning. Prefer native semantics first, then test the exact combination of attributes and content you plan to ship.
You can now explain the browser behavior behind anchors, destinations, fragments, downloads, and navigation semantics, build the markup deliberately, and diagnose the most common failure mode instead of guessing.
Checkpoint: you can now connect the markup for links and navigation to a browser behavior and a concrete debugging step.
Field tip: for links and navigation, test both the ordinary path and the first case that makes your assumptions false.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.