Proper Stops and Pagination: Why Spaces and Empty Lines Ruin Accessibility

Sound familiar? You want to create space between two paragraphs, so you simply hit Enter a few times in a row, until the spacing "looks good" on screen. Or you want to center a line, so you add a few spaces before it until it "sits" in the middle. Both of these habits look completely harmless visually — and are one of the most common reasons screen readers read documents in a strange and confusing way.

Why space characters "break" reading aloud

A screen reader doesn't "see" white space on the screen — it reads characters. An empty line created by an extra Enter press is read out as "empty paragraph," and sometimes repeats several times if there are several Enters in a row. Using repeated spaces (for example, for manual indentation or centering) can sound like "space, space, space" or simply be silenced entirely — depending on the software. In the worst case, using repeated dots or dashes to create a visual "separator line" is read out word by word: "dot, dot, dot, dot..." — an exhausting experience for a user who just wants to know there's a separation between two parts.

The correct alternative: paragraph properties

Every serious editing program — Word, Acrobat, website editors — has a dedicated field for spacing: "Space Before" and "Space After" (in Word: the Layout tab ▸ Paragraph, or opening the full Paragraph properties window). Spacing set this way is a formatting property of the paragraph itself — a screen reader simply moves on to the next paragraph without announcing anything extra, exactly how spacing between paragraphs is supposed to feel: invisible and unobtrusive.

The same principle in tables and lists

The same mistake shows up when creating fake "tables" with tabs or multiple spaces (instead of a real table), and when creating lists with a manually typed dash or asterisk (instead of the built-in numbered/bulleted list tool). In both cases, the structure a screen reader receives is "random text with a lot of odd spacing" — instead of real semantic structure (table, list) that it knows how to navigate in an orderly way.

How to fix an existing document

The most effective fix is usually in the source document: delete the manual "padding" lines/spaces, and in their place set spacing before/after in the paragraph settings or in the Style applied to all paragraphs of that type — that way the fix applies automatically to the entire document at once, not just to the single spot that was fixed.