Monitoring Heading Levels After a Section Redesign

November 3, 2026

A homepage redesign rarely breaks the H1. It breaks the levels underneath it. What heading monitoring should catch when sections are swapped, renamed, or nested twice.

Nobody redesigns a page by editing its heading outline. They drag sections around in a builder, swap a banner for a slideshow, and publish. The visual result looks ordered. The heading structure underneath often is not, because a section that used to sit under an H2 now sits under nothing, or an H3 promo title now outranks the product heading below it.

Heading order is not a ranking trick. Under WCAG 1.3.1 and 2.4.6 Headings and Labels, headings are how screen reader users skim. They pull up a list of headings and jump, the way a sighted shopper scans bold titles. A broken outline gives them a list that lies about what the page contains and in what order it matters.

What a redesign actually breaks

The common failures are small and specific. A skipped level, an H2 followed directly by an H4 because the H4 style looked right for a card title. A second H1 added by a new hero section, so the page now announces two competing titles. A heading that is really a button label, or a button that is really a heading, depending on which component library shipped that week.

Monitoring should compare the outline, not just count tags. Record the sequence of levels and text for the key templates, product, collection, article, and homepage, and flag a change in sequence even when the count stays the same. A page can keep nine headings and still lose the one that named the main content.

Style is not structure

Designers pick a heading tag for its size. That is the root of most of this. The fix in the template is to separate the two decisions: choose the level for the outline, then apply a class for the size. In monitoring terms, that means a change in visual order with no change in tags will not show up in a tag scan, so pair the automated check with a short manual pass on the templates that changed.

Ask a simple question during that pass. If you hid the styling, would the heading list alone tell you what this page is about and what comes first? If the list reads like a set of slogans and sale messages with the product name buried sixth, the outline is serving the layout, not the reader.

Set the alert threshold low

One skipped level on one template sounds minor until you remember a template is thousands of pages. A collection template that skips from H1 to H3 does it on every collection the store runs. Monitoring at template level, rather than page level, is what turns a small finding into a single fix instead of a backlog of near identical tickets.

Log the finding with the template name, the before and after outline, and the date the redesign shipped. Without that link to a release, heading regressions get closed as long standing issues and sit. With it, they go back to the team that introduced them while the change is still fresh enough to remember.

Related reading: Monitoring Focus Order in Sticky Add to Cart Bars, Monitoring Aria-Live Regions for Cart and Search Updates, Monitoring Skip Links: The First Tab Stop Nobody Tests.

Frequently asked questions

Can a page have more than one H1?

HTML allows it in some patterns, but in practice a single clear H1 naming the page is the pattern assistive technology users expect and the easiest to keep consistent. Multiple H1s usually appear by accident when a new section is added.

Is a skipped heading level a WCAG failure?

Skipping a level is not automatically a failure in every reading of the standard, but it breaks the navigable outline headings are meant to provide and is normally treated as a defect in audits, especially when it hides the main content heading.

Should monitoring scan every page or just templates?

Templates first. Most fleet pages inherit their outline from a handful of templates, so a template regression explains hundreds of page findings. Scan individual high traffic pages as a second layer, not the first.

How do screen reader users use headings?

They can request a list of all headings on the page and jump directly to one, similar to scanning visible titles. A clear, correctly ordered outline is therefore a navigation feature, not just document formatting.

Frequently asked questions

What is the main takeaway from An accessibility checklist before holiday traffic?

The main takeaway is to work through the basics in order, check each step as a real user would experience it, and fix patterns at their source rather than patching a single example. A short written record of what you checked makes the next review faster and more reliable.

How should I apply this guide in practice?

Pick one page, product, or routine and apply the steps there first. Note what changes, keep the change if the result improves, and only then roll the same pattern wider. Small verified changes beat a large unverified overhaul every time.

What should I check again later?

Recheck after any template, product, app, or routine change, and on a regular monthly rhythm in between. Conditions drift over time, so a dated check is what tells you whether a fix held or quietly broke again.