Long content has no subheadings

Why does it matter?

Screen reader users move around a long page by jumping from heading to heading. A long post with no subheadings is one unbroken block to them — they have to listen from the top to find the part they need. For everyone else it is a wall of text that is hard to skim, especially for people with reading or attention difficulties.

Who it affects: Screen reader users, who jump from heading to heading to understand and skim a page, and people with cognitive disabilities who rely on clear structure.

What does Lumtera flag?

Content with more than 600 words of visible text and no headings at all (no H1–H6 and no role="heading"). It is reported once per post, as a tip: section headings are a WCAG level AAA recommendation. Dismissing it sticks, even if you later edit the first paragraph.

Check ID content-no-headings — use it to filter the content report or with wp lumtera issues --rule.

How do I fix it in WordPress?

Break the text into sections and give each one a Heading block (H2 for main sections, H3 inside them). Screen reader users can then jump from section to section, and everyone can skim to the part they need. Section headings are a level AAA recommendation.

Example

<p>Our story began in 1998…</p>
<p>…</p>
<p>Today we deliver across the valley…</p>

<h2>How we started</h2>
<p>Our story began in 1998…</p>
<h2>Where we deliver</h2>
<p>Today we deliver across the valley…</p>

How do I check the fix?

1. Update the post. The issue disappears from the Lumtera Accessibility sidebar on the next check, and from the site report on the next scan.
2. Use a headings outline — the block editor's Document Overview (List View → Outline), or a browser extension such as HeadingsMap — and check the levels read like a table of contents.