Anyone who publishes articles on community platforms eventually asks the same practical question: what should a post actually look like so that more people can read it comfortably? This comparison looks at three common ways of formatting a post and weighs each one on accessible content writing, meaning how easily a wide range of readers can get through it. No theory, no fuss, just what works.
Why the “average reader” is a trap
Most posts are written for an imagined reader: someone with good eyesight, a big screen, plenty of time and native-level fluency. Real audiences are mixed. They include older readers who enlarge the text, people reading on an old handset on a patchy connection, readers using a screen reader, and people reading in their second language who feed tricky sentences into a translator.
If your post only works for the imagined reader, the rest quietly leave. You will never see a complaint. You will just see a short time on page. So let’s compare three formats and see which ones leave fewer people behind.
Format A: the wall of text
A long, unbroken run of paragraphs with no subheadings. It is the quickest to produce, and it looks fine in a draft editor.
- Strengths: a single flowing argument, minimal formatting effort.
- Weaknesses: hard to scan, tiring on small screens, almost impossible to navigate with a screen reader, and difficult to translate cleanly when sentences run on.
- Who it shuts out: anyone short of time, anyone using assistive technology, and anyone reading in a second language.
Format B: the structured post
Short paragraphs, descriptive subheadings in order, bullet lists where items really are lists, and links that say where they go. This is the format most readers instinctively appreciate.
- Strengths: scannable, easy to navigate by heading, friendlier to translation tools, comfortable on phones.
- Weaknesses: takes a bit more planning, and it is easy to overuse bullets until the post feels choppy.
- Who it shuts out: far fewer people. Remaining gaps tend to be images without descriptions and tables without headings.
Format C: structured with alternatives
Everything in Format B, plus a second route to the main ideas: a short summary at the top, descriptive text for every image, a transcript for any audio or video, and a plain-words glossary for unavoidable jargon.
- Strengths: works for the widest range of readers, and the summary helps everybody decide whether to read on.
- Weaknesses: the most effort, and the extras must be kept up to date when you edit the post.
- Who it shuts out: almost nobody who can reach the page at all.
A side-by-side look
- Time to write: A is quickest, B takes moderate planning, C takes the most.
- Readability on a phone: A is poor, B is good, C is best.
- Navigation with assistive tools: A is poor, B is good, C is best.
- Handling by translation tools: A struggles, B copes, C copes well because sentences are short and terms are explained.
- Value to the average reader: A is tolerable, B and C are clearly better, because the average reader is also tired, distracted and in a hurry.
Where practitioners often get stuck
The most common slip is treating Format B as “done” and skipping images and media. A neat structure with unlabelled pictures still leaves some readers guessing. The next most common slip is writing subheadings that are clever instead of clear. A heading such as “The plot thickens” tells a screen-reader user nothing, while “How to add a short summary” tells them exactly what follows.
If you are comparing platforms for publishing, it helps to see how the process feels in practice. Our walkthrough on setting up an account and publishing a first newsletter-style piece shows the editing steps, and the guide to posting a technical write-up on a developer community covers a more code-friendly editor. In either one, try the three formats above and see how each renders on a phone.
What a web team does about it
Authors carry some of this load, but the pages themselves are built by developers. That is why it is worth noticing teams that hold themselves publicly to account. The website development and SEO practice at cmsGalaxy, for example, maintains an accessibility statement on its own site, which is a practical sign that the people building pages for others apply the same thinking at home.
A simple decision rule
Here is the no-nonsense version of the comparison.
- If the post is a quick personal note, Format B is plenty.
- If it is something you expect people to return to, such as a guide, a how-to or a reference list, go for Format C.
- If you catch yourself writing Format A, split it before publishing. Add headings, break the longest paragraphs in two, and replace vague headings with descriptive ones.
One last check before you hit publish
- Read the first two sentences aloud. Do they say what the post offers?
- Scan only the headings. Do they tell the story on their own?
- Check every image has a short text description.
- Look at the post on your phone with the text size increased.
- Ask whether a reader who has never heard of your topic could follow the first paragraph.
None of this makes your writing less distinctive. It simply removes obstacles between you and the people you want to reach, and the comparison above shows that the extra effort is modest. Pick the format that fits the post, apply the checklist, and your work will be easier for everyone to read.