Definition of Done (Report)
Use this checklist to decide when an accessibility report is ready to publish.
1) Scope and goals are clear
- The report purpose is stated in plain language.
- The audience (maintainers, contributors, users, procurement, etc.) is identified.
- The time period covered by the report is defined.
- Success criteria are explicit (what “good” looks like).
2) Evidence is complete and traceable
- Findings are tied to concrete evidence (issue links, commits, CI logs, test runs, screenshots, or notes).
- Every claim can be traced to a source.
- Known limitations and assumptions are documented.
- Open risks and unresolved items are listed with owners.
3) Accessibility quality checks are included
- Relevant WCAG 2.2 AA criteria are referenced for key findings.
- Automated checks are reported (or marked “not run” with a reason).
- Manual checks are reported (keyboard and screen reader spot checks at minimum).
- For layout or keyboard-focus changes, Reflow risk (320 CSS-pixel-equivalent viewport) and behavioral Focus Visible testing were applied per Behavioral Accessibility Automation, with indicators reviewed and any exceptions or unresolved
cantTellresults recorded — not treated as conformance. - If the report covers many pages, components, or a fleet-wide scan, findings are grouped into probable root-cause clusters and reported as unique findings with affected-instance counts, not one row per affected page (see Behavioral Accessibility Automation §3.2).
- Critical or High accessibility issues are clearly flagged.
4) Actions and accountability are defined
- Each recommendation has a clear owner.
- Priority/severity is assigned (Critical/High/Medium/Low).
- Target timelines or milestones are defined.
- Follow-up tracking method is stated (issues, project board, roadmap).
5) Publication readiness is met
- The report is internally reviewed.
- Language is concise, inclusive, and actionable.
- Links resolve correctly.
- AI assistance is disclosed if used.
Done criteria
The report is done when all checklist items above are complete, or when any exceptions are explicitly documented with:
- a reason,
- an owner, and
- a target date for closure.