71% accessible was not enough for the court.
European Accessibility Act compliance for an app and a website that ship every fortnight. The Act has been enforced since 28 June 2025, and in June 2026 a French court ordered a retailer to bring both to full accessibility within six months, with €500 a day after that.
The statement is the first thing anyone reads, and it is the oldest thing you publish.
- The statement names a WCAG version from years ago, because nobody re-ran the audit.
- An AI tool fixed the obvious issues, and nothing recorded what was fixed or who accepted it.
- The app ships every fortnight, and the audit describes the version before last.
- Support is handling accessibility complaints with no record of what was promised.
- Everyone agrees it matters. Nobody can prioritise it against the change already going through.
- Losing customers who cannot use the product is invisible in the funnel.
A court, a regulator or a complainant starts with what you published. The question is whether it is still true.
In. Build. Leave. Prove.
One job, four weeks, in production. Then it keeps proving itself.
In
The journeys in scope, the standard you are held to, and who accepts each fix.
Build
Fixes proposed by AI, each checked against EN 301 549 before it goes in, alongside your developers.
Leave
Your team re-audits what a release touches, and the statement updates from the results.
Prove
A dated record of what was checked, what was fixed and who accepted it.
Three jobs a four-week deployment could take.
- Accessibility fixes on the app and site proposed by AI, each checked against EN 301 549 before it goes in and accepted by a named person, with the published statement updating when the audit is re-run.
- Drift: every release compared with the accepted baseline, and the variances flagged for your developers to investigate.
- Customer support and complaint handling, including accessibility complaints, triaged and drafted by AI with a named handler releasing every reply.
- Whichever we start with, the record is the same: what was allowed, what happened, who signed.
If a complainant or a court reads your statement today, can you show it is still true?
What the AI is allowed to do is written down first.
Every decision is checked against those rules before it happens.
A named person signs it off. The check produces the evidence; a person judges.
You can replay the whole history any day and get the same answer.
If anyone changes it later, it shows. Patent pending, UK application GB2620101.2.
The request
Show us that the Aurora Banking app meets EN 301 549.
From a procurement team · 2 Sep
What you show them
Account overview
42 checks
Signed off
QA lead · 4 Sep
Payments
38 checks, 2 fixes re-checked
Signed off
Product owner · 6 Sep
Onboarding
29 checks
Signed off
QA lead · 9 Sep
That is what a deployment leaves running for your job, and what the record holds. In the accessibility product today, a person on your team accepts every finding before it reaches your record.
Who this is for.
- Retail, media, travel and marketplace teams serving EU consumers.
- Product leaders shipping weekly who cannot re-audit by hand each time.
- Teams who have already done the obvious fixes and have nothing to show for them.
Not for
A widget or an overlay. Nothing is injected into your product, and nothing claims to fix accessibility from the outside.
Who you deal with.
You deal with Simon and Jason from the first call. One engineer sits inside your team, full time, for the four weeks.
Simon Milner, Founding Architect
He designed the record: what the AI is allowed to do, checked before it acts, and replayable afterwards. Twenty-five years in Silicon Valley before that.
Jason Crispin, Founder
He owns the customer side of a deployment: what the job is, what it is worth, and that it lands. He is on the first call and every one after.
Four weeks, then it keeps proving itself.
Week 1
The baseline
What the job is, what allowed means for it, and who signs. Written down before anything runs.
Weeks 2 to 4
The build
Our engineer works in your codebase next to your developers. The old way and the new way run side by side.
Week 4 on
The proof
Every decision checked and recorded, on AUDITSU, on a monthly subscription. Replay it any day. Your team runs the job; we maintain it if you ask.
What you keep
- The fixes, in your codebase, assigned to you in writing.
- The audit, running in-house on every release.
- The published statement, built from your results.
- The record of every check and acceptance, replayable any day.
What people ask.
Is the audit an automated check with a human verifying it?
Is the audit an automated check with a human verifying it?
The other way round. It is a guided audit your team answers, and every verdict is recorded against the person who made it. Automated tests help, but no AI decides whether you comply.
We already fixed the major issues with an AI tool. What would we gain?
We already fixed the major issues with an AI tool. What would we gain?
The fixes, probably nothing. What you cannot issue yourself is an independent, dated record that the claim in your published statement was true when you shipped, and that each fix was accepted by a named person.
Does the European Accessibility Act apply to us?
Does the European Accessibility Act apply to us?
If you provide e-commerce, banking, transport, telecoms, streaming or e-books to EU consumers, generally yes; it has been enforced since 28 June 2025. Urban and regional transport apps sit outside it, and air travel never does. We will tell you plainly if you are out of scope.
What happened in France?
What happened in France?
In June 2026 a court in Caen ordered a retailer to bring its website and app to full accessibility within six months, with €500 a day after that. Meeting 71% of the national standard was rejected: accessibility was treated as an obligation of result. It is an order with a prospective penalty, not a fine.
Can you catch what changes between releases?
Can you catch what changes between releases?
Comparing each release with the accepted baseline and flagging the variances is one of the jobs a deployment can build for you. It is not something the platform ships today, and we will not pretend otherwise.
What does it cost?
What does it cost?
Websites are free to audit, and apps are on the paid plan. A deployment is scoped on the call.
Where to go next.
When was your statement last true?
Thirty minutes with Simon and Jason. Bring the app, the statement or the complaint you have been sent, and you leave knowing what it would take.