Skip to main content
Raasta

Free accessibility statement generator

An accessibility statement tells visitors how accessible your site is, what you know still needs fixing and how to reach you. Under the European Accessibility Act, services must publish this kind of information. Fill in the form; nothing you type leaves your browser. Base the statement on real testing: the free scan covers the automated checks, and the manual checks guide covers the rest.

Conformance status

Most sites are partially conformant. Only claim full conformance after a complete manual audit.

For the EAA, EN 301 549 points to WCAG 2.1 AA; WCAG 2.2 AA covers it.
Only content you have formally assessed as too costly to fix now. It is not a general opt-out.
The national authority people can complain to, if you know it.

Your statement

Accessibility statement for this website

Our organisation wants this website to be usable by as many people as possible, including people who use screen readers, keyboards, voice control, magnification or other assistive technology.

Conformance status

this website partially conforms to WCAG 2.2 level AA. Some parts of the content do not fully meet the standard.

Feedback and contact

If you find a barrier on this website, or need information in a different format, contact us. We aim to reply within 5 working days.

Technical specifications

The accessibility of this website relies on the following technologies to work with your browser and any assistive technology: HTML, CSS, JavaScript, WAI-ARIA.

How we assessed this site

Our organisation assessed this website itself, using automated checks and manual testing.

This statement was prepared on 6 November 2026.

A starting point, not legal advice. Review it, keep it accurate and link it from every page.

What the statement includes

The generator follows the structure suggested by W3C WAI and the EU model accessibility statement. Optional sections appear only when you fill them in.

Commitment
Who you are and that you want the site to be usable by everyone, including people using assistive technology.
Conformance status
Whether the site fully, partially or does not conform to a standard, such as WCAG 2.2 level AA.
Non-accessible content
What still fails and why: known problems you are fixing, anything you assessed as a disproportionate burden, and content outside your control.
Feedback and contact
How people report a barrier or ask for another format, and how quickly you reply.
Enforcement procedure
Where people can go if your answer does not solve their problem, usually a national authority.
Technical specifications and compatibility
The technologies the site relies on (HTML, CSS, JavaScript, WAI-ARIA) and what you tested it with.
Assessment and date
Whether you assessed the site yourself or used an external evaluator, when, and when the statement was prepared.

Questions

What is an accessibility statement?

A page on your website that says how accessible the site is, which standard you measure it against, what you know still fails, and how people can contact you about barriers. W3C WAI recommends one for every site, and EU public-sector sites must publish one using the EU model.

Do I need an accessibility statement for the European Accessibility Act?

Service providers covered by the European Accessibility Act must publish information on how their service meets the accessibility requirements (Annex V of Directive (EU) 2019/882), in their terms and conditions or another publicly available document. An accessibility statement linked from every page is the usual way to do this. Check the national law of each country you sell into.

Can I say my site is fully conformant?

Only if a complete audit, including manual testing, found it meets every requirement of the standard. Automated scans find a large share of problems but not all, so most sites should say partially conformant and list the known limitations.

Is this generator free, and is my data stored?

Yes, it is free with no account. The statement is built in your browser; nothing you type is sent to Raasta.

Where should I put the statement?

On its own page, for example /accessibility, linked from the footer of every page. Review it after each redesign or audit and update the dates.

Base your statement on a real check

Scan a page free to find the automated failures, each with the WCAG 2.2 criterion and the code to fix it. Then read the WCAG 2.2 guide for the criteria a person has to test, and the European Accessibility Act guide if you sell to consumers in the EU.

Scan a page free