A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Implementation note: Audit content from both human and machine perspectives and resolve the same root cause wherever possible. Keep the browser behavior observable while you work.
Field tip: for production accessibility and seo audits, test both the ordinary path and the first case that makes your assumptions false.
You'll get more mileage from this topic by asking what information the markup communicates than by memorizing every attribute. In this lesson, the focus is joint audits using document structure, metadata, links, and interaction checks. 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.
| 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. |
<main><h1>Pricing</h1><p>...</p><a href="/signup">Start free trial</a></main>
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.
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.
<button type="button" aria-expanded="false" aria-controls="filters">Filters</button><section id="filters" hidden>...</section>
In a team codebase, the expensive bugs usually come from assumptions. Someone assumes an anchor is just a button with a different visual style, that a placeholder is a label, that an iframe is only a rectangle, or that a client-side constraint is security. The safe engineering move is to name the browser behavior you actually depend on and encode it directly in HTML.
Source-reading note: the exact semantics here come from the HTML element/attribute you chose, not its CSS appearance.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.