EAA conformance, delivered — not just diagnosed.
We audit your product, author the fixes as deploy-ready code, produce the conformance documentation, and keep you conformant. Your team's only job: review and merge.
30 minutes · no obligation · EnglishThree facts, stated plainly.
-
Enforcement has begun.
The European Accessibility Act (opens in new tab) became enforceable on 28 June 2025, and enforcement is ramping: the first lawsuits were filed in France in late 2025. Fines vary by country — up to €100,000 in Germany, higher elsewhere.
-
It applies wherever you're based.
Any company selling digital products or services into the EU falls under the EAA, regardless of where it's headquartered. Only microenterprises — under 10 employees and under €2 million turnover — are exempt.
-
A scanner alone won't get you there.
Automated tools catch only part of the requirements. A self-run scan that comes back clean creates false confidence — most of the standard can only be judged by a person who knows what to look for.
Not a list of problems. The finished work.
-
The conformance audit
Automated testing, AI-judged analysis, and expert manual review against EN 301 549 / WCAG 2.1 AA — built to WCAG 2.2 AA, ahead of the standard's next revision. Every finding verified by a human, not just flagged by a tool.
-
The fix package
Corrected design tokens, a theme adapter for your stack, and review-ready pull requests. Fixes cascade through your design system instead of patching screens one by one. This is the part nobody else delivers.
-
The documentation
A completed accessibility conformance report (ACR) and your public accessibility statement — the recognized documentation authorities and procurement teams ask for, written for you, not by you.
-
The validation
After your team merges, we re-test the full surface and hand over before/after evidence proving each gap is closed. You don't take our word for it — you get the receipts.
Before and after, on one screen.
This is what the fix package does to a product. Press the button and watch the tokens cascade.
- f-01 body text washed out and undersizedtokens corrected — readable at any sight level ✓
- f-02 button contrast too low to trustaccent token swapped — conformant contrast ✓
- f-03 no visible focus style anywherefocus ring token added — keyboard users see where they are ✓
- f-04 “click here” says nothinglink names its destination ✓
@@ design tokens — colour, type, focus @@
:root {
- --text-muted: #9aa3a0; /* 2.6:1 fails 1.4.3 */
+ --text-muted: #5d6663; /* 5.2:1 passes aa */
- --font-size-body: 13px;
+ --font-size-body: 1.0625rem; /* resizes — 1.4.4 */
}
- .btn:focus { outline: none; } /* hidden — 2.4.7 */
+ .btn:focus-visible {
+ outline: 3px solid var(--focus-ring);
+ outline-offset: 2px;
+ }Five steps. You keep the merge button.
-
Scoping call
Thirty minutes. We establish what you sell into the EU, what surface needs to conform, and whether the EAA applies to you at all. If it doesn't, we'll say so.
-
We test your staging environment
You share a staging URL — no codebase access needed to start. The pipeline runs the full audit; the expert judges what the pipeline can't.
-
You receive the fix package
Corrected tokens, the theme adapter for your stack, and pull requests ready for review — each one scoped, explained, and traceable to the requirement it satisfies.
-
Your team reviews and merges
Full control stays with you. We never touch production — everything arrives as proposals your engineers approve like any other code review.
-
Re-validation and handoff
We re-test against the merged result, close out the evidence, and hand over the ACR and accessibility statement. Done means documented.
The boundary is fixed: we work on staging, you keep the merge button. Nothing ships without your engineers' approval.
Three ways to spend the same budget.
-
Automated scanner
- Finds some of the issues — the machine-detectable fraction.
- Fixes nothing.
- A clean result reads as "we're fine." It isn't conformance.
outcome: false confidence
-
Traditional audit firm
- Finds the issues, often thoroughly.
- Hands you a PDF of findings.
- Your developers do the fixing — weeks of unplanned work.
outcome: a report, then a backlog
-
This service
- Finds the issues — automated, AI-judged, and expert-verified.
- Authors the fixes as tokens, adapters, and pull requests.
- You review, you merge, you're documented.
outcome: delivered conformance
Early, honestly priced, and limited by design.
This service is new, and the first clients get the advantage of that: the full delivered outcome at founding-client pricing, in exchange for a case study and a reference once the work proves itself.
One specialist runs every engagement personally, so concurrent capacity is genuinely limited — that's the only scarcity here, and it's real.
Book a scoping callOne specialist. An AI pipeline doing the volume.
Behind this service is one senior specialist with twenty years across architecture and enterprise UX — industrial systems, medtech, and autonomous-machine interfaces. Work where getting the interface wrong has consequences, and where "it passes the checklist" was never the bar.
The audit volume — crawling every page, testing every state, checking every token — is handled by an AI pipeline built on Playwright, axe-core, and Claude: the work that used to take an agency team. The judgment, the fixes, and the accountability stay with the specialist. You always talk to the person doing the work.
Operating from Switzerland under the AGEN-C K consultancy, serving EU and international clients in English.
The things people ask on the call.
Does the EAA apply to my company?
If you sell digital products or services to consumers in the EU — e-commerce, SaaS, banking services, booking, e-books, transport — the EAA applies, regardless of where you're headquartered. The exemption is narrow: microenterprises with fewer than 10 employees and under €2 million annual turnover. If you're unsure, that's exactly what the scoping call settles.
Do you need access to our codebase?
Not to start. The audit runs against a staging URL. Fixes arrive as design tokens, a theme adapter, and pull requests against the repository you choose to share — and repository access stays read-and-propose, never write-to-production.
What stacks do you support?
Any web stack can be audited and fixed. The deepest delivery expertise — where the theme-adapter approach shines — is React with Mantine or Tailwind, and any system built on CSS variables.
Is this a certification?
No, and be wary of anyone selling one — no official EU accessibility certificate exists. What exists, and what you get, is the recognized documentation: a completed accessibility conformance report (ACR) and a public accessibility statement, backed by test evidence.
How long does it take?
A standard product surface goes from first scan to delivered fix package in weeks, not months — the pipeline does the volume work in days, and expert review and fix authoring set the pace. Exact timeline is scoped on the call.
What happens after we're conformant?
Conformance drifts as you ship. Ongoing monitoring is available as a retainer: scheduled re-scans of your releases, drift flagged with proposed fixes, and your documentation kept current.