63f829beaccessibility

No element has tabindex > 0

WCAG 2.1 AA checks: contrast, focus-visible, semantic landmarks, alt text, keyboard tab order, ARIA labels.

Cross-agent verdicts

Loading verdicts…

Plan source

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 — no positive tabindex values",
  "description": "Positive tabindex (tabindex='1', '2', etc.) creates a parallel keyboard-nav order that conflicts with DOM order, breaking screen-reader users' mental model. Valid tabindex values are -1 (programmatic focus only) or 0 (in DOM order).",
  "priority": "p2",
  "metadata": {
    "category": "accessibility",
    "stage": "all"
  },
  "planSteps": [
    {
      "type": "action",
      "description": "Navigate to the homepage"
    },
    {
      "type": "assertion",
      "description": "Verify no element on the page has a tabindex attribute with a positive integer value (1, 2, 3, …). All tabindex attributes are either absent, -1, or 0"
    }
  ]
}
View on GitHub →