Does the statement have to match the audit scope exactly?

Yes. If the statement includes pages/services that were not audited, the document becomes inconsistent and harder to defend. Keep scope and evidence aligned.

Are exemptions always a last resort?

Exemptions are legitimate when a specific context applies, but they must be justified and tied to the findings and your improvement plan.

How can RGAAudit.com help teams?

RGAAudit.com helps you run an automated RGAA 4.1.2 audit, organise findings by themes, and generate a draft statement-ready workflow. You still need to review and complete the required sections.

Accessibility statement checklist (DINUM)

A statement is only credible if it matches your audit findings and your reality on the ground. Use this checklist to produce a consistent accessibility statement (DINUM model): scope, exemptions, and a real action plan.

1) Scope: keep it precise

List the exact services/pages covered by the statement.
Define what was actually audited (and what was not).
Document edge cases (e.g., pages with special rendering or protected areas).

2) Evidence: turn findings into “decisions”

Don’t paste a report. Convert findings into actions: what you fixed, what you plan to fix, and what requires an explicit decision (including manual validation areas).

Use thematic grouping (images, keyboard navigation, forms, etc.).
Make sure manual criteria decisions are traceable to a context review.
Keep terminology aligned with the RGAA audit workflow.

3) Exemptions: justify with clarity

Exemptions are not “default”. They should be: specific, understandable, and tied to your findings.

Explain why the situation exists (cause).
State what is impacted (pages/components/criteria).
Describe what happens next (correction plan or workaround strategy).

4) Action plan: make it usable

Define “what”, “when”, and “how” for each improvement bundle.
Prefer patterns/components-based correction to avoid repeating the same work.
Plan re-validation after each important correction wave.

5) Review & maintain

Do a second pass to ensure consistency between audit scope and statement scope.
Update when you have a major refactor, new features, or a significant correction milestone.
Keep the statement readable for non-technical stakeholders.

Quick checklist (ready-to-publish)

Scope matches the pages/services you actually audited.
Exemptions (if any) are justified and linked to findings.
The action plan is realistic and maintainable by your team.
Manual decisions are validated with context (not guessed).
You plan revalidation after meaningful changes.

Where RGAAudit.com fits

RGAAudit.com helps you run an automated RGAA 4.1.2 audit and organise results by theme. It can accelerate your workflow toward a statement-ready process—but your team must still review and complete the required sections. If you want a fast start, install the extension and begin with an audit on representative pages.

Next step: check our keyboard-only testing checklist to validate what matters most for real users.