Home›Quizzes›HTML & CSS Basics Quiz

HTML & CSS Basics Quiz

Developer Quiz

Test your HTML and CSS knowledge with 12 questions on the box model, semantic HTML, specificity, and flexbox. Get your score in about 3 minutes.

3 min · 12 questions

Question 1 of 12

What does HTML stand for?

HTML and CSS look simple on the surface, but concepts like the box model, specificity, and semantic markup quietly shape how reliably a page renders and how accessible it is. This 12-question quiz checks your grasp of these fundamentals. It takes about 3 minutes, with an explanation after every answer.

Once you've tested your knowledge, check your markup with the HTML Validator, or confirm a CSS property and value combination is valid with the CSS Property Validator.

Frequently Asked Questions

Each of the 12 questions has exactly one correct answer, and your final score is the number you got right out of 12. There's no partial credit, so read each option carefully.
No. The quiz runs entirely in your browser and nothing is sent to a server or stored. Refreshing the page resets your progress.
No, the questions cover foundational HTML and CSS concepts commonly taught early on, with explanations written to be understandable even if a concept is new to you.
Visually, a styled `<div>` and a semantic `<nav>` or `<article>` can look the same, but semantic elements carry meaning that screen readers, search engines, and other tools rely on — `<div>` conveys no information about the content's purpose.
The [HTML Validator](/html-validator/) checks your markup for structural errors and standards compliance, catching issues that might not be visually obvious but could cause inconsistent rendering.
The [CSS Property Validator](/css-property-validator/) checks whether a given CSS property and value combination is valid and correctly supported, which helps catch typos or unsupported syntax before they cause silent styling bugs.
Specificity involves a scoring system based on selector types (IDs, classes, elements) that isn't always intuitive, especially when multiple stylesheets or frameworks are involved — it often takes hands-on debugging experience to build a solid mental model of it.
Yes, any time — the questions stay the same, so it's a good way to confirm concepts like the box model and specificity have actually stuck.