Free tool
Free Accessibility Statement Generator
Fill in one form and get an accessibility statement written to the W3C model: your conformance target, how you assessed the site, what you know falls short, and how people reach you. Ready to paste as HTML or copy as plain text.
This generator runs entirely in your browser. Nothing you type is sent to Sitejar, stored, or logged.
Example output
Accessibility statement for Acme Ltd
Conformance status
We aim to conform to WCAG 2.2 at level AA. This is a statement of intent, not a certification.
How we assessed this site
We assessed acme.example using a combination of automated testing tools and manual review.
Known limitations
Some older PDF documents are not fully tagged. Video published before 2024 has no captions.
Feedback and contact
If you find a barrier, contact us at [email protected].
Date of this statement
Prepared on the date you choose, and reviewed at least once a year.
Illustrative, for a fictional company. Your own statement replaces this panel when you generate it.
When you generate
Paste the HTML
A clean fragment starting at a level 2 heading, with no classes and no inline styles, so it takes on your own site design.
Copy the plain text
The same document with no markup at all, for a CMS or a form that refuses HTML.
Download a text file
Named after your organisation, ready to hand to whoever owns the page.
Nothing you type leaves your browser.
The short answer
What is an accessibility statement?
The one-paragraph version, before the detail.
An accessibility statement is a page on your website that says which accessibility standard you are working towards, how you checked the site against it, what you already know falls short, and how somebody can tell you when they hit a barrier. It is a public declaration of intent and effort, not a certificate: it does not prove your site is accessible, and no statement can. In the European Union the Accessibility Act has required one from in-scope services since June 2025, and in most other places publishing one is standard practice and the first thing an auditor looks for.
The anatomy
What a good statement includes
Eight parts a reader and a regulator both expect. The generator writes the first six; the last two are short additions worth making by hand.
01
A named conformance target
Which standard you are working towards, at which level: WCAG 2.1 or 2.2, level A, AA or AAA. Without a target, every other sentence in the document is unmeasurable.
02
How you assessed the site
Self-assessment, automated testing, an external audit, or a combination. A reader weighs the claim by the method behind it, so the method is part of the claim.
03
Known limitations, stated plainly
The parts you already know fall short, and what you are doing about them. Naming a barrier is what makes the rest of the document credible: a statement with nothing to admit reads as one nobody checked.
04
A real feedback route
An address a person can write to when they hit a barrier. Under the European Accessibility Act this is not decoration: the statement has to tell people how to report a problem.
05
The date it was prepared
When the assessment happened, not when the page was last rebuilt. An undated statement tells a reader nothing about whether it still describes the site in front of them.
06
The scope it covers
Which site, and which parts of it. A statement that quietly covers the marketing pages while a reader is stuck in the checkout is worse than no statement at all.
07
Compatible assistive technologies
The screen readers, browsers and operating systems the site was tested with, and the combinations you aim to support. A conformance claim with no test environment behind it cannot be reproduced by anyone, which is the difference between a record and an assertion.
08
Formal approval and preparation method
How the statement itself was put together: a self-assessment, or an evaluation by a third party, and when it was last reviewed. Public sector bodies in the EU and the UK must also name who formally approved it. This part is about the document, not the site: how the pages were assessed is its own part above.
Obligations
Which laws require or expect one
Six instruments that name a statement, or name the standard a statement cites. Whether any of them binds you depends on your sector, your size and where you operate, and nothing here is legal advice.
European Union
European Accessibility Act
Directive (EU) 2019/882 applies to a broad set of consumer products and services sold in the EU, including e-commerce, banking, transport and e-books. Its obligations became enforceable on 28 June 2025.
Requires a published accessibility statement, including how to report a barrier.
European Union
EN 301 549
The harmonised European standard that the Accessibility Act and the Web Accessibility Directive both point at. It incorporates WCAG 2.1 level AA as its technical requirement for web content.
Defines the target a European statement names, and supplies the model wording.
United States
Americans with Disabilities Act
The ADA is widely applied to digital services through Title II and Title III. The Department of Justice rule under Title II sets WCAG 2.1 level AA as the target for state and local government web content, on fixed deadlines.
Does not mandate a statement. Publishing one is standard practice and evidence of effort.
United States
Section 508
Section 508 of the Rehabilitation Act binds federal agencies and, through procurement, the vendors that sell to them. It incorporates WCAG 2.0 level AA as its technical standard.
Expects a conformance claim, usually as an ACR or VPAT alongside a public statement.
Canada
AODA, Ontario
The Accessibility for Ontarians with Disabilities Act requires WCAG 2.0 level AA for public websites of designated organisations, with accessibility reporting on a fixed cycle.
Requires periodic compliance reporting, which a maintained statement feeds directly.
United Kingdom
Equality Act 2010
The Equality Act requires reasonable adjustments for disabled people, and the public sector accessibility regulations add a published statement on top of it for public bodies.
Requires a statement in the public sector, and expects evidence of effort everywhere else.
European Union
Web Accessibility Directive
Directive (EU) 2016/2102 covers the websites and mobile applications of public sector bodies across the EU, measured against EN 301 549. Its deadlines have all passed: 23 September 2019 for sites published from 23 September 2018, 23 September 2020 for older sites, and 23 June 2021 for mobile applications.
Makes a statement mandatory, and Commission Implementing Decision (EU) 2018/1523 sets the model it must follow.
United States
Unruh Civil Rights Act, California
California Civil Code section 51 treats a violation of the ADA as a violation of state civil rights law, and section 52 sets statutory damages of no less than $4,000 per offence. That combination is why a large share of United States web accessibility litigation is filed in California.
Does not require a statement and does not create a defence. A dated statement with a remediation plan is evidence of a good faith effort, which is a weaker thing than compliance.
The honest part
A statement is a claim. It is not compliance.
Publishing one is the right thing to do. It is also the easiest half of the job.
Everything above is something you assert about your own site. Nobody checked it on the way out, and the generator above cannot check it either: it has never seen your pages. That is the whole reason its wording says you aim to conform rather than that you do.
A statement that names a target the site misses is worse than none, because it is a documented claim that is straightforward to disprove. The way to make it safe is not softer wording. It is to find out where you actually stand, fix what is broken, and write the statement from the result.
Backed by a real scan
Want a statement based on a real scan of your site, not a template?
Sitejar crawls your site, evaluates it against 49 documented rules across six dimensions, and generates an accessibility statement from what it actually found: the confirmed barriers named, the pages counted, the assessment date real. Every sentence in it is one you can stand behind.
See plans and get startedStatement generation is a paid feature. Start with a free scan first if you would rather see the findings.
Scope
This generator, and a real Sitejar scan
One writes a document from what you tell it. The other writes one from what it measured. This page is honest about which is which.
| What you get | This generator | Full scan |
|---|---|---|
| What it produces | A statement you write | A statement built from measurements |
| Names a conformance target | Included | Included |
| Reads the pages on your site | Not included | Included |
| Lists barriers actually found | Not included | Included |
| Rules evaluated | None: it is a declaration | 49 documented rules |
| All six dimensions | Not included | Included |
| Exportable evidence | Not included | Included |
| Account needed | No | Yes |
FAQ
Straight answers.
Including the one people most want to hear a different answer to.
Is an accessibility statement legally required?
Where do I put the statement on my site?
Does publishing a statement protect me from lawsuits?
How often should I update it?
Can I say my site is WCAG compliant?
Scan-backed statements
Generate a scan-backed statement.
Stop declaring a target and start measuring against it. One scan reads every page across six dimensions and 49 documented rules, then writes the statement from what it found.
Not ready to pick one? Scan your site free first. No account, up to 5 pages.