How CheckFox structures audits and what users can do with them.
What an audit is
An audit is one assessment of a digital service against one referential at one conformance level. It groups samples, criteria, findings, journeys, an accessibility statement, and a report.
Lifecycle
- Created — name, description, referential, level chosen.
- Samples added — pages or screens to evaluate.
- Criteria evaluated — each applicable criterion is reviewed on each sample.
- Findings recorded — verdicts, problem descriptions, fix suggestions, screenshots.
- Statement generated — accessibility statement built from findings.
- Report exported — final deliverable.
An audit can be reopened, re-audited, or archived after completion.
Audit settings
- Name and description
- Referential (WCAG 2.2 / RGAA 4.1 / RAWeb 1.1 / others). See methodology / referentials overview.
- Conformance level (A / AA / AAA)
- Scope notes (free text describing what is and is not in scope)
- Visibility within the workspace
Audit folders
Audits can be organized into folders within a workspace. Useful when an agency or in-house team is auditing multiple clients or product lines. See /docs/audit-folders.md for the full design.
Audit versioning
Available on Pro and Enterprise plans. Lets the auditor snapshot an audit at a point in time and continue iterating without losing the snapshot's state. Useful for re-audits.
<!-- needs review: confirm exact plan gating for versioning -->Where it lives in the UI
- Sidebar > Audits — list view.
- Audit page tabs: Samples, Findings, Statement, Report.
- Audit settings accessible from the audit's overflow menu.
Limits
Plan-dependent: maximum number of active audits and maximum number of samples per audit. See plans and roles.