Break a long document into sections and give each one a short, specific heading. Use real heading styles, not bold text. Keep to two or three levels, and word each heading so the reader knows what is underneath.
A page with no headings is a wall. Readers cannot tell where one topic ends and the next begins. The sections below cover what headings do, which levels to use, how to word them, and how many a document needs.
What headings do in a long document
The W3C tutorial on headings says they communicate the organization of the content on the page. Web browsers, plug-ins and assistive technologies can use them for in-page navigation.
That has a plain meaning. Headings let a reader jump straight to the part they need. A screen reader can announce a heading with its level and move from heading to heading, according to the W3C technique for heading markup. Any reader can do the same by scanning the page.
Headings help you as well. Digital.gov's plain language guide suggests starting to write with the headings. Draft them first, and they show you the major groups of information before you write a line of body text.
Real headings versus bold text
A bold line with a larger size looks like a heading. The software does not treat it as one. GOV.UK guidance says plainly: do not use bold to mark up subheadings. Use styles to create a hierarchy of headings, such as heading 1 and heading 2.
The W3C lists this as a failure. It describes a case where a paragraph is styled to look like a heading, so assistive technology cannot tell it is one.
In Word, Microsoft's steps are short. Select the text you want as a heading. On the Home tab, pick a heading style in the Styles gallery. Menu names can differ by version.
Styles also give you control. Microsoft says heading styles let you build a table of contents, reorganize the document and reformat its design without changing each heading by hand. Here is a quick test. Change the look of one heading style. If every heading changes together, they are real headings.
How many levels, and in what order
Headings come in levels. The W3C tutorial says the most important is rank 1 and the least important is rank 6. Headings of equal or higher rank start a new section. Lower ranks start subsections inside it.
Digital.gov advises limiting levels to three or fewer. Four or more make it hard for readers to keep track of where they are. The W3C adds that skipping ranks can confuse. An H2 should not be followed directly by an H4.
| Level | Job | Example |
|---|---|---|
| 1 | The title of the document | Volunteer handbook |
| 2 | A main section | Before your shift |
| 3 | A part of that section | At the check-in desk |
| 4 and below | Avoid. Rework the structure. | None |
Use one level 1 heading per document, as the title. Do not pick a level for its size. Pick it for its place in the outline, and set the look in the style.
If you need a deep outline, the document may be trying to do too much. Split it into two documents.
Words that tell the reader what is there
A heading is only useful if it says something. Digital.gov describes three kinds: question headings, statement headings and topic headings. Questions work when you know what readers will ask. Statements are bold and direct. Topics are formal and can be so vague that they do not help.
The guide names "General", "Application" and "Scope" as topic headings that confuse. The word "Application" could mean two different things. Be concrete.
Keep a heading shorter than the text under it. Do not make it so short that it says nothing.
Before: Information. Details. Other.
After: When the event starts. What to bring. Who to ask for help.
The second set tells the reader what each part holds before they read a word of it. For help with the writing under each heading, see putting the main point first.
How many headings to use
There is no fixed count. A rule of thumb is one heading for every few paragraphs. Each section should hold one topic. If a section has only two sentences, merge it with its neighbor.
Avoid a lone subheading. If a section has a level 3 heading, it should have at least two. One by itself suggests the section does not need one.
Picture a handbook of about 900 words. It might have one title, four level 2 headings and a few level 3 headings under the longest section. That is roughly one heading for every 150 words. Use this checklist on your own draft.
- The document has one title at level 1.
- Every main section has a level 2 heading.
- No level is skipped.
- Each heading says what the section holds.
- Headings are real styles, not bold text.
The Easy-Read Editor flags long paragraphs. A long stretch of text with no break is often a sign that a heading is missing. Add one, and the stretch usually splits into two clear parts.
Headings pair well with lists. When a section is mostly a set of items, see when to use a list instead of a paragraph. The W3C also lists a technique for tagging headings inside a PDF. The article on making a PDF that reads well on screen shows what to check.
Common mistakes
- Making a line bold and large instead of using a heading style.
- Choosing heading levels by how big they look.
- Skipping from level 2 to level 4.
- Writing vague labels such as "Overview" and "Other".
- Writing headings as long as the paragraph beneath them.
- Adding a heading for every one or two sentences.
- Going four or five levels deep.
FAQ
How many heading levels should a document use?
Two or three. Digital.gov advises three or fewer, because deeper outlines are hard to follow.
Can I use a question as a heading?
Yes. Question headings work well when you know what your readers will ask. Keep them short and specific.
Should every document have a heading 1?
Give each document one title at level 1. Then use level 2 for the main sections.
Why do headings matter to a screen reader?
Software can read the heading level and jump between headings. A bold line gives it no such signal.
Sources
Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.
- Headings (W3C Web Accessibility Initiative tutorials) Checked November 19, 2026
- Headings (Digital.gov plain language guide) Checked November 19, 2026
- Publishing accessible documents (GOV.UK) Checked November 19, 2026
- Add a heading in a Word document (Microsoft Support) Checked November 19, 2026
This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.