Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallSemantic HTML means choosing elements for what their content is, not merely for how it should look. Use elements such as <main>, <nav>, <article>, <aside> and <section> to express a document’s structure; use CSS to control its appearance.
What semantic HTML communicates
An element is semantic when its name and role describe the meaning or purpose of its content. A navigation menu belongs in <nav>; the page’s dominant content belongs in <main>. A generic <div>, by contrast, groups content without assigning it a particular document role.
As an Amazon Associate I earn from qualifying purchases.
Semantics give browsers and assistive technologies structural information, and make the markup easier for people to understand and maintain. They do not dictate visual design: CSS can style semantic elements just as it can style generic containers. The WHATWG HTML Living Standard is the normative reference; MDN’s HTML elements reference is a practical guide.
How to choose between article, section and aside
Start by asking whether the content can stand on its own, whether it is central or supporting, and whether a more specific element already describes it.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
| Element | Use it for | Example |
|---|---|---|
<article> |
A self-contained composition that could make sense independently. | A blog post, news story or comment. |
<section> |
A meaningful, thematic grouping within a document when no more specific element fits. | A headed chapter or topic within a longer guide. |
<aside> |
Content related to the surrounding material but not part of its main flow. | A related-links box or author biography. |
Choose article for independent content
Use <article> when the content forms a distinct composition that could be distributed or understood on its own. A page may contain an article, and an article may contain sections that organize its internal topics.
Choose section for a meaningful grouping
Use <section> when you are grouping related content as a distinct part of a document and no more specific element applies. In ordinary use, give a section a heading so its subject is clear. Do not use it for every box or layout region; use <div> when a grouping has no special semantic purpose.
Choose aside for tangential support
Use <aside> for material that complements the surrounding content rather than carrying its central thread. If the material is essential to the main explanation, it may belong in the main flow instead.
What the other structural elements do
Main identifies the dominant content
<main> identifies the document’s dominant content. The WHATWG defines it this way: “The main element represents the dominant content of the body of a document.” A document must not have more than one <main> without the hidden attribute. See MDN’s main element reference.
Rank #3
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Nav marks navigation
Use <nav> for a section whose purpose is navigation, such as a site menu, table of contents or index. Not every group of links is navigation; choose the element based on the links’ purpose.
Header and footer mark introductory and closing material
<header> and <footer> can belong to the page as a whole or to their nearest relevant sectioning ancestor. They are not restricted to one global header and footer per document.
Headings express hierarchy
Use headings from <h1> through <h6> to label and organize sections according to their hierarchy. Choose a heading level for its place in the document, not as a shortcut for a particular font size; CSS controls sizing.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A practical decision process
- Identify the content’s purpose. Is it the dominant content, navigation, a standalone composition, tangential support, or a meaningful topic grouping?
- Choose the most specific fitting element. For example, use
<nav>for navigation rather than a generic container. - Use section only for a real document grouping. Give it a heading in ordinary use; do not use it solely to create a styling hook.
- Use a generic container when no semantic role applies. A
<div>is appropriate when you need a wrapper for layout or styling without implying a document role. - Style the result with CSS. Let semantics describe the content and CSS determine its appearance.
For example, a guide page might place its main article inside <main>, use <article> for the guide itself, divide the guide into headed <section> elements, and put related resources in an <aside>. A site-wide menu belongs in <nav>. The exact nesting depends on what each part represents, not on how many boxes the design contains.
Why semantic structure matters for accessibility
Structural elements can expose implicit landmark regions that help assistive-technology users find major parts of a page. The W3C WAI H101 technique gives semantic elements such as <main> and <nav> as examples of ways to identify page regions. It is a technique example, not a complete accessibility checklist.
Landmarks work best alongside a coherent heading hierarchy and link text that describes its destination. Semantic HTML contributes useful navigation cues, but using structural elements alone does not make every aspect of a page accessible. MDN’s document-structure learning material explains how headings and landmarks help users navigate content.
Common semantic HTML mistakes
- Using section as a universal wrapper: choose it for a meaningful document grouping, not simply because a block needs styling.
- Confusing independence with grouping: use
<article>for a composition that can stand alone; use<section>for a distinct part of a larger document. - Treating aside as a visual sidebar: its meaning is tangential supporting content, not its position on the screen.
- Using headings for visual size: select heading levels by document hierarchy and adjust appearance with CSS.
- Assuming semantics guarantee accessibility: landmarks and headings help, but their value depends on appropriate use and a clear structure.
Where to check element details
For normative definitions and behavior, consult the WHATWG HTML Living Standard. For quick element-by-element explanations, use MDN’s HTML elements reference, including its entries for section and main.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
