Frequently asked questions

EN 301 549 v3.2.1 is cited in the Official Journal under the Web Accessibility Directive (EU) 2016/2102, where meeting its applicable clauses confers a presumption of conformity. Under the EAA no revision is cited yet — so today an EN 301 549 report is the strongest evidence available, not a legal certification, and final responsibility rests with the economic operator placing the product or providing the service.

It depends on the EN 301 549 revision in force: v3.2.1 maps to WCAG 2.1 AA, and the v4.1.0 (2026-06) final draft maps to WCAG 2.2 AA. v3.2.1 is the revision cited in the Official Journal today, so it is our default; v4.1.0 (2026-06) is a Harmonised European Standard final draft — not adopted by the ETSI/CEN/CENELEC vote and not yet cited in the Official Journal, with final v4.1.1 expected from that ballot — and every artefact generated against it says so. Our reporting is version-aware — you pick the revision and the report follows it.

Yes. The EN 301 549 conformance report is surface-aware across all ten chapters in which the standard states requirements — Chapter 4 (Functional Performance), Chapter 5 (Generic), Chapter 6 (Two-way voice communication), Chapter 7 (Video capabilities), Chapter 8 (Hardware), Chapter 9 (Web), Chapter 10 (Non-web documents), Chapter 11 (Software), Chapter 12 (Documentation & support services) and Chapter 13 (Relay & emergency service access) — so the report you get matches what you audited. The catalog holds every normative clause of the revision; what it leaves out is the conformance-claim machinery and the Electronic Programme Guide clauses. Clauses with no WCAG equivalent are rendered as explicit “manual review required” rows rather than silently dropped — and in Chapters 6, 7, 8 and 13 that is every clause, because none of those chapters references WCAG at all.

The audit is not. The engine, scoring and reporting are self-hosted: page content, screenshots and results stay in your environment, and the only outbound traffic is to the site you asked us to audit. The optional AI features are the exception, and they are off by default — if you enable one, you supply your own cloud AI provider and API key, and the relevant content and prompts go to that provider. Leave AI unconfigured and nothing leaves your environment at all. That distinction matters for banking, government, healthcare and other regulated sectors evaluating EAA readiness, so we state it rather than answering a flat no.

No. The EAA is an EU instrument; the UK has its own regime (Equality Act 2010 / the public-sector body accessibility regulations). We support a UK conformance target for reporting, but the EAA does not extend to the UK — don't conflate the two.

It is expected to be cited in the Official Journal of the EU around October 2026. We track the cited revision, and our version-aware reporting follows it — so your reports stay aligned with the harmonized standard in force.