Writing an accessibility statement in 4 sections — copyable template

The accessibility statement is a public, mandatory and legally binding document. Public: it must be reachable from every page, typically at `/accessibilite`. Mandatory: the EAA and the RGAA require it of every e-commerce service concerned. Binding: what you write commits your responsibility — a false statement aggravates the sanction instead of softening it. Good news: it fits in 4 sections and takes about thirty minutes to write, once the audit is done.

Section 1 — Compliance status

Three possible values: Full (100% of criteria), Partial (50 to 99%), Non-compliant (under 50%). Also state: the exact estimated rate, the framework (RGAA 4.1), the method (self-assessment or third-party audit) and the date of the last audit. A dated rate is far better than a vague phrase: it proves you measure.

What to write

"The site is partially compliant with RGAA 4.1. Estimated compliance rate: 73%. Assessment carried out on 12 May 2026 by automated audit supplemented with a manual check."

Section 2 — Non-compliant content and exceptions

List the known non-compliant content, and for each: the reason and the planned fix date. Three exception grounds are accepted by the RGAA — but you have to name them correctly.

• →Simple non-compliance: a criterion fails, you'll fix it — give a deadline
• →Disproportionate burden: the fix is out of proportion with your means — to be justified, not invoked lightly
• →Uncontrolled third-party content: payment widget, interactive map, embedded customer-reviews module

Section 3 — Accessibility contact

A dedicated address (for example an accessibility inbox on your domain) and an announced response time (15 days is the recommended practice). This address MUST receive a real human reply: it's the very first test a complainant runs — and its silence is often what turns a report into a formal complaint.

Section 4 — Means of appeal

Mandatory mention: if the user doesn't get a satisfactory reply, they can refer the matter to the Défenseur des droits (defenseurdesdroits.fr). This means of appeal must appear explicitly; its absence is itself a breach.

Ready-to-paste template

<h1>Accessibility — statement</h1>

<h2>Compliance status</h2>
<p>[Site name] is partially compliant with RGAA 4.1.
Estimated rate: 73%. Audit of 12/05/2026.</p>

<h2>Non-accessible content</h2>
<ul>
  <li>Customer-reviews module (third-party) — uncontrolled</li>
  <li>Catalogue images — fix planned Q3 2026</li>
</ul>

<h2>Contact</h2>
<p>accessibility@[your-domain] — reply within 15 days.</p>

<h2>Means of appeal</h2>
<p>Without a satisfactory reply: refer to the Défenseur des
droits — defenseurdesdroits.fr</p>

Frequently asked questions

Where to host the statement?

On a dedicated, stable page, ideally `/accessibilite`, accessible from the footer of every page. The footer link is also expected by the authorities.

How often to update it?

At every audit, and at least once a year. The rate and date must reflect the current reality; a statement frozen for two years is a negative signal.

Can I declare myself compliant without a third-party audit?

Self-assessment is allowed and must be mentioned as such. But in case of a dispute, an independent, timestamped audit carries far more weight than a self-declaration.

What does a false statement risk?

The combination: the sanction for RGAA non-compliance, plus the risk of an advertising or misleading-commercial-practice qualification — precisely the ground on which the FTC fined an overlay vendor $1M.