Overview

CORA is Vispero’s accessibility tooling for web developers. It scans your app’s pages in Google Chrome, fails pull requests that add accessibility violations, and lets coding agents find and fix them.

These docs describe one minor release, the one their address names, such as /docs/0.6/ for every 0.6 release. Each docs link that cora and cora-mcp print, such as an error’s docs: line, opens the docs of the release that printed it.

What CORA checks

CORA checks each page with axe-core’s rules, against WCAG success criteria and accessibility best practices. It checks the page’s main document, its iframes and its open shadow roots. The rules reference lists every rule, and which run by default. The config’s rules changes which run.

Note

Automated rules find only some accessibility issues. A scan that finds none does not show that a page is accessible, or that it conforms to WCAG.

How the pieces fit

1. cora scan opens each page in Chrome, waits for it to settle, and runs the rules. Scanning with cora scan covers targets, crawls and waits.
2. The results file records what the run covered and every finding. Each run writes one to .cora/runs/ in the project, or in the folder you run it in when you scan without a project (Scanning without a project).
3. The baseline and the gate. cora.baseline.json accepts the violations a project has today. The gate then fails a run only on new ones. See Baselines and the gate.
4. CI runs the same command. It also writes a report directory: a SARIF log for code scanning, and a Markdown summary. Under GitHub Actions, it annotates the run. See Running in CI.
5. Coding agents scan through @vispero/cora-mcp, an MCP server. CORA’s plugin for Claude Code and Codex runs a fixer agent that fixes each issue and checks the fix in the browser. See Coding agents.
6. Source stamps. CORA’s build plugin for Vite, webpack, Rspack, Rsbuild, Rollup, Rolldown or esbuild stamps each element with its place in your source, and in an Angular app Angular’s compiler writes it, so a finding names the file and line to fix. See Source locations.

The packages

The two packages release together, at one version.

Package	What it holds
@vispero/cora	The cora CLI, @vispero/cora/config to type cora.config.ts, its build plugins for Vite and six other bundlers, and CORA’s plugin for coding agents. Install it in a project as a devDependency, or run it with npx from any folder.
@vispero/cora-mcp	The MCP server that coding agents start with npx. It is never installed in a project.

Where to start

Getting startedScan a site from any folder, or install cora, set up a project, sign in and scan a first page.

Running in CIGate pull requests on new violations, and upload the report.

Coding agentsScan and fix from Claude Code and Codex.

ConfigurationChoose targets and rules, sign in to your app, and start its server.