Heading hierarchy (one h1)

What TestSprite reads

The testing agent reads this JSON, opens the deployed URL in headless Chromium, executes each action step, evaluates each assertion. Verdict: passed / failed / blocked / inconclusive.

{
  "projectId": "1ad26753-ee03-4689-8f0f-6fa5d67c5c72",
  "type": "frontend",
  "name": "Accessibility — page uses an ordered heading hierarchy (one h1, no skipped levels)",
  "description": "The bracket page must have exactly one <h1>, and the rest of the headings (<h2>, <h3>, …) must descend without skipping levels. Catches the common pattern where decorative styling drives heading choice and a page ends up with h1 → h3 → h2 → h4, which breaks screen-reader navigation.",
  "priority": "p1",
  "metadata": {
    "category": "accessibility",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Navigate to the homepage"
    },
    {
      "type": "assertion",
      "description": "Verify the page contains exactly one <h1> element"
    },
    {
      "type": "assertion",
      "description": "Verify all heading levels on the page form an ordered sequence — i.e. after an <h1>, only <h2>s appear before any <h3>; after an <h2>, only <h2>s or <h3>s appear before any <h4>; etc. No level is skipped on the way down"
    }
  ]
}