Learning overview
- Estimated time
- 4 minutes
- Difficulty
- Intermediate
- Prerequisites
- Learn HTML: From First Page to Semantic Websites · HTML Tutorial: Build a Complete Semantic Web Page
- Learning outcome
- Explain html using a clear mental model · Apply html in practical HTML work
- Last updated
- July 18, 2026
Core answer
HTML describes the structure and meaning of web content. A strong interview answer connects element choice to browser behavior, accessibility APIs, form submission, navigation, search interpretation, or loading behavior.
Semantic HTML means choosing elements according to content purpose. A button performs an action, an anchor navigates, a heading names a section, and a label names a form control. Native semantics usually provide keyboard and assistive-technology support that a generic div does not.
The head contains document metadata such as character encoding, viewport settings, title, description, resource links, and selected machine-readable information. The body contains the document users consume and interact with.
Worked example
An interviewer may ask why a button is better than a clickable div. The answer is visible in the amount of behavior HTML provides natively.
<button type="button" aria-expanded="false" aria-controls="filters">
Show filters
</button>
<section id="filters" hidden>
<!-- filter controls -->
</section>Follow-up questions
Strong interviews test whether you can apply the idea, not only recite a definition. Practice answering these out loud.
- What is the difference between semantic HTML and ARIA?
- When should alt text be empty?
- Why must labels remain visible instead of relying on placeholders?
- What happens when a browser encounters invalid nesting?
- How do async and defer change script execution?
- When would you use picture, srcset, or sizes?
- What is the difference between section and article?
- How would you test a page using only a keyboard?
- Why do image dimensions help prevent layout shift?
- What information belongs in the document head?
Frequently asked questions
How should I answer semantic HTML questions?
State the element’s purpose, describe the native behavior or role it provides, and give a concrete example where that behavior benefits users or maintainers.
Should I memorize every HTML element?
Know common document, text, media, table, and form elements well. For uncommon elements, demonstrate that you can verify semantics in standards-based documentation.
Are HTML interviews only about syntax?
No. Strong interviews cover accessibility, browser parsing, forms, responsive images, metadata, performance, and the reasoning behind element choices.
Topic graph
A taxonomy-generated path through this subject.
Related courses
Related learning
Recommended automatically from shared technologies, topics, intent, and difficulty.
Related Guides
Related Tutorials
Related Glossary
Related Cheatsheets
Related Projects
Related Interview Questions
Related reading
Hand-picked companion pages that deepen this topic.
Your next steps