Accessibility audits · European Accessibility Act
I test your site the way disabled customers use it, with a keyboard and a screen reader, then give you a plain-language list of what to fix, in order, and a draft accessibility statement. No overlays, no scare tactics.
Pode escrever-me em português: respondo com todo o gosto.
Since 28 June 2025, the European Accessibility Act covers online shops and booking sites that sell to people in the EU. The technical benchmark is WCAG 2.1 AA (through the standard EN 301 549); I test against WCAG 2.2 AA, which includes it. In Portugal it's law under Decreto-Lei 82/2022.
Microenterprises are exempt for services: fewer than 10 staff and no more than €2 million a year in turnover. If that's you, accessibility is still good business, but the legal deadline isn't your problem.
Selling to the US? The ADA is enforced through lawsuits, and WCAG 2.1 or 2.2 AA is the usual benchmark there too. This is general information, not legal advice.
Your key journeys tested by hand with a keyboard and a screen reader: home, search, product, basket, checkout and account. Plus automated checks (axe-core, Lighthouse) on every template.
Every problem in plain language: what's wrong, who it stops, and the exact fix, ranked by impact. Your developer can start the same day.
The EAA expects you to publish one. You get an honest draft that matches what was tested and found, worded as "partially conformant with WCAG 2.2 AA, tested on [date]" until every issue is fixed.
Part of the audit price: when the fixes are in, I re-test the same pages so you know they're done, with before-and-after numbers.
A typical example from an online shop, the kind of thing an audit report is made of:
The button shows only a cart icon. A screen reader announces it as just "button", so a blind customer can't tell what it does, and can't buy.
- <button class="btn cart"><i class="icon-cart"></i></button> + <button class="btn cart" aria-label="Add to cart"><i class="icon-cart" aria-hidden="true"></i></button>
One attribute in the theme template fixes every product page at once.
Want to see a full before-and-after? The Crumbwell teardown takes a sample bakery checkout from 30 WCAG issues to 0 and an accessibility score of 78 to 100, with a 3-minute video. The Classly teardown does the same for a booking app (23 issues to 0, 54 to 100).
Covers up to 10 page templates (home, category, product, basket, checkout and so on), the report and the accessibility statement, delivered within 5 working days. Larger sites get a fixed quote within one working day. Fixing the issues is separate and optional: your own developer can do it, or I can, at a fixed price.
An automated accessibility and speed check of your homepage, with the top 5 fixes explained in plain language, emailed within two working days. It's a starting point: automated tools only catch part of the real problems (they can't tell whether a checkout makes sense with a screen reader), which is why the audit includes testing by hand.
No. Overlays add a toolbar on top of the site but leave the underlying problems in place, and they don't make a site meet WCAG. The fixes have to go into the site itself.
I do: Kevin McCalley, a designer and developer with more than 15 years on the web. I also built AccessBridge, a tool that checks sites against WCAG.
No. Everything works by email: you get a fixed quote in writing, the report as a document, and a short recorded walkthrough of the findings.