Create a new audit, ready to receive samples.
Cette documentation est disponible en anglais uniquement.
Goal
Create an audit in the active workspace, ready for samples and findings.
Preconditions
- Signed in as an Owner, Moderator or Editor of the target workspace, or as a Reader allowed to create audits.
- The workspace is under its active-audit limit and its audits-per-year limit.
Steps
Three form steps: audit information, items to audit, review.
- Click New Audit in the navigation.
- Enter a name (service or product audited) and optionally a description with scope notes.
- Enter the website or target; pick the workspace.
- Pick the accessibility guideline and version: RAWeb, RGAA, WCAG, RAAM (mobile applications), RAPDF (PDF documents), or a workspace custom guideline. See methodology / referentials overview.
- Pick the scope: full website, web artifact, PDF document, mobile app, or custom.
- Pick the coverage. Full checks every criterion; RGAA also offers quick and complementary audits, RAWeb the simplified control. Reduced coverage is a fast non-conformity check and cannot back a conformance statement.
- Pick the evaluation method: manual, automated or hybrid (most audits). It appears in the accessibility statement.
- Optional: priority, due date, language of the evaluation, country and responsible body (used later by the statement).
- Add first items to audit, or skip and add samples later (product / samples).
- Review and create.
Audits can be put in folders from My Audits at any time.
Start from an official evaluation grid
Import from an XLS file imports an audit recorded in an official grid.
- Grids: RGAA, RAWeb, RAAM (mobile applications);
.xlsx,.xlsor.ods, max 10 MB. RAPDF has no official grid, so cannot be imported. - The referential is read from the file and fixed (criterion numbers only mean something in their own referential). The version can change; it is preselected to the file's version or the closest CheckFox has.
- Each page (RGAA, RAWeb) or screen (RAAM) becomes a sample. Blank template screens start unticked; tick or untick samples before importing.
- Imported per criterion: status, derogations, failure description.
- Text on a criterion marked compliant becomes a note on it, not a failure description; a RAAM "Patch follow-up" becomes its own note. These notes are team-visible and left out of the report and statement.
- Refused: more samples than the plan's sample limit, or an unidentifiable referential.
Verify success
- The audit is in the workspace's audit list.
- Its header shows the chosen guideline and coverage.
- Its Samples, Versions, Reports and Statements tabs open.
Common pitfalls
- Reduced coverage for work that must end in a statement. Coverage can be widened, never narrowed: when in doubt, start full.
- Forgetting scope notes. Easy to skip upfront, expensive to reconstruct.
- Creating audits in a personal workspace for collaborative work. Personal workspaces have one member only.
Related
- product / samples, product / journeys - what to add next.
- methodology / audit process - the full audit process.
- methodology / referentials overview - which referential to pick.