A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Treat the markup here as a contract with the browser. The more precisely you express the contract, the less repair work the browser has to invent. In this lesson, the focus is article, aside, figure, and figcaption in content relationships. 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.
Source-reading note: the exact semantics here come from the HTML element/attribute you chose, not its CSS appearance.
<article><h1>Incident review</h1><figure><img src="graph.svg" alt="Latency by hour"><figcaption>Peak latency at 14:00.</figcaption></figure></article>
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.
Don't confuse browser-side convenience with a security boundary. The markup in articles, aside, and figure elements should improve behavior, but authoritative validation and policy belong at the trust boundary that processes the request.
<!-- Contrast the weak version --><div>Articles, Aside, and Figure Elements used as a generic container</div>
Now put the same idea under pressure. A realistic failure is: Model primary content, tangential material, and self-contained media correctly. 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.
<section aria-labelledby="topic-title"><h2 id="topic-title">Articles, Aside, and Figure Elements</h2><p>Use the element that matches the content's meaning.</p></section>
For this topic, the edge case is worth remembering: HTML has legacy parsing and compatibility behavior, so invalid markup does not always fail loudly. If you are debugging a strange result, reduce the page to one element at a time, validate the source, and inspect the resulting DOM. Small reproductions beat guessing at the full application.
Keep the markup close to the meaning of the content. Future CSS and JavaScript changes then have a stable surface to work against.
Checkpoint: you can now connect the markup for articles, aside, and figure elements to a browser behavior and a concrete debugging step.
Warning: invalid or overly permissive markup may still render. Rendering is not proof that the document model is correct.
Warning: invalid or overly permissive markup may still render. Rendering is not proof that the document model is correct.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.