How CheckFox structures audits and what users can do with them.
What an audit is
One assessment of a digital service against one referential. It groups samples, criteria, findings, an accessibility statement, and reports.
Lifecycle
- Created - name, description, referential, scope, coverage and evaluation method chosen.
- Samples added - pages or screens to evaluate.
- Criteria evaluated - each applicable criterion on each sample.
- Findings recorded - verdicts, problem descriptions, fix suggestions, screenshots.
- Statement generated - from findings.
- Report exported - final deliverable.
After completion an audit can be reopened, re-audited, or archived.
Audit settings
The first step of New Audit has three blocks, plus a summary of the choices (and of required fields still empty):
- The audit (« L'audit »): name, target, description, technology, report language, referential and version, coverage, custom guideline (Pro), scope, evaluation method.
- Organisation: workspace, folder, priority, due date, ticketing tool (Jira, GitHub, Linear, GitLab or Bitbucket, among the integrations the user connected).
- Administrative (« Administratif », optional, folded by default): country and responsible body, used for the accessibility statement. See procedures / create a statement.
Details:
- Referential: RAWeb 1.1, RGAA 4.1.2, WCAG 2.2, RAAM 1.1, RAPDF 1.1, or a custom guideline. See methodology / referentials overview.
- Coverage: full, or a reduced profile of the referential.
- Report language: see procedures / export a report.
- Technology of the site: plain HTML, React, Vue, Angular, Svelte, WordPress, Drupal, other, or not set (= plain HTML). Scanner and AI code fixes use it (JSX for React, a template for Vue or Angular, a theme or the media library for WordPress). If a scan recognises a page's technology and the audit has none, the results offer to use it; nothing changes without that click.
Audit coverage
Official reduced criteria sets, chosen at creation:
- RGAA - audit rapide (25 criteria) and audit complémentaire (50 criteria, a superset of the quick set).
- RAWeb - contrôle simplifié (47 criteria).
A reduced audit surfaces non-conformities quickly. It is not a conformance audit and must not back a conformance statement. Other referentials are full-coverage only.
Coverage can be raised later (quick to complementary, or either to full), keeping findings. It cannot be narrowed.
Audit folders
Folders group audits within a workspace, for example per client or product line.
In My Audits, create a folder:

Set it up:

The folder is then browsable:

Audit versioning
Enterprise plan. Snapshots an audit at a point in time; work continues without losing the snapshot's state. Useful for re-audits. A version is like a duplicate with a direct affiliation link. Reduced audits cannot be versioned: widen coverage to full first.

Where it lives in the UI
- Operations > My Audits - list view.
- Audit page tabs: Samples, Versions, Reports, Statements.
- Audit settings: the audit's overflow menu.
Possible actions with audit
Share a public link
Share creates a read-only link, no account needed.
- Lists published issues (Failure and Derogation) by sample, criterion or impact.
- If findings have an expert proposal, a Correction view shows per issue the affected elements and the proposed fix (corrected code, or a design or content change), with a copy button per code block. Meant for whoever fixes the issues.
- Direct link: append
?view=correction. - The owner can hide it with Show the Correction view in the share dialog (e.g. remediation sold separately).
- Code from the audited site is shown as text, never run.
Duplicate audits
Copies all content, including findings, notes and image references.

Move or Copy an audit
Moves or copies the audit to a workspace or folder where you are owner or moderator.

Limits
Plan-dependent: maximum active audits and samples per audit. See plans and roles.
Related
- samples, findings, journeys, statements, reports.
- methodology / referentials overview - choosing the referential and the level.