Four words explain a surprising share of what separates a document that reads easily from one that doesn’t: contrast, repetition, alignment, proximity. Designer Robin Williams built this framework around an unfortunate but memorable acronym in a book aimed at people who had never studied design, and the underlying document design principles still hold up on pages nobody thinks of as designed at all, a report, a memo, a government form.
Document design principles: four forces worth naming
Contrast means using real difference, not a slight variation, to draw a reader’s eye somewhere on purpose. A heading that is only a few points larger than the body text barely functions as a heading at all; a heading that is clearly bigger, or bold against a lighter body, announces the structural break instantly, without asking a reader to work for it. The same logic applies to color, weight and spacing: a small, tasteful difference often reads as no difference at all, and a document benefits from contrast being obvious rather than subtle.
Repetition means the same formatting choices recurring consistently throughout a document: the same heading style every time a new section starts, the same spacing after a table, the same treatment for a callout or a citation. A reader’s eye learns the pattern once, early in the document, and reads faster for the rest of it, because it no longer has to work out what a formatting choice means each time it reappears. A document that changes its heading style halfway through forces that learning to happen twice.
Alignment means every element sits on a deliberate line rather than scattered wherever it happened to land during drafting. Even a small, nearly invisible misalignment, a caption a few pixels off from the image it describes, a paragraph indented slightly differently than the one above it, reads as disorganized without most readers ever consciously identifying why. A clean underlying grid, even an informal one, removes that friction before a reader notices it exists.
Proximity means grouping related items close together and putting real distance between items that are not related. Physical closeness on a page reads as a relationship whether or not the writer intended one: a caption placed slightly closer to the wrong image, or a footnote sitting ambiguously between two paragraphs, creates confusion purely through spacing, independent of what the words themselves say.
These four rarely operate in isolation. A table with a bold header row (contrast) that repeats the identical bold treatment on every table in the document (repetition), with every column aligned to a consistent grid (alignment) and its caption sitting directly beneath it rather than floating somewhere nearby (proximity), reads as a single coherent object. Strip away just one of the four, misalign the columns, say, while leaving the header bold and the caption close, and the table still looks subtly wrong, even to a reader who could not name which of the four principles had been dropped. That is part of why the framework holds up decades after it was first written down for non-designers: the principles are easiest to notice by their absence, not their presence, which makes them a useful thing to check for specifically rather than to trust a document has by default.
Why white space is doing more work than it looks like
A dense, margin-to-margin page looks intimidating before a reader has read a single word of it, and that first impression matters more than most writers assume. Generous margins, a real gap between sections, and a paragraph that is allowed to end early rather than being stretched to fill out a line, all signal to a reader that the document respects their effort and their attention. Cramming more text onto a page rarely saves real reading time. It usually just moves the cost from the page count onto the reader’s patience, and a reader who feels that cost early often skims harder, or skips entirely, exactly the sections a writer worked hardest on.
White space also does a quieter structural job: it separates. A gap between two sections functions the same way a heading does, telling a reader’s eye that one idea has ended and another is starting, often before the reader has consciously processed the heading text itself. Removing that gap to save room usually costs more clarity than the saved space is worth.
The instinct to fill every available inch of a page is understandable, especially under a length limit or a printing-cost constraint, but it trades a real cost for an imagined one. The imagined cost is a longer document; the real cost is a reader who disengages before reaching the second half of it. A four-page report with generous margins that gets read in full has done its job better than a three-page report, crammed to the edges, that gets abandoned halfway through.
Readability: plain language alongside plain layout
Visual design solves only half the readability problem; the words themselves are the other half. The United States passed the Plain Writing Act in 2010, requiring federal agencies to write public-facing documents in language ordinary readers can actually understand on a first read, a legal requirement rather than a style suggestion. Shorter sentences, familiar words instead of jargon, and a document that states its point before qualifying it all serve the exact same underlying goal that contrast and white space serve visually: getting a reader to the actual content with less friction standing between them and it. A beautifully laid-out document full of dense, jargon-heavy prose still reads slowly; a plainly written document crammed onto a cluttered page still reads slowly too. Both halves need attention, not just one.
A short readability checklist before publishing
A quick second pass, applying the four principles and plain language together, catches most of the common problems before a document goes out. Do headings look clearly different from body text, not just slightly different? Does formatting repeat consistently from section to section, or does it drift partway through? Does everything align to a clean, consistent structure? Do related items sit close together, with real distance around anything unrelated? Is there enough white space that the page doesn’t look intimidating before a word is read? And, on the language side, would a reader unfamiliar with the subject understand the first sentence of each section on a single read?
None of these checks require design training. They require noticing, on a second pass through any document before it ships, whether the important parts actually look important and read plainly, which is most of what document design and readability actually come down to. Applying that second pass sits alongside the broader habit of reading, not just writing, a document well, covered in how to read a report: a reader who can spot weak contrast or a cramped page has usually also learned to spot a claim without evidence sitting a few lines away from it. The accessible PDF checklist picks up where this one leaves off, covering what happens once a well-designed document needs to reach a reader using a screen reader or another assistive tool, a layer of readability visual design alone cannot solve.