How to use notes to communicate with your team, document decisions and prepare statements.
Why notes matter
Verdicts and findings record what; notes record why: the auditor's reasoning, for future-you, teammates, developers reading the report, and disabled users reading the public statement. Each note level reaches a different reader.
The three levels of notes
1. Audit-level notes (global)
Scope: the whole audit. Reminders for you or teammates, not user-facing: scope decisions, environment (browser, screen reader), open team questions, re-audit reminders.
2. Sample-level notes
Scope: one sample. What applies to all the page's findings: authentication state, page quirks, why the sample was selected.
3. Criterion-level notes (per-finding)
Scope: one (sample, criterion) pair. Typically internal, the why of a verdict: justifying a borderline one, what was tested and how, alternative interpretations for the next auditor.
Who can see a note
Visibility is set per note, independent of level: Only me, Workspace (all workspace members), or Anyone invited (anyone with access to the audit, guests included). CheckFox refuses a private note marked for the report or statement.
Notes that travel: report notes vs. statement notes
Two independent per-note toggles publish a note; it can carry both.
Notes for the report
Appear in the audit report and Excel exports, beside findings and proposed solutions. Audience: the team fixing or explaining the issues; write running commentary for them.
Notes for the statement
Appear in the public Accessibility Statement. Audience: disabled users (and others) deciding whether they can use the service. Explain what is wrong, clearly and plainly - do not justify or minimize.
- Bad: "Some images may have suboptimal alternative text in certain edge cases."
- Better: "Several product images in the catalog do not have descriptive alternative text, so screen reader users may not know what the product looks like."
Mention here any alternative way to reach the same information:
- "The interactive map on the Contact page is not accessible to keyboard users. The full address and opening hours are available in text directly below the map."
- "The video tutorial does not have captions yet. A written transcript is linked under the video."
Anti-patterns
- Mixing levels. Team reminders stay out of the statement; borderline-verdict justifications stay out of the developer report.
- Defensive statement notes. "We are committed to accessibility" is filler. State the issue.
- Empty notes. "See finding" adds nothing.
- Hidden context. Reasoning kept in memory is lost next round. Write it at criterion level.
Where to put what - quick reference
| You want to... | Use |
|---|---|
| Remind yourself or a teammate about audit scope | Audit-level note |
| Document the auth state or sampling reason for a page | Sample-level note |
| Justify a borderline verdict | Criterion-level note |
| Give developers extra context for the fix | Note for the report |
| Tell disabled users what is wrong and what alternative exists | Note for the statement |
Related
- audit process - where notes fit in the audit phases.
- finding quality - finding text vs. note text: the boundary.
- statement quality - statement notes feed directly into it.