// wcag evidence reporting
WCAG accessibility reports for the pages your users actually reach.
Turn a completed, login-aware scan into a printable record of automated WCAG 2.2 A/AA findings. See exactly which public and signed-in pages were examined, what failed, and what still needs human review.
Automated evidence, not a certification or legal determination.
// example artifact
Coverage is part of the result.
A list of violations is easy to generate and easy to misread. AegisRunner leads with the page inventory, sample, authenticated reach, exclusions, and failures before presenting any criterion counts.
- Pages discovered
- 48
- Pages selected
- 12
- Pages audited
- 12
- Behind sign-in
- 5 of 5
Findings by success criterion
16 automated failures detected across the examined sample.
| Criterion | Level | Failures |
|---|---|---|
| 1.1.1Non-text Content | A | 4 |
| 1.3.1Info and Relationships | A | 3 |
| 1.4.3Contrast (Minimum) | AA | 7 |
| 4.1.2Name, Role, Value | A | 2 |
// workflow
From authenticated scan to evidence report.
Scan the real site
A real browser inventories reachable pages. Add App access once to include pages behind sign-in.
Choose a completed scan
The report phase draws a structured and reproducible random sample from that completed inventory.
Run the evidence check
A fresh browser session runs axe-core on the selected public and authenticated pages without changing application data.
Share the evidence
Open or download a printable HTML record of coverage, detected failures, WCAG criteria, exclusions, and limitations.
// what the product records
A defensible automated evidence trail.
Authenticated page coverage
Saved password access or session cookies are reused automatically. The report states how many protected pages were selected and reached.
Coverage before findings
The document leads with what was discovered, selected, audited, excluded, or unreachable so findings cannot imply broader coverage.
WCAG 2.2 criterion matrix
Findings map to WCAG 2.2 A/AA criteria, while the complete matrix keeps every criterion and its manual-review status visible.
Reproducible sampling
The structured selection, random component, method, and seed are recorded so the same inventory can reproduce the sample.
Fail-closed reporting
If important page roles or authenticated pages cannot be examined, no report artifact is produced. The UI explains what prevented it.
Review-ready evidence artifact
The report separates failures, automated passes, and axe results requiring human judgement, then prints the remaining manual-review matrix.
What AegisRunner can establish
Which sampled pages were reached, whether authenticated pages retained a session, which axe-core rules failed, how those failures map to WCAG 2.2 A/AA criteria, and which pages were excluded or could not be examined.
What still requires a person
Content meaning, quality of alternatives, keyboard and assistive-technology experience, interaction states, and complete processes. WCAG conformance applies to full pages and complete processes, so automated findings alone cannot certify it.
Read the W3C conformance requirements// faq
Questions teams ask before sharing a report.
Does this certify WCAG conformance?
No. Automated rules can detect real failures, but they cannot evaluate every WCAG success criterion or every complete user process. The report is an evidence record, not a certification or a statement of conformance.
What standard does the report use?
New reports target WCAG 2.2 Level A and AA. EN 301 549 v3.2.1 currently maps WCAG 2.1, so its clause 9 references appear only where applicable and newer WCAG 2.2 criteria are labelled not mapped.
Will it check pages behind sign-in?
Yes, when the selected scan found protected pages and the project has saved password access or session cookies. The report explicitly records how many authenticated pages were selected and successfully audited.
What happens when coverage is incomplete?
AegisRunner refuses to produce a report artifact. It shows the missing roles, inaccessible authenticated pages, failed pages, or other coverage reasons that must be addressed first.
What still needs manual review?
Keyboard operation, screen-reader experience, content meaning, alternative quality, interaction states, and complete multi-step processes still require evaluation by a person. The generated report states this limitation prominently.
Start with the pages your users depend on.
Run the site, save App access once, then generate the WCAG evidence report from the completed scan.