Cypress AccessibilityPremium Solution
Connect & extend
Cypress Accessibility results don't have to stay in Cypress Cloud. This section covers the ways to get a run's results into a file, a CI check, an AI agent, or a reporting system, so you can analyze and act on them wherever you already work.
Ways to get your data​
| Method | Best for | Interface |
|---|---|---|
| Download report | A one-off, manual export of a single run's violations for offline analysis, sharing, or AI agents. | .csv or .json file |
| Webhooks | Push Cypress Accessibility results to your own endpoint when the report finishes processing. | run.accessibility.completed |
| Results API | Automated pass/fail checks in CI that assert on results and block pull requests. | Node module (@cypress/extract-cloud-results) |
| Cypress Cloud MCP | Live, interactive querying by AI agents while you work in your editor. | MCP tools |
| Data Extract API | Bulk analytics and trends across projects and over time, pulled into BI or a data warehouse. | API and Enterprise Reporting downloads |
Which should I use?​
- For a single run's results, use the Download report button. The file works offline with any tool or AI agent.
- To enforce a standard in CI, use the Results API to assert on a run's results and block pull requests that don't meet it.
- To work with an AI agent, use a downloaded report for the full dataset or Cypress Cloud MCP to query results live. See Work with AI agents.
- To push results when a report finishes, use Webhooks. The
run.accessibility.completedevent can start other workflows in this list. - To get results into your issue tracker, have an agent read the latest report for a branch, check what is already filed, and open only the missing tickets. See File issues in your issue tracker.
- To track trends across runs and projects, use the Data Extract API and Enterprise Reporting.