European Accessibility Act ready — before the deadline.
WCAG 2.2 AA conformity, written accessibility statement, technical documentation, and remediation plan for the gaps your site has today. Fixed €3,490. 14 days. Self-declaration ready before 28 June 2025.
If you're reading this, this is what you're facing
- Your e-commerce / SaaS site falls under EAA scope (B2C, EU consumers, > 10 employees, > €2M turnover). Most sites do.
- You ran an accessibility audit and got back a 47-page PDF with 280 issues. Now what? Which to fix first, what's actually required, what counts as "disproportionate burden"?
- June 28 is hard. National enforcement bodies (in DE, FR, IT, ES) can fine non-conforming products up to €100K per violation under transposed legislation.
How we fix it
We translate the EAA from regulation into a buildable plan. WCAG 2.2 AA gaps prioritised by impact, EN 301 549 mapping for the technical documentation, your accessibility statement drafted to the required template, and the highest-impact remediations implemented in your codebase. The output is a complete file your legal team deposits, plus a working site that actually conforms.
What's in the package
How it works
- Day 1. Audit + scoping. Full WCAG 2.2 AA scan, manual review of critical user journeys, written gap report.
- Days 2–8. Critical remediations. Top-tier violations fixed in code on a feature branch your team reviews and merges.
- Days 9–12. Documentation pack. EN 301 549 conformity table, accessibility statement, disproportionate-burden rationale where applicable.
- Days 13–14. Handover + training. Final files, statement live on /accessibility, 60-min team session on maintaining conformance.
Who this is for
- B2C e-commerce sites > 10 employees
- SaaS products with EU consumer-facing surfaces
- Banking, insurance, e-money apps (financial services category)
- Travel, transport, ticketing platforms
- Anyone targeting EU consumers with > €2M turnover
- Companies caught flat-footed by 28 June 2025
Frequently asked
Does the EAA apply to my B2B SaaS?
Mostly no. The EAA targets consumer-facing products and services. If your SaaS is strictly B2B (no consumer-direct sales), you're generally out of scope — but mixed-use products (e.g. a B2B platform with a consumer self-serve tier) bring the consumer surface in scope. We assess this in Day 1.
Is WCAG 2.2 AA strictly required, or is 2.1 AA enough?
The EAA references EN 301 549 v3, which currently aligns with WCAG 2.1 AA. WCAG 2.2 AA is recommended as the more current standard and most national transpositions reference v3.x of EN 301 549. We document conformance to 2.2 AA — covers both.
What if our site has 280 violations and we can't fix them all in 14 days?
You don't have to. The EAA requires conformity, not perfection — critical violations in user journeys must be fixed; lower-severity issues can be roadmapped with documented disproportionate-burden rationale. We prioritise; you ship.
Who signs the conformity declaration?
Your legal entity signs the self-declaration. We supply the technical documentation that supports the declaration — the WCAG conformance evidence, the EN 301 549 table, the accessibility statement. You sign because you're the obligated party under the directive.
Recommended path
European Accessibility Act readiness · €3,990 · 14 days
Talk to the Architect →