Baseline diff

The most useful accessibility question is rarely how many issues are there. It is did this change make things worse. Baseline diff answers it.

New, fixed, still present

Pick any saved report as a baseline, and the active report is shown as new regressions, fixed issues, and findings that are still present, alongside a conformance delta that tracks failing node movement. You see at a glance whether a change cleared issues, introduced them, or left them where they were.

Stable identity across scans

Findings are matched by rule id, a normalised page path, and selector, so staging lines up with production and a trailing slash difference does not show as a spurious change. The comparison is computed entirely on the client from two already loaded reports, and the compare picker reuses the existing project file tree.

The basis for the CI gate

The same diff drives the new only mode of the CI gate, so a pipeline can fail on regressions against a committed baseline while tolerating known, pre existing findings.