By Design Productive Editorial
A heading outline review asks whether a page makes sense when you read only its section names. It is a useful checkpoint for a small business owner or small design team because it separates content organization from typography. A large bold sentence may look like a heading without being marked as one. A correctly marked heading may still tell readers very little about what follows.
Editorial note: this is a practical editorial review workflow, not a complete accessibility audit or a guarantee of conformance. Use your project’s own requirements and a specialist reviewer where the stakes are high.
The W3C Web Accessibility Initiative explains that headings communicate content organization and can support navigation through browsers and assistive technology. This guide turns that principle into an editorial review workflow for small teams.
Choose one page and one reader task
Start with a real page, such as a service explanation, a help article or a project case study. Write down the main thing its reader should be able to find. For a service page, that might be how the engagement works. For a help article, it might be the steps for correcting a specific problem. Avoid reviewing an entire website in the same session.
Identify the version you are checking. A design file, a content document and the built page can have different headings. Record the URL or file reference and the review date. If you are looking at a mockup, say so in the notes. A visual mockup cannot confirm which HTML elements the final page will use.
Ask the content owner to identify intentional constraints before the review begins. A product name may need a particular spelling. A support page may have a fixed title format. Those constraints are inputs to the review, not reasons to accept vague section names throughout the rest of the page.
Extract the words before discussing appearance
Copy each heading into a plain document in reading order. Include the main page heading, section headings and subsections. Leave out paragraph text at this stage. Indent subsections beneath their parent sections so the intended relationships are visible. This simple list is the review artifact everyone will use.
If you can inspect the built page, record the actual heading level beside each entry. If you cannot, add a separate column for the intended level and leave the implementation result unverified. Do not turn an assumption into a passed check because the font sizes appear consistent.
Keep the wording exactly as it appears initially. Editing while extracting hides the original problem. For example, preserve a heading called “More” until the team agrees whether it introduces pricing details, setup steps or related articles. The outline should expose that uncertainty rather than quietly remove it.
Run the heading outline review without body copy
Read the list aloud or ask a teammate to read it silently. Can they tell what the page covers? Can they point to the section that answers the main reader task? Have them describe what they expect under each heading. Compare that expectation with the actual section only after they have given their answer.
Try this with a fictional service page. Its original headings might be “Overview,” “Our Approach,” “More” and “Get Started.” A clearer outline might be “What the Service Includes,” “How Requests Move Through Review,” “What You Supply Before Work Starts” and “Send Your First Request.” These are editorial examples, not a universal template.
A heading does not need to contain every detail. It should name the subject or action clearly enough to help someone choose a section. If a section contains several unrelated subjects, changing the heading alone may not solve the problem. Split or reorganize the content before polishing the label.
Check the relationships between sections
Compare each subsection with its parent. A subsection named “What to Bring” belongs naturally under “Prepare for the Workshop.” It is harder to place under “Our Values.” That mismatch suggests either a misplaced section or a parent heading that does not describe its children.
The W3C heading tutorial recommends logical nesting and avoiding skipped ranks where possible, while allowing higher-level headings to close existing subsections. For the team review, draw the intended tree first. Then let the developer compare that tree with the actual markup rather than choosing levels simply to obtain a particular visual size.
Repeated sections should have consistent relationships. If every service card is a subsection of “Available Services,” check that one card has not accidentally become a peer of the entire group. Mark the exact entry where the relationship changes. “Fix hierarchy” is less useful than naming the affected section and its intended parent.
Separate a heading from a promotional line
Inspect prominent text that was left out of the extracted list. Some pages use large slogans above smaller, more informative section labels. Decide which text actually introduces a section and which text is supporting copy. Record that decision so the implementation does not depend on a developer guessing from the design.
For example, “Make Every Request Count” might be a promotional sentence above a section explaining an intake form. “Prepare Your Design Request” identifies the section more directly. The page can retain a slogan if it serves the brand, but the review should make the organizational role of each piece explicit.
Do the same for cards, accordions and sidebars. Do not add a heading level to every short label by habit. Ask what relationship the label expresses within the page. When the right structure is unclear, add a question for the developer or accessibility reviewer rather than prescribing markup without sufficient context.
Make a small issue log
Use a table with the current heading, intended purpose, proposed change, owner and verification step. Keep copy changes and implementation changes in separate rows when they need different people. A writer can rename a section; a developer may need to correct its markup. Both changes can be necessary.
An example copy issue might read: “More → rename to What Happens After Submission; section explains review and response.” An implementation issue might read: “Preparation Checklist → verify as a subsection of Before the Workshop.” Each entry says what to inspect and where to inspect it.
Assign a verification action that someone can actually perform. “Read the revised outline without body text” checks wording. “Inspect the built heading structure” checks implementation. “Confirm with the content owner that the section still matches the heading” checks the meaning after revisions.
Recheck the outline after revisions
Extract the headings again from the revised version. Do not assume that accepting all suggested edits produces a coherent result. Two individually sensible changes can create duplicate labels or move related sections apart. Compare the complete outline with the original reader task and with the issue log.
Then read the surrounding paragraphs. A heading may now promise instructions that the section does not contain. Fix either the promise or the body. If the page includes a table of contents, confirm that its labels and destinations match the revised headings. Treat outdated navigation text as part of the same correction.
The W3C page structure tutorial describes headings as one part of meaningful structure alongside regions and appropriate content markup. Keep the review bounded: a clean outline does not establish that links, forms, focus behavior or the rest of the interface have passed review.
Hand over evidence instead of a vague approval
Save the final outline, the issue log and the version reference together. Note which checks were completed and which still depend on the built page. A useful handover might say that wording and intended nesting were reviewed, while actual markup remains for developer verification. That is clearer than an unqualified “accessibility approved.”
For a wider team process, connect this checkpoint with your business systems workflow. Repeat it when a major section is added or reorganized, rather than restarting the discussion from memory. A heading outline review is complete when the section names tell a coherent story, the relationships are explicit and the remaining implementation questions have owners.
By Design Productive Editorial.


