The EAA does NOT directly obligate Turkish companies. Your European client is the entity legally obligated under the Directive. You comply because the contract requires it. This report is the deliverable your client's compliance team expects alongside the code.
Why Turkish dev shops are getting accessibility clauses in 2025
Turkey is the 4th largest IT outsourcing destination for European companies. Istanbul, Ankara, Izmir and Antalya host hundreds of software houses building e-commerce sites (Art. 2.2.f), banking interfaces (Art. 2.2.d), telecoms dashboards (Art. 2.2.a) and SaaS platforms for European clients. Since the EAA became enforceable, every one of those clients needs their digital services to be accessible — and the first thing they do is add a clause to your contract.
The clause is not optional. Without the accessibility report, your client cannot close their compliance file. Without the file, they risk fines up to €100,000 in Germany, €1M in Spain, €250K in France. Your report is not a nice-to-have. It is a contract deliverable.
What your European client's compliance team expects
E-commerce builds
Art. 2.2(f). Shopify, WooCommerce, custom platforms selling to EU consumers.
Banking UI
Art. 2.2(d). Consumer banking interfaces, account management, payment flows.
SaaS dashboards
Consumer-facing SaaS platforms. Art. 2.2(f) if selling to individuals.
Mobile apps
Any app selling to or serving EU consumers. Same WCAG 2.1 AA criteria apply.
What you receive
Cover page
Compliance score, verification reference, date.
Service identification and scope
Product, deployment context, evaluation method, legal framework.
17 WCAG 2.1 AA criteria
Criterion-by-criterion evaluation across four principles.
W3C remediation guidance
Actionable fixes per failed criterion.
Accessibility statement
Following Annex V of Directive 2019/882.
Legal basis and scope disclaimer
Directive 2019/882, EN 301 549 V3.2.1, national transposition law.
Generated in your browser.
What it costs
Three mistakes Turkish dev shops make
"That's the client's responsibility, not ours"
Yes, legally. But if you don't deliver the documentation, you don't get the final payment. The report is a contract deliverable.
Sending Lighthouse or Axe output to the client
Automated tools catch ~30% of WCAG issues. European compliance teams require a structured criterion-by-criterion assessment. EAA-Report produces exactly that.
"Nobody has enforced this yet"
The clause is already in the contract. If you delay, you delay deployment and payment.
Enforcement your client faces
Fines for your client, contract consequences for you.
BFSG. Per-infringement fines.
Law 11/2023.
Ordonnance 2023-859.
Implementatiewet. Up to 10% of turnover.
What EAA-Report guarantees and what it doesn't
EAA-Report generates a document structured under Art. 13.2 of Directive (EU) 2019/882 based on the information you enter. The truthfulness, accuracy and completeness of that information is your responsibility as service provider.
We guarantee that the document structure follows Art. 13.2 of Directive (EU) 2019/882 and that the legal references cited are correct. We do not guarantee that a specific document will be accepted by a market surveillance authority in a specific case.
EAA-Report is not legal advice. For specific situations, consult a lawyer or specialised regulatory consultancy.
Frequently asked questions — Turkish software outsourcing
Does the EAA obligate me as a Turkish company?
What if my client doesn't ask?
One report for multiple projects?
Do I need WCAG expertise?
15 minutes?
Legal advice?
⚠️ Important notice: EAA-Report is a self-assessment documentation tool, not legal advice and not a third-party audit. The document is generated from your input data. You are responsible for the accuracy of the data you provide. EAA-Report does not replace a qualified professional assessment.
Official legal sources
- Directive (EU) 2019/882 — European Accessibility Act — full text