Accessibility Statement for the European Accessibility Act: Providers & Prices 2026
- EAA requires a factual, tested accessibility statement (Annex V, Directive (EU) 2019/882).
- Micro-enterprises may be exempt if compliance is a disproportionate burden.
- Statements must include test results, known barriers, feedback process, and review date.
- Automated generators offer templates but not legal compliance or evidence.
- Prices (October 2026): free to €690/year, with varying scope and support.
- Non-compliance risks include fines, market restrictions, or legal action.
Providers compared
| Provider | Established in | Published price | What the price includes | Best for |
|---|---|---|---|---|
| AccessibilityStatement.org | European Union | €690/year (price_verified_on_source_page) | Manual and automated testing, signed statement, public verification code, monthly retest, 7-day free trial | Organisations needing a tested, signed, and regularly updated statement |
| AccessHarborsource | United States | On request | Automated WCAG 2.1 AA scan, violation report, 20-minute consultation call | Quick automated scan and basic advice |
| RampChecksource | Germany | €79 (excluding VAT) (price_verified_on_source_page) | Full EAA audit, prioritized plain-language fix plan | One-off EAA audit with actionable fix plan |
| Cluesiasource | United Kingdom | Free | Automated accessibility statement checker for EU consumer-facing websites | Self-service automated statement check |
Prices as published on each provider's website on 17 October 2026, excluding VAT unless stated. Each row links to its source.
What the European Accessibility Act Requires (with Article References)
The European Accessibility Act (Directive (EU) 2019/882), effective from 28 June 2025, sets out harmonized accessibility requirements for a range of products and services across the EU. The Act covers digital products and services such as computers, operating systems, ATMs, ticketing and check-in machines, smartphones, e-commerce, banking, and passenger transport services (source).
- Annex V of the Directive specifies the required content for a public accessibility statement. This includes:
- A plain-language description of the service and its accessibility features
- The conformance level claimed, typically against WCAG 2.1 AA (referenced via EN 301 549)
- A list of known barriers and, where possible, alternatives offered
- A feedback mechanism that users can use to report problems, which must be functional
- The date of the last review and a commitment to keep the statement current
- Identification of the economic operator responsible for the statement
- Member States had to incorporate the Act into national law by June 2022. Penalties for non-compliance, such as fines or market restrictions, are determined at the national level (source).
- Micro-enterprises (fewer than 10 employees and under €2 million turnover) may be exempt if compliance would cause a disproportionate burden, but this must be justified (source).
It is important to note that the Act does not accept generic or template-based statements. The statement must reflect the actual, current state of the website or service, based on real testing. Automated generators that simply produce a block of text do not meet these requirements, as they lack evidence of testing and do not disclose real barriers or alternatives (source).
How to Choose a Provider: What the Price Really Includes
Choosing a provider for your accessibility statement under the EAA is not just about price—it's about the depth and defensibility of the service. Providers range from free automated generators to comprehensive, manually tested and signed solutions. Here’s how to compare:
- Automated generators (e.g., Cluesia) are free and quick, but only check for the presence of a statement or generate a template. They do not test your site, do not identify real barriers, and do not provide a signed or verifiable record. These are suitable only for initial self-checks or very low-risk scenarios.
- Automated scan plus advice (e.g., AccessHarbor) offers a basic automated WCAG 2.1 AA scan, a violation report, and a short consultation call. This can help identify some issues, but does not replace manual testing or fulfill the full requirements of Annex V.
- One-off audits (e.g., RampCheck) provide a full EAA audit and a prioritized, plain-language fix plan. This is a more thorough approach, but may not include a signed statement, ongoing updates, or public verification.
- Comprehensive services (e.g., AccessibilityStatement.org) include both automated and manual testing, a signed statement by an EU-based entity, a public verification code, and monthly retests. This matches the legal requirements for evidence, ongoing accuracy, and accountability.
Always ask:
- Is the statement based on real, manual testing?
- Does the provider disclose known barriers and alternatives?
- Is there a feedback mechanism and is it tested?
- Is the statement signed and verifiable by a third party?
- How often is the statement updated, and is this included in the price?
| Provider | Included | Not included | Extra fees |
|---|---|---|---|
| AccessibilityStatement.org | Manual & automated testing, signed statement, monthly retest, public verification code | Filing the report for you | None stated |
| AccessHarbor | Automated scan, report, 20-min call | Manual testing, signed statement | On request |
| RampCheck | Audit, fix plan | Ongoing updates, signed statement | On request |
| Cluesia | Automated statement checker | Testing, signed statement, support | None |
For legal compliance, prioritize providers offering real testing, signed statements, and regular updates.
Hidden Costs and What Providers Usually Do Not Say
Many organizations underestimate the true costs and limitations of accessibility statement services. Here’s what to watch for:
- Template generators rarely mention that their output is not legally defensible. A generic statement without real testing does not meet EAA requirements and may increase risk if challenged by regulators or users.
- Notice periods and update cycles are often omitted. Some providers only offer a one-time audit or statement, leaving you exposed if your site changes or if a barrier is reported. AccessibilityStatement.org includes monthly retests; others may charge extra or not offer updates at all.
- Per-request fees for additional support, urgent re-testing, or legal advice are common but not always disclosed upfront. Always ask for a full price list and clarify what is included.
- Liability limits: Most providers, including those offering automated or template-based solutions, do not accept legal responsibility for your compliance. AccessibilityStatement.org is clear that only your organization can sign and file the official report; no provider can offer government certification.
Always request a sample statement, ask for a detailed breakdown of what is included, and clarify what happens if your site changes or if a user reports a problem. A statement that is not regularly updated quickly becomes non-compliant.
How the Appointment Works: Step by Step
The process for obtaining an accessibility statement varies by provider. Here’s a detailed step-by-step guide, using AccessibilityStatement.org as the model for full compliance:
- Initial scan: Start with a free automated scan of your site. No account or payment is required to see the automated findings.
- Order service: If you proceed, you provide your website address and, if needed, credentials for testing behind logins or paywalls.
- Testing: AccessibilityStatement.org conducts both automated and manual testing, including keyboard navigation, screen reader use, and testing of forms, checkout, and other critical flows. This covers areas automated tools cannot check, such as contrast in real use, focus traps, and screen reader announcements.
- Draft statement: Within five business days, you receive a draft statement that includes:
- Plain-language description of the service
- Conformance level and test results
- List of known barriers and alternatives
- Feedback mechanism and contact details
- Review date and responsible entity
- Verification: The statement is signed by an EU-based company and includes a public verification code.
- Publication: You publish the statement on your website, linking it from every page as required by the EAA.
- Ongoing updates: Monthly retests are included, ensuring the statement remains accurate and defensible as your site evolves.
Other providers may offer only automated scans or one-off audits. Always ask about the process, turnaround times, and what happens if you need updates or support after the initial statement is delivered.
Risks, Fines, and Legal Consequences
Non-compliance with the European Accessibility Act carries real risks. Penalties are set at the national level and may include:
- Fines: Financial penalties for failing to provide a compliant accessibility statement or for misrepresenting your site’s accessibility.
- Market restrictions: Authorities may restrict or ban the sale of non-compliant products or services in the EU market.
- Legal action: Users or advocacy groups may bring complaints or lawsuits, especially if barriers prevent access to essential services.
Publishing a template statement without real testing does not meet Annex V requirements. If a regulator or user challenges your statement, you must provide evidence of testing and honest disclosure of barriers. Regular updates and a working feedback mechanism are critical for defensibility.
Micro-enterprises may be exempt if compliance is a disproportionate burden, but this must be documented and justified. Relying on automated tools or generic templates without real testing increases your risk of enforcement action.
Decision Matrix: Do You Need an Accessibility Statement?
| If you are … | You need … | You do not need it if … |
|---|---|---|
| EU-based company, B2C, >10 employees | Full EAA statement with real testing | Micro-enterprise and compliance is a disproportionate burden |
| Non-EU company selling to EU consumers | EAA statement if offering covered products/services | No EU sales or not covered by the Act |
| B2B SaaS platform | Statement if public-facing or required by procurement | Internal-only tools, no public access |
| Marketplace seller (Amazon, Etsy, eBay) | Depends on platform’s compliance; direct sellers may need a statement | Platform handles all accessibility obligations |
Review your business model, size, and sales channels to determine your obligations. When in doubt, consult the Act or a qualified provider for clarification.
Checklist: Steps to Compliance Today
- Determine if your business and services are covered by the EAA (see Directive (EU) 2019/882, Annex V).
- Check if you qualify for the micro-enterprise exemption (fewer than 10 employees and under €2 million turnover, and compliance would be a disproportionate burden).
- Review your current accessibility status: conduct an automated scan and/or manual review.
- Choose a provider based on your need for real testing, legal defensibility, and ongoing support.
- Request a sample statement and clarify what is included (testing, updates, support, verification).
- Provide access and information needed for testing, including credentials for non-public areas.
- Receive and review the draft statement, ensuring it accurately reflects your site and barriers.
- Publish the statement on your website, linking it from every page as required.
- Set up a feedback mechanism and document your process for responding to reports.
- Schedule regular reviews and updates (at least annually or after major changes).
- Document all actions taken for compliance, including testing reports and correspondence.
Scenarios: Which Obligation Applies and How to Comply
- US SaaS company selling to EU consumers: If your SaaS platform is used by EU consumers or businesses, you must publish an EAA-compliant accessibility statement if your service falls under the Act. The simplest compliant route is to use a provider that can sign and verify statements within the EU (e.g., AccessibilityStatement.org), ensuring your statement is based on real testing and is kept up to date.
- Chinese Amazon seller: If you sell only through Amazon, the platform may handle accessibility obligations. If you also sell directly to EU consumers from your own site, you must provide a compliant statement for that site if the Act applies. Automated generators are not sufficient; use a provider offering real testing and a signed statement.
- UK online shop: Post-Brexit, UK businesses selling to EU consumers must comply with the EAA for their EU-facing sites. Use a provider with EU expertise and ensure the statement matches Annex V requirements, including manual testing and honest disclosure of barriers. Ongoing updates are essential as your site evolves.
In all scenarios, the key is to match your compliance approach to your actual risk and obligations. Automated tools are useful for initial checks, but only real testing and honest, regularly updated statements meet the legal standard.
When you do not need this
- Micro-enterprises (fewer than 10 employees and under €2 million turnover) if compliance is a disproportionate burden
- Internal-only tools with no public access
- Sites/platforms where the marketplace (e.g., Amazon) assumes all accessibility obligations
- Businesses not offering covered products or services in the EU
Frequently asked questions
What must an EAA accessibility statement include?
It must describe how the service meets accessibility requirements, list known barriers and alternatives, provide a feedback mechanism, state the date of last review, and identify who stands behind the statement. Templates alone do not meet legal requirements—real testing and honest disclosure are essential.
Who is exempt from the European Accessibility Act?
Micro-enterprises (fewer than 10 employees and under €2 million turnover) may be exempt if compliance would cause a disproportionate burden. However, this must be justified and documented. All other businesses offering covered products or services to EU consumers must comply.
How often must the accessibility statement be updated?
The statement must be kept current—reviewed and reissued whenever the site changes or at least annually. Annex V requires the date of last review to be stated, and ongoing updates are expected to reflect the actual state of accessibility.
What happens if my site fails to meet the requirements?
Non-compliance can result in fines, market restrictions, or legal action. The specific penalty depends on national law. Publishing a statement without real testing or failing to update known barriers increases legal risk.
Can I use a free generator for my EAA statement?
Free generators provide templates but do not test your site or create the evidence required by law. Only a statement based on real, documented testing meets Annex V requirements and can be defended in case of inspection.
Does AccessibilityStatement.org file the report for me?
No. The legal requirement is self-certification; only a senior officer of your organization can sign and file the report. AccessibilityStatement.org prepares the documents and evidence, but you must submit the report yourself.
What is the difference between a VPAT and an accessibility statement?
A VPAT is a procurement document for buyers, detailing technical compliance. An accessibility statement is a public document required by law, describing actual accessibility, barriers, and feedback mechanisms. Both require real testing, but serve different audiences.
How long does it take to get a signed statement?
AccessibilityStatement.org delivers a signed statement within five business days after testing begins. Other providers may vary—automated generators are instant, but do not provide legal compliance.
What if my site changes after the statement is published?
You must update the statement to reflect the current state of accessibility. Providers offering ongoing support (e.g., monthly retest) help ensure continued compliance. Static templates quickly become outdated and non-compliant.
Is there an official EAA certification?
No. The EAA requires a public statement and evidence of compliance, but no government or private company can issue an official certification. Only a dated, honest record of testing is recognized.
Do I need a statement if I only sell through marketplaces?
If the marketplace (e.g., Amazon) assumes all accessibility obligations, you may not need a separate statement. However, if you operate your own site or direct sales channel to EU consumers, you are responsible for compliance.
What should I do if a user reports a barrier?
You must have a working feedback mechanism and a documented process for responding. AccessibilityStatement.org includes guidance on how to reply and what to document. Prompt, honest responses and updates to your statement are essential for compliance and risk management.
Sources
- Directive (EU) 2019/882 – European Accessibility Act — eur-lex.europa.eu
- European Commission – EAA Policy Overview — commission.europa.eu
- Clym – European Accessibility Act — clym.io
- EAA Pass – Micro-enterprise Exemption — eaapass.eu
- AccessibilityStatement.org – Accessibility Statement Generator — accessibilitystatement.org
- AccessibilityStatement.org – Accessibility Statement Example — accessibilitystatement.org
- AccessibilityStatement.org – VPAT vs Accessibility Statement — accessibilitystatement.org
- AccessHarbor — accessharbor.org
- RampCheck — rampcheck.eu
- Cluesia — cluesia.com