# WCAG 2.2 AA accessibility audit and the EAA A WCAG 2.2 AA audit for business: a report listing every violation and the fixes shipped — WordPress, Webflow, Shopify or hand-written sites. From €210 net. **Canonical:** https://spoko.space/accessibility/ **Language:** en **Updated:** 2026-09-22 --- ## An accessible site that meets WCAG 2.2 AA *WCAG 2.2 AA · EAA* An audit, a report listing every violation, and the fixes — on your actual site, not in a slide deck. No scare stories about fines. Audit and report · Fixes implemented · Re-test · Solo, 15+ years [Get a quote](#quote) · [See what you get](#pricing) ## The EAA has applied since 28 June 2025 {#the-eaa-has-applied-since-28-june-2025} *Who it is for* The European Accessibility Act (Directive (EU) 2019/882) **has applied since 28 June 2025**, and it reaches private companies, not just the public sector. Most often: online shops, banking and payment services, telecoms, passenger transport, e-books and services giving access to audiovisual media. The reference standard is EN 301 549, which in practice means **WCAG 2.1 at level AA** — the same bar public bodies have had to meet for years. I audit against the newer WCAG 2.2, which contains every 2.1 criterion and adds a few of its own. Microenterprises providing services (fewer than 10 people and up to €2m turnover) are exempt from the service obligations. I won't try to scare you with enforcement — that is the weakest reason to do this anyway. An accessible site can be operated from the keyboard, read by a screen reader, and seen on a phone in sunlight. The work usually improves semantics and speed along the way, which [helps SEO](https://spoko.space/web-development/) too. If the site sits on a neglected WordPress install, start with [fixing and speeding that up](https://spoko.space/wordpress-rescue/) — then an accessibility audit has something to stand on. And if the question is not "can the site be operated" but "does AI understand what we do", there is a separate [AI Search Audit](https://spoko.space/ai-search-audit/) for that. ## The audit, the fixes, or both {#the-audit-the-fixes-or-both} *Pricing* Net prices, "from" — a quote depends on the number of unique templates and user journeys, not on the page count. You get one within 24 h. ### Accessibility audit {#accessibility-audit} **from €210** — one-off · net I check the site against WCAG 2.2 AA and you get a report you can actually work from. - Automated testing (axe, Lighthouse) plus a manual audit - Keyboard-only and screen-reader passes (NVDA, VoiceOver) - Report: the violation, the WCAG criterion, the place in the code - Priorities — what blocks a user, and what is cosmetic - A suggested fix next to every item - A quote for the remediation, no strings attached ### Remediation — Fixes {#remediation} **from €450** — one-off · net Already have an audit — mine or someone else’s? I implement the fixes in the site code. - Contrast, a visible focus ring, keyboard navigation - Semantics, headings, landmarks, ARIA attributes - Forms: labels, error messages, hints - Alternative text and descriptions for graphics - Fixes land in your site, not in a copy of it - A report of everything that changed ### Audit + fixes + re-test — Package {#audit--fixes--re-test} **from €590** — one-off · net Re-test included The whole way to conformance: the audit, the fixes and a re-test at the end. - Everything in the audit and the remediation - A re-test after the fixes, with a closing report - An accessibility statement for your terms of service - A short guide for whoever adds content - 30 days of questions and small fixes after sign-off I audit any stack — WordPress, Webflow, Shopify, a PrestaShop store or a hand-written site. Fixes go in wherever I can reach the code or the theme; on a closed platform you get a precise list of changes to raise with the vendor, and I verify the result. ## A report you can work from {#a-report-you-can-work-from} *What you get* Not a dump from a scanner — a list of things to do, in the order worth doing them. - **Violation by violation** — Every item carries its WCAG criterion, the place in the code, a screenshot and a suggested fix. - **Tested by hand, not only by a scanner** — Automated tools catch roughly a third of the problems. The rest only shows up on the keyboard and in a screen reader. - **Priorities, not an alphabet** — What genuinely blocks someone first — an unusable cart or form. The cosmetic items come last. - **Fixes in your own code** — Changes go into your site, its styles and its templates. No overlays, no widgets. - **A re-test** — After the fixes I check the same things again, and you get a closing report — the state of the site on the day of the test. - **An accessibility statement** — I write the statement for your terms of service, based on what the audit actually found. ## What I do, and what I will not promise {#what-i-do-and-what-i-will-not-promise} *Straight talk* Accessibility is the state of a site on the day it was tested, not a badge for life. Better said up front than in an email afterwards. ### What I do {#what-i-do} I bring the site up to WCAG 2.2 AA and show it in a report. - A manual and automated audit of the journeys that matter - Fixes implemented in the code, the templates and the styles - A re-test that shows which findings are closed - A short guide so new content does not undo the work [See pricing](#pricing) ### What I will not promise {#what-i-will-not-promise} In a WCAG audit I do not sell "100% compliant, forever" — nobody honestly can. - There is no such thing as a WCAG certificate — there is an audit and a dated report - I do not install accessibility overlays: they do not deliver conformance and they get in the way of real screen readers - Every new page, plugin and uploaded PDF can introduce new problems - I'm not a law firm — I tell you what the standard says, not how an enforcement case would end ## From a URL to a closing report {#from-a-url-to-a-closing-report} *How it works* Typically 2–3 weeks for an ordinary business site; longer for a store or an app. - **Enquiry and quote** — You send the URL and say what matters most. The quote and the dates come back within 24 h. - **Audit** — Automated testing first, then walking the key journeys with the keyboard alone and with a screen reader. - **Report** — Violations with their WCAG criteria, priorities and suggested fixes. We go through it on a call or by email. - **Fixes** — Changes go into the site code — the real blockers first, the cosmetic items last. - **Re-test** — I check the same things again, close the findings in the report and leave guidance for what comes next. ## Frequently asked questions {#frequently-asked-questions} ### What is WCAG 2.2 AA, in plain words? {#faq-what-is-wcag-22-aa-in-plain-words} It is a list of concrete conditions a site has to meet so it can be used without a mouse, without good eyesight and without sound. Level AA is the one the law points at: sufficient text contrast, a visible focus indicator, keyboard operation, sensible headings and form labels, descriptions for images, captions for video. Level AAA is stricter and is not required. ### Does the EAA apply to my company? {#faq-does-the-eaa-apply-to-my-company} Usually yes, if you sell to or serve customers online and you are not a microenterprise (fewer than 10 people and up to €2m turnover). The services named include e-commerce, banking and payment services, telecoms, passenger transport, e-books and services giving access to audiovisual media. Public bodies are covered by the older Web Accessibility Directive, where WCAG 2.1 AA has applied for years. If you are not sure which group you are in, write to me — I will tell you how it looks and I will not turn that into a sales call. ### Will I get a WCAG certificate? {#faq-will-i-get-a-wcag-certificate} No, because no such document exists — there is no body that issues WCAG certificates. What you get is an audit report: what was tested, by what method, what conforms, what does not, and on what date. That is the evidence people actually use, and it is what your accessibility statement is built from. ### Is an accessibility widget or overlay enough? {#faq-is-an-accessibility-widget-or-overlay-enough} No. Overlays promise conformance from a single script, but they do not fix the code underneath and they can get in the way of people using their own screen readers. Disability organisations have advised against them for years, and in the US sites have been sued despite having one installed. I do the fixes in the code. ### Do you only work on sites you built? {#faq-do-you-only-work-on-sites-you-built} No. I audit and fix any site: WordPress, Webflow, Shopify, a PrestaShop store or something hand-written. On closed platforms some things can only be changed by the vendor — then you get a precise list to raise with them, and I verify the result. ### How long does it take? {#faq-how-long-does-it-take} An audit of an ordinary business site is usually 3–5 working days from the start; the fixes take another week or two. A store or an app with a customer panel takes longer, because there are more journeys to walk. You get the dates with the quote, and I keep to them. ### What about the accessibility statement? {#faq-what-about-the-accessibility-statement} It is part of the package. For a private company it is a statement of how the service meets the requirements, which goes into your terms of service or general conditions. For a public body it is the formal accessibility statement in the prescribed template, built from the audit results. I write the text; publishing is yours or mine, depending on who has access. ### Will the fixes ruin how the site looks? {#faq-will-the-fixes-ruin-how-the-site-looks} No. Most of the work is invisible: semantics, labels, ARIA attributes, source order. Two things usually become visible — a clear focus ring when navigating by keyboard, and stronger contrast where the text was too light. Both can be done within your brand; if the brand colour fails on text, I propose a variant for that one use, not a new logo. ### Does accessibility help SEO? {#faq-does-accessibility-help-seo} It does, though that is a side effect. Proper headings, alternative text, meaningful link labels and faster code are things screen readers, search engines and the language models summarising your page all like. I do not sell accessibility as an SEO trick, though — it is done for people, and the ranking is a bonus. ### What keeps the site accessible afterwards? {#faq-what-keeps-the-site-accessible-afterwards} Two things cover the day to day: a short guide for whoever adds content (describe images, use real headings, never ship text as a picture) and a review every so often — around bigger changes, or once a year. I can do that as ongoing care, or you can call me in for a single review. ## Get a quote for an accessibility audit {#get-a-quote-for-an-accessibility-audit} Send the URL and two sentences about what you need — I’ll come back with a quote within 24 hours. I reply within 2 business hours.