Descriptive Headings That Map Service Page Sections

A visitor on a service page rarely reads every paragraph in order. They skim for the section that answers their question—what you do, how it works, what it costs, how to inquire. When those sections sit under headings like “Overview,” “Details,” or “More information,” the map collapses. The content may be solid; the labels do not say so.

WCAG 2.2 Success Criterion 2.4.6 (Headings and Labels, Level AA) requires that headings and labels describe topic or purpose when they are present. GOV.UK’s content guidance adds a writer’s checklist: descriptive, frontloaded, active, and removable. Together they give service sites a practical standard for section titles that survive both visual scanning and assistive navigation.

---

Why vague headings stall service-site decisions

Screen-reader users often jump through a list of headings to build a mental table of contents. Sighted scanners do something similar with their eyes: they read headings first, then decide whether to enter the paragraph below. W3C’s Understanding document for 2.4.6 states the intent plainly—clear headings help people find information and understand how parts of the page relate, especially readers who process text slowly or have limited short-term memory.

On a consultancy or trades homepage, a non-descriptive heading wastes that moment. “Services” might be acceptable if the list is short and obvious. “Module 1,” “Section,” or a date used as the only heading for an article card is not—W3C’s related techniques and common audit patterns treat headings that fail to describe the following content as failures of the criterion’s intent.

GOV.UK’s Create a clear structure for your content guidance notes that many people skim and may read only a fraction of a page. Their remedy is structural: break text with headings that carry meaning, then put the most important information early in both the page and the heading itself.

---

What “descriptive” means under WCAG 2.4.6

Success Criterion 2.4.6 is short: headings and labels describe topic or purpose. The Understanding page clarifies what that does not require:

• It does not force you to add headings where none exist.
• It does not cover whether a heading is correctly marked up—that sits under Success Criterion 1.3.1 (Info and Relationships).
• Form labels that are missing altogether are handled under 3.3.2; 2.4.6 applies when a label or heading is present and must be clear enough.

That split matters in practice. A page can pass 1.3.1 with perfect h2 markup and still fail 2.4.6 if those h2s say “Details” and “Info.” Conversely, visually bold text that looks like a heading but is only a strong or span can fail 1.3.1 even when the words are excellent. Service sites need both: accurate wording and real heading elements.

W3C technique G130 (Providing descriptive headings) is the sufficient technique most relevant here. Labels for controls follow G131; for service marketing pages, the everyday win is section titles that name the offer, process step, audience, or outcome.

A useful analogy: headings are chapter titles in a book you will not finish. If the chapter is called “Chapter Three,” you keep flipping. If it is called “How we scope a website redesign,” you know whether to stop.

---

How GOV.UK turns description into writing rules

GOV.UK’s publishing guidance for clear structure asks writers to make headings:

Rule	Meaning for a service page	Weak example	Stronger example
Descriptive	Avoid generics that could fit any section	Introduction	Commercial roofing for mid-rise buildings
Frontloaded	Put the distinctive words first	You can request a site audit	Request a site audit
Active	Prefer verbs when the section is a task	Driving licence applications	Apply for a driving licence
Removable	Body copy still makes sense if headings vanish	—	Write paragraphs that stand alone

Their formatting guidance adds hierarchy rules that match assistive-technology habits: the page title is the H1, content starts at H2, and you should not skip from H2 to H4. Bold text must not substitute for a heading tag—screen readers will not treat it as a header. GOV.UK also advises against question-form headings when they are hard to frontload; on a service site, “What happens after you inquire?” can work if the answer section is short, but “After you inquire” or “What happens next” is often clearer for scanners.

The Design System’s headings pattern separates visual size from semantic level: you may style an H2 to look smaller, but you still choose the HTML level for outline order. Rare inversions need accessibility testing. For most business sites, keep the outline honest—H1 once, then nested H2/H3 that mirror the real content tree.

---

Applying the rules on a typical service layout

Walk a common service template and rewrite the outline before touching layout:

1. Page H1 — Name the service and audience, not the firm alone (“Bookkeeping for independent clinics,” not only the company name repeated).
2. H2: What we include — Lists deliverables; avoid “Overview.”
3. H2: How the engagement works — Steps, timeline, who does what.
4. H2: Who this is for — Fit criteria; reduces wrong-fit inquiries.
5. H2: Pricing or investment — Even a ranges-and-factors section beats “Details.”
6. H2: Start a project — Sits above the contact form or primary CTA so the heading matches the task, as GOV.UK recommends for start buttons.

Audit checklist

• One H1 that matches the page’s primary topic.
• Every H2 predicts the section content without reading the paragraph.
• No skipped levels in the main content outline.
• No “fake headings” made only with bold, larger font, or colored spans.
• Generics (“Introduction,” “Welcome,” “More”) replaced with topic words.
• Form section headings name the purpose (“Request a consultation,” not “Form”).
• Nested H3s only appear under a related H2 (for example, under “How the engagement works”).

Limits worth stating

Descriptive headings do not fix thin offers, missing prices, or a buried contact path. They also do not replace landmark regions (main, nav) or a skip link—those are separate orientation tools. Overly long headings can themselves slow scanners; W3C notes that labels need not be lengthy—a short phrase is enough when it cues the content accurately. Brand voice still applies: active and frontloaded does not mean shouty.

“A heading is a promise about the next block of copy. If the promise is vague, scanners and screen-reader users both pay the same tax—extra work to learn what the section is for.”
— Windware Studio Practice Note

---

Practical takeaways for your next website

1. Inventory the outline: export or list every H1–H3 on homepage, primary service, and contact templates; rewrite any title that could fit a different section unchanged.
2. Pair wording with markup: descriptive text in real heading elements; keep visual scale in CSS so the outline stays truthful.
3. Frontload service nouns and verbs: lead with the offer, audience, or task—“Commercial HVAC maintenance,” not “Our approach to keeping systems efficient.”
4. Align CTA blocks with their H2: the heading above a form or button should name the same task the control performs.
5. Retest with a heading-only pass: read just the headings aloud or via a headings list; if the story of the page is unclear, the body will not rescue scanners.

The next step is editorial before decorative: lock the heading outline in the content draft, then design components that honor those levels instead of inventing new visual “titles” that never enter the document outline.

---

Ready to Discuss Your Website?

If you are planning a new website, a service redesign, or custom development for your business, we’re here to help shape the work.

• Explore Our Services: Web Design · Web Development · Website Redesign
• Start a Conversation: Tell us about your project via our Contact Form or email us directly at [email protected].