How to inspect a webpage's heading structure
Headings help readers and assistive technology understand how a page is organized. A heading inventory makes it easier to spot unclear hierarchy or sections whose labels do not describe their content.
Start with the right material.
- What you provide
- current page inspected through approved read-only DOM code.
- The intended result
- Export heading levels and text, flagging missing or skipped structure for review.
How the workflow works.
Record the heading text and level in page order. Consider whether the relationship between sections is understandable rather than treating every numbering jump as the same kind of problem.
What to check in the result.
Review the actual content around a flagged heading before changing it. Visual size and semantic heading level can differ, so inspect the markup when the supplied view is incomplete.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Position, Level, Heading, Observation. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.