# Heading Structure Audit

Verify that page headings expose a meaningful hierarchy, label sections accurately, support navigation, and match visual relationships in the content.

## Usage note

Audit the rendered page and its semantic heading outline, not bold styling alone. Headings support navigation for many readers, including people using screen-reader shortcuts. This worksheet focuses on content structure and cannot replace a complete accessibility evaluation, automated and manual technical testing, or conformance review against the standard applicable to your product.

## How to use this template

1. Capture the page purpose and extract every semantic heading in rendered DOM order.
2. Compare visual hierarchy, reading order, heading levels, and associated sections.
3. Review heading wording for specificity, uniqueness, and meaning out of context.
4. Test navigation with keyboard and relevant assistive technology, including dynamic components.
5. Fix page and component issues, then retest and assign regression ownership.

## Blank template

### Page outline

- **Page URL and version:** [Location/build]
- **Primary page subject:** [One sentence]
- **Application shell heading:** [If relevant]
- **Heading order source:** [DOM inspection/tool/manual]
- **Assistive technology tested:** [Name/version or Not tested]
- **Viewport/state:** [Desktop, mobile, expanded, logged in]
- **Audit owner and date:** [Name; YYYY-MM-DD]

### Heading record

- **Sequence:** [1, 2, 3]
- **Visible text:** [Exact heading]
- **Semantic level:** [H1–H6 or none]
- **Visual role:** [Page title, section, subsection, card, decorative]
- **Content governed:** [What follows]
- **Parent heading:** [Expected relationship]
- **Issue:** [Missing, vague, duplicate, wrong level, order, hidden]
- **Revision:** [Text, level, component, or removal]

### Audit checks

- [ ] Main page subject is exposed as a meaningful heading.
- [ ] Visual and semantic hierarchies describe the same relationships.
- [ ] Heading levels represent nesting rather than font size.
- [ ] Labels remain useful in a headings-only list.
- [ ] Decorative text is not announced as a heading.
- [ ] Dynamic components preserve logical order and state.
- [ ] Keyboard and assistive navigation were tested where available.
- [ ] Shared-component defects have regression coverage and ownership.