European Accessibility Act compliance for your website
Since 28 June 2025, organisations selling to consumers in the EU have to meet accessibility requirements for their websites and apps. We audit the pages where the risk sits and give you the code changes that fix them.
Does this apply to you?
Three questions.
- 01Do you sell products or services to consumers in the EU or Ireland?
- 02Do you have 10 or more staff and turnover above 2 million euros?
- 03Was the service launched or significantly changed after June 2025?
If the answer to the first two is yes, you are in scope wherever the company is registered. What matters is where your customers are, not where your office is. Services already on the market before June 2025 have until June 2030.
Türkiye has its own rule, and it is not the same one. A Presidential Circular published on 21 June 2025 sets WCAG 2.2 Level A. It gave banks, private hospitals, licensed private schools, passenger carriers and A-group travel agencies a year, and gives e-commerce providers under Law 6563 until June 2027.
What you get.
- 01The six screens that matterHome, category, product, basket, checkout and sign-in. That is where the legal risk sits, and auditing the other two hundred pages first is how a budget disappears.
- 02Manual testingKeyboard and screen reader, by hand. An automated scan finds about a third of it.
- 03Mapped findingsEvery issue tied to a WCAG 2.2 AA success criterion and the corresponding EN 301 549 clause.
- 04Prioritised by riskOrdered by legal exposure and user impact, so you know what to fix first. Some of it you can leave.
- 05Fixes a developer can applyThe specific component and the specific change, written for a developer to act on.
- 06Accessibility statementA draft statement you can publish, in the format the regulations expect.
We write the fix, not the finding.
Most audits end with a PDF and leave you to work out what to do with it. We have spent fourteen years building interfaces, seven of them on enterprise UK projects in banking and automotive, where compliance and security constraints were part of the brief from the first commit. The report we write is a list of changes a developer can act on, because we write the code too.
What the audit covers.
A fixed scope and a fixed price, both agreed before anything starts. You know which screens are covered and what the report will contain.
Remediation quoted separately once the audit is done.
Request an auditQuestions, answered.
WCAG is the technical standard. The EAA is the law that requires it. The EU harmonised standard EN 301 549 is what connects the two.
It is EU law, but the test is where your customers are. Sell to consumers in the EU and you are in scope, whether you are registered in the UK, in Türkiye or anywhere else. A UK-only business is covered by the Equality Act 2010 instead, which also points at WCAG.
A Presidential Circular of 21 June 2025 sets WCAG 2.2 Level A and set up a monitoring commission under the Ministry of Family and Social Services. Banks, private hospitals, licensed private schools, passenger carriers and A-group travel agencies had a year. E-commerce service providers under Law 6563 have until June 2027. It is a lower bar than the EAA, so a site built to clear the EAA already clears this.
Automated scanning finds a minority of the issues that matter. Keyboard traps, focus order, screen reader announcements and form error handling need a person.
We do not use or recommend them. They do not make a site conformant and they are widely criticised by disabled users.
It depends on what the audit finds. We quote it separately once we know the scope.
Find out where you stand.
Send us your URL. We will come back with scope, price and a start date.
This page is general information about accessibility regulations, not legal advice.