Supporting reports
Source reports, batch status, and delivery readiness
Use this page to verify what evidence exists behind the current cycle, which reviewed pages have fresh source reports, and whether compare or export outputs are ready.
- Report batch
- Latest batch ready
- Pages covered
- 1
- Confirmed findings
- 1
- Blocking findings
- 2
- Compare status
- Compare not ready
- Export status
- Formal export ready
Last updated May 12, 5:57 PM.
1 of 1 required families captured
5 total reported findings in the current cycle.
Use this to gauge how much of the report set still needs remediation planning.
Verification requires two completed assessment snapshots with committed storefront coverage.
Evidence Pack and Backlog Export can represent the current cycle as a formal deliverable.
Report sources
Reviewed pages with current source inputs
Each row shows the page-level report set behind the current assessment so a customer can confirm coverage before opening compare or export outputs.
Home
Axe, Pa11y, performance
- Accessibility
- 0%
- Findings
- 5
Batch and compare
Current batch status
The current workbench view keeps source freshness, coverage, and compare readiness together so the customer can tell whether this cycle is stable enough to reuse.
- Batch status
- Latest batch ready
Last updated May 12, 5:57 PM.
- Last report
- May 12, 5:57 PM
Fresh report timestamps matter because compare and export decisions should only use the latest cycle.
- Coverage
- 1 of 1 required families captured
All currently required website families are represented in the captured report set.
- Compare readiness
- Compare not ready
Verification requires two completed assessment snapshots with committed storefront coverage.
Artifacts and export
What can be reused from this cycle
Artifacts stay summarized here. The goal is to tell the customer whether the current cycle is ready for evidence, backlog, or compare deliverables without mixing in internal operations.
- Evidence Pack
- Available for remediation follow-up
Current evidence exists for customer review, even if the cycle is not yet formally deliverable.
- Backlog Export
- Remediation grouping exists
Packaged findings are ready to feed a backlog-style export for the current cycle.
- Diff Pack
- Waiting for a compatible baseline
Verification requires two completed assessment snapshots with committed storefront coverage.
- Next step
- Open formal deliverables
The current cycle has met the formal delivery bar, so the next step is to open the formal customer files.
Delivery details
Supporting Reports stays at the summary layer. Open Deliverables when you need the actual evidence, backlog, or compare files.
Compare outputs only become trustworthy when the current and baseline cycles cover the same required website families.
Formal exports stay gated by current-cycle coverage and evidence quality, even when draft remediation material already exists.