A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
In production, this piece of HTML is rarely isolated; it sits between content, navigation, user input, and browser defaults. In this lesson, the focus is mixed images, video, captions, and accessible alternatives. 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.
<figure><img src="project.webp" alt="Checkout flow on mobile"><figcaption>Checkout redesign.</figcaption></figure>
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.
Implementation note: Use media elements where they add evidence to the portfolio rather than turning the page into a gallery of decoration. Keep the browser behavior observable while you work.
Don't confuse browser-side convenience with a security boundary. The markup in creating a media-rich portfolio should improve behavior, but authoritative validation and policy belong at the trust boundary that processes the request.
<video controls autoplay><source src="intro.mp4" type="video/mp4"></video>
Now put the same idea under pressure. A realistic failure is: Use media elements where they add evidence to the portfolio rather than turning the page into a gallery of decoration. 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.
<video controls preload="metadata"><source src="intro.webm" type="video/webm"><source src="intro.mp4" type="video/mp4"><track kind="captions" src="en.vtt" srclang="en" label="English"></video>
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.
Source-reading note: the exact semantics here come from the HTML element/attribute you chose, not its CSS appearance.
Checkpoint: you can now connect the markup for creating a media-rich portfolio to a browser behavior and a concrete debugging step.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.