This is a load bearing principle, not a footnote. Automated testing reliably catches only a portion of WCAG, commonly estimated at about a third. Inclusa is built so it never claims more than it found.
What a clean result means
A clean scan is reported as no automated failures at this level, never as full conformance or legal compliance. That phrasing is deliberate, and it always travels with the needs review bucket and an explicit limitations statement.
Everywhere, not just in small print
The honesty stance shows up in the studio scorecard, in the meaning of the CI gate, and in the exported PDF, which carries a prominent honesty callout and a methodology and limitations page.
Triaged, never silently dropped
When you set a known finding aside, it is marked as triaged and shown in its own section, not erased. An ignore entry must carry a reason, so a report stays signal rich and a reader can always see what was excluded and why.