CI mode

The same tool that powers the studio runs in your pipeline and fails the build when accessibility regresses.

An exit code your pipeline can read

Run inclusa scan <url> --ci and it scans headless with no studio, writes the report, and sets the exit code: 0 passes, 2 means the gate was breached, and 1 is an execution error. stdout is just the report path, kept machine clean, while the human verdict and progress go to stderr.

A gate you control

The gate combines the config ci block with command line flags, and flags win. The default fails on any automated failure at the target. --fail-on <impact> fails on a given impact or worse, --max-violations <n> caps the count, and --baseline <report.json> --new-only fails only on regressions against a committed baseline.

SARIF and JUnit

Inclusa emits SARIF 2.1.0 for GitHub code scanning annotations and JUnit XML for CI dashboards. It can also write the assessment PDF straight from the pipeline, so you can archive a dated assessment from a run. Triaged and disabled rules are honoured throughout.