Kilotest: Diagnoses of heading level skipped violation by HTML element 1007 on Run! page

Here is how tools diagnose the heading level skipped issue for HTML element 1007 of the Run! page.

Basics

• About the heading level skipped issue
  • Why it matters: Helper misdescribes the document
  • Priority: low
  • Related WCAG standard: 1.3.1
• About the Run! page
  • URL: https://www.designedtorun.com/
  • Tested on 2026-04-05 at 01:26
• About HTML element 1007
  • Take me there
  • Tag name: H6
  • Text: 651 N Broad St., Suite 201 … Middletown, DE 19709
  • Start tag: <h6 class="MuiTypography-root MuiTypography-subtitle1 css-e3gdml">
  • XPath: /html/body/div[1]/div[1]/footer[1]/div[1]/h6[1]
  • Bounding box: x = 601, y = 9996, width = 719, height = 40

Diagnoses

1. Heading levels should only increase by one; Heading order invalid

   Tool: Axe (Deque)

   Rule: heading-order

2. <p>Headings and subheadings create a <a href="https://www.w3.org/WAI/tutorials/page-structure/headings/" target="_blank" title="Opens in new tab">navigable table of contents</a> for assistive devices. The numbers indicate indents in a nesting relationship:</p> <ul> <li>Heading level 1 <ul> <li>Heading level 2: a topic <ul><li>Heading level 3: a subtopic</li></ul></li> <li>Heading level 2: a new topic</li> </ul> </li> </ul> <p>This heading skipped from level 3 to level 6. From a screen reader, this sounds like content is missing.</p> <p><strong>To fix:</strong> adjust levels to form an accurate outline, without gaps.</p>

   Tool: Editoria11y (Princeton University)

   Rule: headingLevelSkipped

3. The heading h6 (with computed level 6) follows the heading h3 (with computed level 3), skipping 2 heading levels.

   Tool: Html Checker API (World Wide Web Consortium)