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 picture art direction, source media queries, and type selection. 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.
Checkpoint: you can now connect the markup for picture and source elements to a browser behavior and a concrete debugging step.
<picture><source media="(max-width: 600px)" srcset="portrait.jpg"><img src="landscape.jpg" alt="Team at work"></picture>
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.
<!-- Contrast the weak version --><div>Picture and Source Elements used as a generic container</div>
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.
<section aria-labelledby="topic-title"><h2 id="topic-title">Picture and Source 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.
You can now explain the browser behavior behind picture art direction, source media queries, and type selection, build the markup deliberately, and diagnose the most common failure mode instead of guessing.
Field tip: for picture and source elements, test both the ordinary path and the first case that makes your assumptions false.
Implementation note: Use picture when the image itself needs to change, not merely because you can add another URL. Keep the browser behavior observable while you work.
Implementation note: Use picture when the image itself needs to change, not merely because you can add another URL. Keep the browser behavior observable while you work.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.