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 misused headings, fake buttons, nested landmarks, and structural shortcuts. 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.
Field tip: for common semantic html mistakes, test both the ordinary path and the first case that makes your assumptions false.
Step by step
3 steps to follow
<div onclick="save()">Save</div><!-- replace with a real button -->
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.
<!-- Contrast the weak version --><div>Common Semantic HTML Mistakes used as a generic container</div>
Don't confuse browser-side convenience with a security boundary. The markup in common semantic html mistakes should improve behavior, but authoritative validation and policy belong at the trust boundary that processes the request.
<section aria-labelledby="topic-title"><h2 id="topic-title">Common Semantic HTML Mistakes</h2><p>Use the element that matches the content's meaning.</p></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.
When you debug this in a real project, inspect both the source and the parsed DOM. The two are related, but they are not always identical.
Engineering judgment: prefer the native HTML behavior described here before reaching for a custom widget.
Implementation note: Audit a flawed page and repair semantic errors without changing the visual design. Keep the browser behavior observable while you work.
Implementation note: Audit a flawed page and repair semantic errors without changing the visual design. Keep the browser behavior observable while you work.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.