Semantic HTML

Elements such as main, nav, article, button and heading elements communicate document structure to browsers, assistive technology and other software. In practical terms, Semantic HTML belongs to the browser, server or document layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use Semantic HTML as if it also meant HTML. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Choose elements for their meaning first; styling can still make semantic elements look however the design requires.

In day-to-day work, Semantic HTML matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

Using <main>, <nav>, <article> and real headings communicates document meaning more clearly than making every region a generic <div>. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.