Digital accessibility,checked and fixed.
Since 28 June 2025 the European Accessibility Act makes digital accessibility a legal duty for many businesses selling to consumers online in the EU. I test your site, shop or app against WCAG 2.1 AA, tell you plainly what fails — and fix it in the code if you have nobody to do it.
First check whether you have to at all.
Online shops
Selling products or services to consumers through a website or mobile app — including the whole purchase path, cart and payment.
Banking and finance
Consumer banking services: transactional sites, mobile apps, application processes.
Passenger transport
Carrier websites and apps, electronic ticketing, travel information.
Telecoms and media
Electronic communications services, access to audiovisual media services, e-books and readers.
Micro-enterprises: exempt
With fewer than 10 people and turnover up to EUR 2 million a year, the Act puts no such duty on your services. An accessible site still pays off, but I won't scare you with inspections.
Public sector
Public bodies fall under separate web-accessibility rules — the technical requirements are in practice the same.
Basis: the European Accessibility Act (Directive (EU) 2019/882), implemented in Poland by the Act of 26 April 2024. This is a technical description, not legal advice — a lawyer should confirm how your business qualifies.
Four steps, the first one free.
Quick scan
step 1An automated scan of the home page and key subpages (axe-core, Lighthouse). You get the result by email: the issues found and whether a full audit makes sense.
WCAG 2.1 AA audit
step 2 · fixed priceAutomated and manual testing: keyboard, screen readers (NVDA, VoiceOver), contrast, forms, error messages, the purchase path. A report with each issue mapped to a WCAG criterion, prioritised, with a recommended fix.
Remediation
step 3 · hourlyFixes in your code — Angular, React, Vue, WordPress, plain HTML — or consulting for your team. An hours estimate after the audit, before work starts.
Monitoring
step 4 · subscriptionCompliance is not one-off: any significant interface change can break it. A monthly scan, a manual review of changes and a diff report, with hours for small fixes.
Net prices in PLN; Polish VAT (23%) applies where due. The audit price depends on the number of unique templates and flows — I confirm it in writing before starting.
Scan and call
You send the address, you get the scan result. On a 15-minute call we agree the scope: which templates and which flows go into the audit.
Audit and report
I test manually and automatically. You get a report developers can act on: what, where, which criterion, how to fix it, in what order.
Fixes and monitoring
You fix it yourselves or I do. After the fixes — a re-test and, if you want, ongoing monitoring and help with the accessibility statement.
An auditor who can also fix it.
01I am a developer, not only an auditor. The report doesn't stop at “missing attribute” — I point to the concrete change in the component and can ship it in your repository.
02I build accessible components every day: mk-kit, my open library of 165+ Angular components, has WCAG 2.1 AA as a design target. The code is public.
0318 years of experience, the recent ones in regulated industries — pharma (projects for Pfizer and GSK) and banking. I know what documentation read by a compliance team looks like.
Does the EAA apply to my business?
If you provide consumers with services covered by the Act — most often online sales — and you are not a micro-enterprise (fewer than 10 people and turnover up to EUR 2 million), most likely yes. A lawyer should confirm the final qualification; I cover the technical side.
Isn't an automated scan enough?
No. Automated tools catch only part of the problems — they can't judge whether a form can be completed by keyboard, whether a screen reader reads the cart sensibly, or whether an error message is understandable. That's why the scan is a free first step, not the audit.
Will I get a compliance certificate?
There is no official WCAG certificate. You get the audit report and — after the fixes — a re-test result, on which you can base your accessibility statement and your answers to a supervisory authority.
What if we have no developers?
Then I do the remediation, billed hourly, after an estimate delivered with the report.
Why monitoring once the audit is done?
Because the site changes. A new banner, a new cart step or a template update can introduce new barriers. Monitoring catches them before a customer or an inspection does.
Let's start with the free scan.
Send the site address. I'll reply with the scan result and an honest view on whether you need a full audit at all.