A long unsegmented block drops reading completion

What it is

A block that fills a screen or several screens with no place to breathe is a wall of text. People can read it. They often decide not to finish. Completion here is the share who reach the end or reach an action, not literacy. Paragraphs cut the wall into pausable chunks. Without those chunks, the only pause left is leaving.

Why it happens

Working memory holds a limited number of propositions at once. A paragraph’s job is to bound that set: finish a chunk, close it, decide whether to take the next. A wall removes the bound, so the reader has to find footholds inside a continuous sentence stream, and the cognitive ledger is spent on “where am I” rather than on content. Screens deter more than paper: scroll position is the only progress bar, a wall barely moves that bar, progress vanishes, and leaving looks cheaper than continuing. Links and buttons buried mid-wall cannot be scanned as action points, so the task is abandoned before reading starts. The loss is completion and action, not ugly type.

Studying it

Give one text two versions, paragraphed and not; hold length, size, and measure, vary only the breaks. The task can be read-then-answer, or find-and-do an action named in the copy. Dependent measures: completion rate, scroll depth at abandon, answer accuracy, time to the action. On screens, log leaving; forcing a laboratory finish washes out the main effect, which is choosing not to read. Split by device: the same wall is abandoned earlier on a phone than on a desktop.

Where it stops holding

Legal full text, academic paragraphs, and stream-of-consciousness fiction come with a different completion contract, so the deterrent weakens — but interface help, policies, and error reasons still run on the interface contract. Experts who have already committed to close reading will segment for themselves. Spoken playback linearizes the wall; completion then follows duration and structural announcements, and visual breaks do not help. A three-to-five-line “wall” will not show a completion gap. The claim is about blocks that take scrolling to finish.

Applying it

• Cut help, policy, empty states, and error detail to one proposition per paragraph. Do not pack five conditions into one block.
• In product analytics, if scroll depth on these pages dies on the first screen with no click, inspect for a wall before rewriting the argument.
• Put the sentence that demands action in its own short paragraph. Do not bury it mid-wall.

Related

• Same group: F4.13.1 Paragraph spacing must exceed leading or the break cannot be seen · F4.13.2 First-line indent and a blank between paragraphs are mutually exclusive conventions · F4.13.4 Paragraph spacing should track leading, not a fixed pixel value
• Nearby: F4.08 Legibility and readability · F4.03 Measure
• Search terms: wall of text · reading completion · paragraph chunking