Frequently asked questions

An accessibility statement is a public page that explains how accessible your website or app is, which standard you follow (for example WCAG 2.2 Level AA), what is not yet fully accessible, how visitors can report a barrier, and how you assessed accessibility. It is the standard way to be transparent with disabled users and with regulators.

Yes. The generator is free, with no account, no email capture, no usage limits and no hidden paid tier. It runs entirely in your browser, so there is nothing for us to meter.

The generated statement is available in English, German, French and Spanish. You can generate more than one language at the same time, which is useful if you serve customers in several countries.

The European Accessibility Act (Directive (EU) 2019/882) applies to consumer-facing products and services in the EU, including e-commerce, consumer banking, electronic communications, passenger transport services, e-books and access to audiovisual media. Microenterprises providing services are exempt. The EAA guide explains the scope, exemptions and key dates.

It depends on your country and sector. Public sector websites in the EU must publish a statement under the Web Accessibility Directive, and several national implementations of the European Accessibility Act expect providers to give consumers accessibility information and a way to report barriers. A statement is the standard way to meet that expectation. Even where it is not strictly required, it is good practice and often requested by customers and auditors.

WCAG (Web Content Accessibility Guidelines) has three conformance levels. Level A covers basic requirements, Level AA covers the requirements most commonly referenced by law and policy, and Level AAA covers the most demanding requirements. Level AA is the standard target for the European Accessibility Act, EN 301 549 and most accessibility regulations, so the generator defaults to WCAG 2.2 Level AA.

EN 301 549 is the European harmonised standard for accessibility requirements for ICT products and services, and it is how the European Accessibility Act gets its technical substance. Version 3.2.1, based on WCAG 2.1 Level AA, is the version currently referenced for conformity. A newer version, EN 301 549 v4.1.1, was published in September 2026 and adopts WCAG 2.2, but it is not yet the legal reference standard until the European Commission cites it in the Official Journal.

Yes, and you should. The output is plain HTML or Markdown that you can paste into your site and adapt. Add details about your own limitations, your accessibility roadmap or your organisation's specific commitments.

No. Everything runs locally in your browser. Nothing is uploaded, there is no account, and the site sets no tracking cookies. You can even use the generator offline once the page has loaded.

Publish the statement anyway, and be honest. Choose "partially conformant", list the known limitations and describe what you are doing about them. An accurate statement with a working feedback channel is far better than silence or an overstated claim.

Review it at least once a year, and update it whenever your site changes significantly or when you fix (or discover) accessibility issues. The generator lets you set the statement date, so regenerating an updated version takes a minute.

No. AccessProof provides a template and general information, not legal advice, and it does not certify or audit anything. Only an assessment of your actual site can establish conformance. If you need assurance, get an independent accessibility audit.