Annex V, Directive (EU) 2019/882 · O. Reg. 191/11 · Equality Act 2010
Accessibility statement generator: what it gives you, and what it cannot.
A generator writes a paragraph in thirty seconds. The law asks for something a paragraph cannot contain: the result of a real test of your website, the barriers that are still there, the date, and a working way for a user to report a problem. This page explains exactly what belongs in a statement in the EU, in Ontario and in the UK, what a generated text leaves out, and how a tested and signed record is built instead.
Seven days free, no card. Signed in five business days.
What a generator is, honestly
An accessibility statement generator is a form. You type the name of your organisation, an email address, sometimes a date, and it returns a block of text that says you are committed to accessibility and that your site conforms, or partially conforms, to WCAG. The text is grammatical, it looks like every other statement on the internet, and it takes half a minute.
There is nothing wrong with that as a layout. The problem starts where the layout meets the legal text. The European Accessibility Act does not ask you to publish a commitment. It asks, in Annex V, for a description of how the service meets the accessibility requirements, and that description has to correspond to the service as it actually is. Ontario's O. Reg. 191/11 does not ask for a paragraph either: it asks organisations with twenty or more employees to make their web content conform to WCAG 2.0 level AA and to be able to state so. The UK route runs through the Equality Act and the duty to make reasonable adjustments, where what matters in a dispute is what you did, not what you wrote.
So a generated statement is an answer to a question nobody asked. It fills the page. It does not create the evidence behind the page.
What has to be inside a statement, by jurisdiction
The three regimes we cover ask for different things. Any text that pretends one paragraph satisfies all three is wrong in at least two of them.
| Element | European Union, Annex V | Ontario, AODA | United Kingdom |
|---|---|---|---|
| Description of the service | Required, in plain language | Expected in the accessibility policy | Expected in procurement answers |
| Conformance level claimed | Against the applicable requirements | WCAG 2.0 AA for web content | WCAG 2.2 AA by convention |
| Known barriers | Required, with alternatives offered | Expected in the multi-year plan | Central to reasonable adjustment |
| Feedback mechanism | Required and it must work | Required, with a process behind it | Required in practice |
| Date and review | Required, kept current | Report filed on the legal cycle | Expected, dated evidence |
| Who stands behind it | The economic operator | The organisation filing | The service provider |
Read the second row of that table again. A generator asks you which level to claim, and then writes what you chose. You are the one certifying, from a dropdown, a fact about software you did not test.
The five things a generator cannot know about your site
Whether the keyboard works
Most real failures are here: a menu that opens on hover only, a modal that traps focus, a carousel that cannot be stopped, a custom dropdown that a keyboard cannot reach. None of it is visible in the markup a scanner reads.
What a screen reader announces
An icon button with no accessible name is announced as “button”. A form error shown in red with no programmatic link is silence. These are the barriers that end a purchase.
Whether the forms recover
Labels, error messages, required fields, time limits. The checkout and the booking form are where money is lost, and where automated checks are weakest.
Your real contrast
Contrast depends on the rendered page, on hover states, on text over images, on your brand palette in dark mode. It is measured, not declared.
What is behind the login
The part of the service that matters most is usually the part a public scanner never sees. We test it with credentials you provide.
How a tested statement is produced, step by step
- Free scan. You enter your address and see the automated findings immediately. No card, no account. This is the part a generator also does, and it is the smallest part of the work.
- Order and scope. A form of about ten minutes: the domain, the company that will be named, the signatory, the languages, and any area behind a login you want covered.
- Manual testing. A representative set of pages is tested by hand: home, a category and a product or service page, the forms, the checkout or booking flow, login, contact and legal pages. Keyboard, screen reader, zoom to 400%, reflow, contrast, focus order, error recovery.
- Findings. Every barrier is written in plain language: where it is, what it breaks, who it affects, what to change, and how urgent it is.
- The statement. The text is written from the findings, in the structure the applicable law asks for, including the barriers that are still open and the alternatives available meanwhile.
- Signature and code. The document is signed by the company established in your jurisdiction and gets a public verification code that anyone can check.
- Monthly re-test. Sites change. Once a month we test again and re-issue when something material moves.
Five business days from a complete form. The trial is seven days with no card, so the record is live while you decide.
Generated text against a tested record
| Generator | Tested and signed record | |
|---|---|---|
| Time to produce | Thirty seconds | Five business days |
| Based on | What you typed | What was tested on your site |
| Manual testing | None | Keyboard and screen reader on real flows |
| Barriers listed | Usually none | All of them, with priority |
| Signed by | Nobody | A registered company in your jurisdiction |
| Verifiable | No | Public code, checkable by anyone |
| Kept current | Until your site changes | Monthly re-test, re-issued |
| Useful in an inspection | As an admission | As evidence |
Where an overlay fits in all this
An overlay is a script that promises to fix accessibility from the outside. It cannot restructure your headings, name your buttons or rewrite your form errors, and in practice it often interferes with the assistive technology the user already has configured. A statement produced by an overlay vendor has the same defect as a generated one, with an extra claim attached to it.
If you already run one, keep it or remove it, that is your decision. It does not change what the statement has to say, and it does not remove a single barrier from the underlying pages.
Who needs this, and where
In the European Union the Accessibility Act has applied since 28 June 2025 to a defined list of products and services sold to consumers, e-commerce among them. In Germany it arrives through the BFSG, in Italy through the Legge Stanca as amended, in Spain through Real Decreto 193/2023, and so on: one directive, twenty-seven national laws, one statement that must satisfy the one that applies to you. Our EU plan covers a single domain, EU Plus covers three domains and six languages.
In Ontario the obligation runs on a different clock: organisations with twenty or more employees file a compliance report, and the next deadline is 31 December 2026. What we prepare and sign there is the underlying web conformance record; the filing itself stays with you, because it is a self-declaration. The detail is on the AODA page, and the federal side on the Accessible Canada Act page.
In the United Kingdom the statement is contractual more often than statutory: it appears in tenders, in supplier questionnaires and in procurement frameworks, and a WCAG 2.2 AA report signed by a UK company is what buyers ask to see. That route is described on the UK page, and the European one on the EAA page.
What you receive
The tested statement
Written from the findings, in the structure your jurisdiction requires, in the language of your market.
The findings report
Every barrier in plain language, ordered by priority, with the change to make.
A public code
Printed on the document, checkable by anyone, listed in our public register unless you ask otherwise.
A hosted feedback channel
The contact point the law requires, hosted by us and forwarded to you.
Monthly re-testing
Because a statement that describes last year's website is worth as little as a generated one.
Five years of records
Every test, every version of the document, kept and retrievable if an authority or a client asks.
Start with the scan, not with the text
Run the free scan on your own address. It costs nothing, asks for no card, and in two minutes you will know whether your site has the kind of problems a paragraph cannot solve. If it comes back clean, keep your generated statement and spend the money elsewhere. If it does not, you now have the list, and the choice of what to do with it.
Either way you will know something you did not know before opening this page, which is more than any generator can offer.
Questions people ask before they choose
Is an accessibility statement generator enough to comply?
A generator produces text. The law asks for text that is true. Under Annex V of the European Accessibility Act, under Ontario's O. Reg. 191/11 and under the UK Equality Act, the statement has to describe the real state of your site, the barriers that remain and the contact point for feedback. A generator cannot know any of that, because it has never opened your website.
What does a generator actually give me?
A form with a few fields and a paragraph of boilerplate: your company name, a claim of conformance, a contact email. It is a starting layout, not evidence.
What is missing from generated text?
The test itself. A statement is the summary of an assessment: which pages were checked, with which assistive technology, on which date, what failed, what is planned. Without the assessment the summary describes nothing.
Can a false statement hurt me?
Yes. A statement claiming full conformance on a site that fails basic keyboard access is a documented misstatement, made by you, in public. It is easier to act against than silence.
Do authorities read these statements?
They do. Market surveillance authorities in the EU use the statement as the entry point of an inspection, and complaints often quote it word for word.
How is your document different?
We run an automated scan and a manual test with keyboard and screen reader, write the findings, then issue a statement that matches them, signed by a registered company with a public verification code.
Who signs your statement?
Europe Services SE in Prague for the European Union, REP27 LTD in England for the United Kingdom, Goldman Services INC in Ontario for Canada. Each is a real company in a public register.
What is the verification code?
A code printed on the document that anyone can check on our public register to confirm the record exists, who signed it and when.
How long does it take?
Five business days from a complete order form. The form takes about ten minutes.
How much does it cost?
690 € a year for the European Union, 1,290 € a year for three domains and six languages, 890 CAD a year for Canada, 1,990 € a year for the EU, the UK and Canada together. Renewal is 20% lower.
Is there a free trial?
Seven days free, with no card. The record is valid and verifiable from day one.
What if my site fails the test?
That is the normal result of a first test. The statement says what was found and you receive the fix list ordered by priority. When the fixes are done we re-test and re-issue.
Do you fix the website?
No. We test, document and sign. The code changes are made by you or your developer, working from our list.
Do I still need a statement if my site is accessible?
Yes. The statement is a separate obligation from conformance: the site has to work, and the statement has to say so and offer a feedback channel.
Which standard do you test against?
WCAG 2.2 level AA. Ontario requires WCAG 2.0 AA, so testing at 2.2 AA is stricter than the legal minimum there.
Can I move from a generated statement to yours?
Yes, and it is the common case. We test the site, correct what the generated text claimed wrongly, and issue the signed version with the same public URL.
What happens after the first year?
Renewal is 20% lower, and the monthly re-test continues, so the statement stays aligned with the site as it changes.
Can I see a real example first?
Yes. There is a specimen record on the site with a working verification code you can check yourself.