Free Accessibility Statement Generator

An Accessibility Statement is a page that tells visitors how accessible a website or an app is for people with disabilities.

It names the standard the website follows, such as WCAG 2.2 at level AA, and says whether the website meets it fully, partially or not yet. It lists the content that doesn't meet the standard yet, with the workaround and the planned fix.

The statement gives visitors a contact for reporting a barrier and asking for content in another format. Public sector bodies add the procedure for complaints.

Yes, the Accessibility Statement Generator from TermsFeed is free to use.

A one-time purchase or a paid plan removes the TermsFeed credits link and adds more features, such as downloads and the Text Editor.

Yes, you need an Accessibility Statement when the European Accessibility Act or the public sector accessibility rules of the EU or the UK apply to your website or app.

The European Accessibility Act (EAA, Directive (EU) 2019/882) has applied since 28 June 2025 to services such as online stores, consumer banking and e-books. Their providers publish how each service meets the accessibility requirements of the Act (Article 13(2) and Annex V).

The Web Accessibility Directive (Directive (EU) 2016/2102) asks every public sector body in the EU for an Accessibility Statement on each website and mobile app (Article 7). Commission Implementing Decision (EU) 2018/1523 sets the model statement.

In the UK, the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 ask public sector bodies for an Accessibility Statement.

In the US and Canada, an Accessibility Statement is good practice for a business that follows the Americans with Disabilities Act (ADA), Section 508 or the Accessibility for Ontarians with Disabilities Act (AODA). It states your WCAG target and gives visitors a way to report a barrier.

Answer the questions of the Accessibility Statement Generator, then link the result from the footer of every page.

The European Accessibility Act applies to your business when you offer one of its services to consumers in the EU and your business is larger than a microenterprise.

The services it covers include e-commerce (selling to consumers through a website or an app), consumer banking, e-books and their reading software, and electronic communications. The websites, apps and e-tickets of air, bus, rail and waterborne passenger transport are covered as well.

A microenterprise has fewer than 10 employees and an annual turnover or balance sheet total of no more than €2 million. A microenterprise that provides services is exempt (Article 4(5)).

A business based outside the EU that sells to consumers in the EU is covered for those sales. Each EU country sets the details in its own law, such as the Barrierefreiheitsstärkungsgesetz (BFSG) in Germany and Law 11/2023 in Spain.

An Accessibility Statement includes the standard you follow, how well your website meets it, the content that doesn't meet it yet and how visitors contact you.

The conformance status says whether the website is fully, partially or not conformant with the standard. The list of known limitations names each piece of content, the problem and the workaround or the date of the fix.

The statement says how you assessed the website (a self-assessment, an external audit, automated testing or testing with users) and when. It lists the accessibility features, the browsers and assistive technologies you support, and the technologies the website relies on.

The feedback part gives an email address or a phone number, the time you take to answer and the alternative formats you offer. Public sector bodies add the content they leave out because of a disproportionate burden, the content outside the scope of the law, and the enforcement procedure.

Aim for WCAG level AA, the level the European and UK accessibility rules use.

The Web Accessibility Directive points to the European standard EN 301 549, which follows WCAG 2.1 level AA for web content. UK government guidance for public sector bodies uses WCAG 2.2 level AA.

The W3C published WCAG 2.2 in October 2023. It adds success criteria to WCAG 2.1, and content that meets WCAG 2.2 meets WCAG 2.1 as well.

The Accessibility Statement Generator uses WCAG 2.2 level AA by default. Pick WCAG 2.1 level AA or EN 301 549 in its place when your rules name one of them.

A website that isn't fully accessible yet publishes an Accessibility Statement with the status "partially conformant" or "not conformant" and a list of its known limitations.

An honest statement tells visitors which content gives them trouble, which alternative to use and when the fix comes. A statement that claims full conformance without testing misleads the visitors who rely on it.

The Accessibility Statement Generator asks for each limitation, the problem and the workaround or the fix date, and writes them as a list. Public sector bodies add the content they exempt because of a disproportionate burden, with the reason.

Create an Accessibility Statement with the Accessibility Statement Generator in 6 steps.

1. Enter the website or app the statement covers.

2. Enter your business details, and say whether you publish as a business or a public sector body.

3. Choose the standard, the conformance status and how you assessed the website.

4. List the known limitations, with the workaround or the fix date for each one.

5. Describe the accessibility features, the supported browsers and assistive technologies, and the technologies you rely on.

6. Add the feedback contact, the response time and the alternative formats, then publish the statement with its Live Link or download it.

The Accessibility Statement Generator covers Germany, Austria, France, Italy, Spain, the Netherlands, Ireland and the UK with the wording of each country, and writes a general version for every other country.

In Germany, it cites the Barrierefreiheitsstärkungsgesetz (BFSG) and the Barrierefreie-Informationstechnik-Verordnung (BITV 2.0). In Austria, it cites the Barrierefreiheitsgesetz (BaFG) and the Web-Zugänglichkeits-Gesetz (WZG).

In France, it writes the déclaration d'accessibilité of the Référentiel général d'amélioration de l'accessibilité (RGAA). In Italy, it follows the Legge Stanca and the guidelines of the Agenzia per l'Italia Digitale (AgID). In Spain, it cites Royal Decree 1112/2018 and Law 11/2023.

The generator writes the statement in English, German, French, Spanish or Italian.

Place your Accessibility Statement on its own page and link it from the footer of every page.

Visitors who meet a barrier look for the statement there, under a link named "Accessibility" or "Accessibility Statement". In an app, add the link to the settings or the about screen and to the app store listing.

The European Accessibility Act asks service providers to include this information in their general terms and conditions or an equivalent document (Annex V), so link the statement from your Terms and Conditions as well.

Update your Accessibility Statement after every change that affects accessibility, and review it at least once a year.

A redesign, a new feature, a fixed limitation or a new audit each changes what the statement says. The statement shows the date of the assessment, so visitors see how current it is.

The Web Accessibility Directive asks public sector bodies to update their statement regularly (Article 7(1)). The European Accessibility Act asks service providers to keep the information for as long as the service runs (Article 13(2)).

No, an Accessibility Statement doesn't make your website accessible.

The statement describes how accessible the website is today. Accessibility comes from the design, the content and the code: text alternatives for images, enough color contrast, keyboard navigation, captions for videos and labels on forms.

Automated testing finds some problems. A manual review, an external audit and testing with people who use assistive technologies find others.

TermsFeed writes the statement from your answers and doesn't test your website, so the statement is as accurate as the assessment behind it.