Conformance

A clean scan is not, on its own, a WCAG conformance claim — and pretending otherwise is exactly the kind of overreach this engine refuses to make. This section covers how individual rule results actually roll up to a Success Criterion verdict, what that verdict honestly does and doesn't cover, and how to gate a real CI pipeline on known, already-reviewed violations instead of blocking every build until everything is fixed at once.

WCAG conformance mapping

See exactly how atomic rules, coverage facets, and composite WCAG-SC rollup rules fit together, so a composite pass means something specific rather than a vague "looks fine." Target a conformance level (A, AA, or AAA) across any WCAG version with one tag set, and get a straight answer to the question that actually matters: what can this kind of automated result tell you, and where does it stop. See WCAG conformance mapping.

Baseline / allowlist

Don't let a first scan of an imperfect, existing site block every future build — record what's already known once, and gate CI only on violations that are genuinely new. It's the difference between "we can't ship anything until this is perfect" and "we can catch regressions starting today," and it's what actually gets a team to turn the gate on. See Baseline / allowlist.