Foxipa
/
HTML
/
HTML Exercises
/
HTML Quiz Exercises
/
Test your knowledge: Paragraphs

Quiz

Test your knowledge: Paragraphs

A short assessment covering whitespace collapsing, paragraph content rules, and common mistakes with the HTML p element.

6 questions ~3 min Beginner

Quizzes

Test your knowledge: Paragraphs
Test your knowledge: HTML Headings
Test your knowledge: HTML Foundations

Knowledge check

Test your knowledge: Paragraphs

A short assessment covering whitespace collapsing, paragraph content rules, and common mistakes with the HTML p element.

Stuck? Each question has an optional hint.
Skip a hard question and review it before your results.
Questions and answer options can shuffle between attempts.

You can retake this quiz whenever you like.

0:00

Question 1 of 6

What happens to extra spaces and line breaks inside a `` element by default?

The browser treats a run of whitespace as a boundary to normalize, not as content to preserve exactly.

Answer options A They render exactly as written B They collapse into a single space C They are stripped out entirely, leaving no space D Only line breaks collapse; extra spaces stay

Default HTML whitespace handling collapses any run of spaces, tabs, and line breaks into one space. Changing that requires CSS (white-space) or <pre>, not a different element.

Review this lesson

Question 2 of 6

What’s generally the better way to separate two distinct ideas in body text?

Which one gets vertical margin for free from the browser, with zero CSS written?

Answer options A Two tags back to back B A single C Two separate elements D A <div> placed between them

carries real meaning and gets margin for free from the browser. Stacking tags to fake that spacing is one of the most common misuses of the element.

Review this lesson

Question 3 of 6

What does a browser actually do if a <div> appears inside an open ?

The parser can’t truly nest a block element inside phrasing-only content — something in the DOM tree has to give.

Answer options A It throws a parsing error and stops rendering B It nests the <div> inside the , exactly as written C The parser silently closes the right before the <div> D The <div> is dropped and its content discarded

can only contain phrasing content. Hitting a block-level element auto-closes the paragraph — the page still renders, but your DOM tree isn’t what the markup implied.

Review this lesson

Question 4 of 6

Why can reader-mode tools segment -separated text poorly?

Think about what a screen reader’s “read from here” command actually needs to find in the markup.

Answer options A tags are invisible to their parsers B They rely on block-level boundaries like to find stopping points C is deprecated and unsupported in modern browsers D Reader mode only recognizes <div> elements

Reading tools segment content by block-level elements. A wall of text broken only by gives them no real boundaries to work with.

Review this lesson

Question 5 of 6

Which of these is not valid content directly inside a ?

Phrasing content only — would this element still make sense sitting mid-sentence?

Answer options A bold text B <a href="#">a link</a> C <ul><li>a list item</li></ul> D <code>inline code</code>

only accepts phrasing content — inline elements like , <a>, and <code>. <ul> is block-level, so it can’t nest inside.

Review this lesson

Question 6 of 6

What’s the main problem with empty tags used purely for vertical spacing?

Ask where spacing decisions belong: in the content itself, or in how it’s styled?

Answer options A It’s invalid HTML and the page won’t render B It conflates presentation with structure — that spacing belongs in CSS margin C Screen readers announce the word "paragraph" for each one D Browsers automatically strip empty paragraphs, so it has no effect

An empty is markup doing a layout job. The fix is margin on real content, not structural tags with nothing in them.

Review this lesson

Quiz results

0/0

Review

What happens to extra spaces and line breaks inside a  element by default?
Default HTML whitespace handling collapses any run of spaces, tabs, and line breaks into one space. Changing that requires CSS (white-space) or <pre>, not a different element.
What’s generally the better way to separate two distinct ideas in body text?
 carries real meaning and gets margin for free from the browser. Stacking tags to fake that spacing is one of the most common misuses of the element.
What does a browser actually do if a <div> appears inside an open ?
 can only contain phrasing content. Hitting a block-level element auto-closes the paragraph — the page still renders, but your DOM tree isn’t what the markup implied.
Why can reader-mode tools segment -separated text poorly?
Reading tools segment content by block-level elements. A wall of text broken only by gives them no real boundaries to work with.
Which of these is not valid content directly inside a ?
 only accepts phrasing content — inline elements like , <a>, and <code>. <ul> is block-level, so it can’t nest inside.
What’s the main problem with empty tags used purely for vertical spacing?
An empty is markup doing a layout job. The fix is margin on real content, not structural tags with nothing in them.

Back to lesson

Test your knowledge: Paragraphs

Test your knowledge: Paragraphs

What happens to extra spaces and line breaks inside a `<p>` element by default?

What’s generally the better way to separate two distinct ideas in body text?

What does a browser actually do if a <div> appears inside an open <p>?

Why can reader-mode tools segment <br>-separated text poorly?

Which of these is not valid content directly inside a <p>?

What’s the main problem with empty <p></p> tags used purely for vertical spacing?

Review

Test your knowledge: Paragraphs

Test your knowledge: Paragraphs

What happens to extra spaces and line breaks inside a <p> element by default?

What’s generally the better way to separate two distinct ideas in body text?

What does a browser actually do if a <div> appears inside an open <p>?

Why can reader-mode tools segment <br>-separated text poorly?

Which of these is not valid content directly inside a <p>?

What’s the main problem with empty <p></p> tags used purely for vertical spacing?

Quiz results

Review

What happens to extra spaces and line breaks inside a `<p>` element by default?