Semantic landmarks (main, nav)

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 semantic landmark roles (main, nav, contentinfo)",
  "description": "The bracket page must expose at least the main, nav, and contentinfo landmarks (as <main>, <nav>, <footer> or their ARIA-role equivalents) so screen-reader users can skip between regions. Catches the common all-div soup where screen readers have to linearise the entire page to find the bracket.",
  "priority": "p1",
  "metadata": {
    "category": "accessibility",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Navigate to the homepage"
    },
    {
      "type": "assertion",
      "description": "Verify the page exposes a single main landmark (either a <main> element or a container with role='main') that wraps the bracket section"
    },
    {
      "type": "assertion",
      "description": "Verify the page exposes a nav landmark (either a <nav> element or a container with role='navigation') containing the top-level site navigation links"
    },
    {
      "type": "assertion",
      "description": "Verify the page exposes a contentinfo landmark (either a <footer> element or a container with role='contentinfo') containing the page footer"
    }
  ]
}