GET/v1/scans/scn_01J…/diff?baseline=scn_01H…
baseline_scan_id = scn_01H…
scan_id = scn_01J…
profile = wcag-2.2-aa-web@1.2.0
match = deterministic fingerprint
3 new · 7 recurring · 4 resolved
The accessibility baseline comparison API accepts a compatible prior scan ID as the baseline. It compares deterministic fingerprints so teams can isolate regressions without hiding accepted work or rewritten history.
For teams adopting accessibility controls in products with an existing issue backlog
IllustrativeThe comparison endpoint returns classifications beside the current finding identity and resolved technical profile.
GET/v1/scans/scn_01J…/diff?baseline=scn_01H…
baseline_scan_id = scn_01H…
scan_id = scn_01J…
profile = wcag-2.2-aa-web@1.2.0
match = deterministic fingerprint
3 new · 7 recurring · 4 resolved
A baseline is useful when every delta state has a named disposition instead of disappearing into one total count.
| Signal | Disposition | Owner |
|---|---|---|
| New fingerprint | Evaluate gate threshold | CI |
| Recurring fingerprint | Keep backlog assignment | Product team |
| Resolved fingerprint | Retain verification | Evidence archive |
| Changed profile | Review comparability | Accessibility lead |
A project can block regressions today while the full backlog remains available for prioritization, remediation, and later threshold changes.
failedBaseline comparisons remain interpretable when both scans use compatible profile and rule versions. Pin that technical target before fingerprints are compared.
Compare a baseline and current scan in a free workspace, then bring the same fingerprints into a release gate when the team is ready.
Automated preflight is not an accessibility certification or legal determination.