A parent opens a practice note from the fictional music school Reed & Meter about returning to an instrument after a break. They first scan the headings to see whether this note is for them, then try to read a section closely. The title is promising, but the headings are vague (“A Few Thoughts,” “More to Consider”), the lines run very wide on a large screen, and the author’s name and the date appear only at the very end.
Reed & Meter is a teaching example, not a test result. The useful question is whether the article’s layout supports both finding a relevant section and reading it.
Use these questions as a way to think, not as a score:
- On a first scan, do the title, introduction, and headings tell you what the piece covers?
- On a close read, is the text comfortable to follow, and does competing material get in the way?
- Can a visitor tell whose piece this is, and when it was published?
This is a visual review of an article or blog template. It is not a help-center layout review. If the page is actually task-oriented help, use How to Review a Help or Documentation Layout.
Headings Should Form a Useful Outline
A visitor who is deciding whether to keep reading should be able to get a coherent outline from the headings. WAI’s headings tutorial treats headings as the structure of the page, not as decoration. Nielsen Norman Group’s writing on text-scanning patterns (2019) describes several ways people scan, including a layer-cake pattern that leans on headings. Do not tell editors to design an article to an F-pattern. An F-pattern is one observed scan path, not a layout to imitate. NN/g describes it as what people tend to do when a page has no subheadings or bullets.
On Reed & Meter’s practice note, “A Few Thoughts” does not tell a returning player what they will learn. A heading that names the section’s job, such as “What to Practice in the First Two Weeks,” does. If the headings alone are a useful outline, the scan pass is doing its work.
If the article is long enough that a contents list would help, that check belongs in In-Page Jump Links for Long Service Pages, or Split the Pages?.
Comfortable Lines, Not One Magic Length
Sources do not agree on a single best line length. In a 1998 study of line length and method of movement, Mary Dyson and Gary Kipping found that long lines (100 characters) were read faster than very short lines (25 characters), with comprehension unchanged, while readers rated moderate lines (55 characters) easiest to read (Visible Language). In 2005, A. Dawn Shaikh and Barbara Chaparro had 20 college-age students read online news articles at 35, 55, 75, or 95 characters per line and found faster reading at 95 characters, with overall satisfaction not affected by line length, although readers preferred the extreme lengths (HFES / SAGE). The GOV.UK layout guidance recommends layouts that would usually mean no more than 75 characters per line. WCAG 2.2 Visual Presentation, at Level AAA, includes an 80-character line-length criterion.
Those are different studies and standards, in different contexts. They do not establish one universal optimum. The 80-character criterion is Level AAA, not a general obligation for every article, and a visual review cannot measure character counts. If lines look uncomfortably long or cramped at a given width, say that as an impression, not as a measurement.
Paste the article address into Online Website Previewer and press Preview. That address opens in all three frames: phone 390 by 844, tablet 820 by 1180, and desktop 1920 by 1080 CSS pixels. The previewer is a visual check of layout in your current browser, not a test of a particular device. Look at the reading column at each width. A line length that feels fine on a phone can feel very wide on a large desktop frame. Body text size on a narrow screen is covered in What Font Size Should You Use for a Mobile Website?.
Byline, Date, and Extra Material
Where the byline and date sit, whether a sidebar stays useful, whether related posts help or distract, and whether a reading-time label appears at all, are editorial judgments, not findings from a test of article templates. This guide’s prompt is simple: can a visitor tell whose piece this is, and when it was published, without hunting? If a sidebar or related-post list competes with the reading column, say what got in the way. If the issue is what draws the eye first, use How to Review a Website’s Visual Hierarchy. Do not invent a rule that every article must show a reading time, or that a sidebar is required or forbidden.
Send a Keep or Rework Note
A useful note might say: “At [address], I checked the phone, tablet, and desktop previews at 390 by 844, 820 by 1180, and 1920 by 1080 CSS pixels, respectively. In the desktop preview, I could not tell from the headings whether this practice note would help someone returning after a break, the lines looked very wide, and the author and date appeared only at the end. Please rename the headings so they form an outline, tighten the reading column on the wide layout, and put the byline and date where a visitor can find them at the start.”
For how to phrase the note, see How to Give Useful Feedback on a Website Design.



