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

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

Basics

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 4 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 h4 (with computed level 4), skipping 1 heading level.

    Tool: Html Checker API (World Wide Web Consortium)

  4. Headings are not in a semantically correct order.

    Tool: WallyAX (Wally)

    Rule: Maintain a logical order by only increasing heading levels by one.