SEO & Search

Accessible Headings on B2B Pages: Make the Page Outline Describe the Buying Information

A service page can explain its scope and still make the answer difficult to find.

The exclusion sits under “More.” The preparation instructions look like a heading but use ordinary paragraph markup. A nested section appears to belong to the wrong topic.

Review the outline before polishing the section names. Write down what each section contains, what its heading says, and where it belongs.

The worksheet below follows a fictional documentation-review service. Its examples describe invented content and proposed review decisions. They report no customer work, audit result, or business outcome.

Separate the Page Title, Heading Rank, and Visual Style

Keep three fields in the review. The page title identifies the document in its title metadata. A semantic heading identifies a section in the content structure. Visual styling controls its appearance.

For this worksheet, record the page title as background. Leave title rewriting outside the assignment. Review the headings readers encounter within the page.

The W3C Web Accessibility Initiative (WAI) describes six heading ranks, from h1 through h6. Headings communicate content organization and support in-page navigation through browsers and assistive technologies. W3C: Headings tutorial.

Record the implemented element or heading role alongside the visible words. “Large and bold” describes presentation. It does not identify the semantic rank.

In the fictional page, “Getting ready” appears in large type. Suppose inspection finds a paragraph with a styling class and no heading role. Record those two observations separately. Do not write “h2” because the text resembles nearby h2 elements.

Start with the document's main topic. Then identify its sections and subsections. Choose wording after those relationships are clear. Otherwise, an attractive label can conceal an unresolved content boundary.

Define the Buying Information Before Naming Sections

The fictional service reviews a buyer's documentation and returns an issue list. It excludes rewriting. The buyer must provide approved sample documents before work begins.

Those are invented service terms. A real content owner must verify its actual offer before changing section wording. Accessibility review does not authorize new service claims.

For this example, use four buying questions: What does the review cover? What does it exclude? What must the buyer supply? What arrives at delivery?

Write each answer in plain language first. Assign it to a section. If one answer spans several sections, identify the relationship before deciding whether a subsection helps.

Keep unrelated content outside the outline. A biography may establish background elsewhere on the site. It does not answer whether rewriting is included in this fictional service.

Give an unanswered question its own working note. Do not insert an affirmative answer merely to complete the page structure. Unknown scope remains unknown until its owner supplies evidence.

The content inventory becomes the reference for the review. A new heading should describe the answer beneath it. It should not advertise a broader service than the approved text supports.

Compare the Visible Outline With the Implemented Outline

Use one row per observed heading or heading-like passage. The following before state is fictional. The parent column records the apparent implemented relationship for discussion.

Visible text Observed structure Apparent parent Section contents Buyer question
Documentation review h1 Main content Service introduction What is this service?
Our approach h2 Documentation review Included review activities What does it cover?
More h4 Our approach Rewriting exclusion Is rewriting included?
Getting ready Styled paragraph; no heading role None recorded Required sample documents What must I provide?
Your next chapter h2 Documentation review Issue list delivered What will I receive?

The table contains five observations. Two labels need a content decision: “More” and “Your next chapter.” One passage needs structural inspection: “Getting ready.” The h2-to-h4 descent needs a nesting review.

“Our approach” is also open to revision. It might describe a method on another page. In this example, its contents list included activities, so “What the review includes” is more direct.

Avoid treating every vague label identically. “More” supplies little topic information here. A short label such as “Sources” can describe its section accurately. Judge the words against their local topic.

Record navigation, sidebar, and footer headings in their own regions. Mixing all regions into one flat list can obscure what belongs to the article. Keep the complete page available during interpretation.

Nest Subsections According to Their Content

WAI recommends nesting ranks and avoiding downward skips where possible. Moving from h2 directly to h4 can confuse the outline. Returning from h4 to h2 can close subsections and begin a new section. The tutorial also distinguishes fixed page sections, where consistency across pages matters. W3C: Heading ranks.

Apply that distinction to the fictional service. Decide whether exclusions form a subsection of scope or a peer section. The answer comes from the organization of the content.

If scope has one heading, put included activities and exclusions beneath it as sibling subsections. If the page presents four separate buying questions, use peer sections. Both proposals require checking the resulting content relationships.

Do not insert an empty h3 to bridge the numerical gap. An invented section with no purpose creates another thing the reader must interpret.

Do not declare every skipped rank an automatic accessibility failure. Record the observed sequence, its content relationship, and the reason for concern. A specialist can assess the applicable criterion against the implemented page.

The proposed after outline below uses peer sections. The service terms support that choice in this fictional example. It is an editorial decision, not a prescribed outline for every B2B service.

Keep Descriptive Wording and Programmatic Structure Separate

Web Content Accessibility Guidelines (WCAG) 2.2 Success Criterion (SC) 2.4.6, Headings and Labels, is Level AA. Provided headings and labels must describe their topic or purpose. Its Understanding document distinguishes descriptive wording from correct structural identification. It does not require headings to exist. W3C: Understanding SC 2.4.6.

SC 1.3.1, Info and Relationships, is Level A. It addresses whether information, structure, and relationships conveyed through presentation are programmatically determinable or available in text. WCAG 2.2: SC 1.3.1.

Give the fictional findings separate records. “More does not describe the rewriting exclusion” concerns wording. “Getting ready is presented as a section heading but lacks an identified heading structure” concerns implementation evidence.

A wording edit cannot settle both records. Renaming “Getting ready” to “Documents you provide” still leaves the markup question open. Changing its element still leaves the content owner responsible for its accuracy.

Use criterion references to bound a finding. Keep the exact page version and observed behavior beside them. Avoid turning a content worksheet into a declaration that the whole page conforms.

Other review tasks remain separate. Use the keyboard-navigation review for menus and controls. The heading worksheet records content structure and section meaning.

Copy the Heading Worksheet

Use this field list in the team's existing document. It is a proposed review record. Add a row for each passage under examination.

Field What to record
Region Main content, navigation, sidebar, or footer
Text Exact visible heading or heading-like words
Rank Observed semantic element or role and level; unknown when uninspected
Parent Intended parent topic and observed relationship
Topic Contents summarized without marketing language
Proposed wording Accurate replacement, or unchanged with a reason
Evidence Page version, inspection method, excerpt, and issue reference
Retest state Uninspected, reproduced, awaiting change, retested, or unresolved

Keep proposed wording separate from approved wording. The worksheet records a decision in progress. It should not imply that a subject owner accepted a claim merely because an editor wrote it down.

For “Getting ready,” enter main content as the region and styled paragraph as the observed structure. Enter required samples as the topic. Propose “Documents you provide.” Mark the semantic change awaiting implementation.

For “More,” record the current h4 and the exclusion paragraph. Propose “What the review excludes.” Record whether the intended parent becomes the main topic or a scope section.

Evidence should identify enough context to reproduce the observation. A cropped screenshot of one word does not establish its place in the implemented outline.

Walk Through the Proposed After State

The fictional content owner selects four peer sections. The implementation owner supplies a revised test page. The proposed outline contains one main heading and four h2 headings.

Proposed text Rank Parent topic Answer retained
Documentation review h1 Main content Service identity
What the review includes h2 Documentation review Included activities
What the review excludes h2 Documentation review Rewriting is excluded
Documents you provide h2 Documentation review Approved samples required
What you receive h2 Documentation review Issue list delivered

Reconcile the after state with the before inventory. Five passages remain five passages. The exclusion retains its full boundary. The preparation answer retains its approved-sample condition. Nothing disappears to make the outline look cleaner.

Inspect the implemented headings in reading order. Compare each rank with its intended parent. Read the first paragraph beneath every heading to check whether the section begins with the promised subject.

Then inspect the complete section. A correct opening can conceal an unrelated paragraph later. Move that paragraph only after the content owner decides where it belongs.

If a comparison grid sits within scope, review its relationships through the accessible comparison-table guide. A useful section heading does not establish the meaning of individual cells.

All after-state observations in this walkthrough are synthetic. A real retest must record what the actual revised page exposes in its stated environment.

Retest the Reader's Question and Preserve the Limits

Return to the four buying questions. Locate each answer using the outline. Read the full condition before marking the item retested.

Record the browser, version, page revision, inspection tool, and assistive technology used. If no screen reader was used, state that limit. A source inspection and a screen-reader navigation attempt produce different evidence.

For the fictional exclusion finding, a bounded after note reads: “The revised heading names exclusions. Its section still states that rewriting is outside the service.”

For the structural finding, record the observed heading element and rank. Keep the original evidence with the after record. Another reviewer should see which change addressed which finding.

Use the zoom and reflow worksheet when headings or their paragraphs become clipped during enlargement. That condition requires its own observation.

Leave untested regions and states visible in the record. The review can close its assigned findings without making a site-wide accessibility claim.

Make the outline describe the answer.

Sources

Topic map: Accessible B2B websites

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: Accessible B2B websites

Neighbor: Technical SEO, crawling, and migrations

Neighbor: Customer and usability research

Neighbor: Topical authority and keyword strategy