Emaration · EAA Ready
An EN 301 549 web conformance gap assessment for EU-facing US e-commerce. We run the same real axe-core checks and real WCAG 2.1 AA contrast math Emaration runs on itself, label every finding with its EN 301 549 clause, and tell you plainly what a machine verified and what still needs a qualified human.
What you get
Live axe-core rules plus sRGB contrast-ratio math over the page's sampled text — no illustrative placeholders. The contrast verdict is the genuine WCAG 2.1 AA threshold (4.5:1 normal, 3.0:1 large), and colours it cannot parse are skipped, never guessed.
Each gap carries its EN 301 549 Chapter 9 clause (9.x.y.z) and the WCAG success criterion it re-references. The register covers all 50 web clauses with a per-clause status: supported, partially supported, not supported, not applicable, or not evaluated.
Automation reaches only 9 of 50 clauses, and even those it can often check for presence only. A clause the engine did not test reads Not Evaluated — manual review required, never Supported. That rule is enforced in code, not in wording.
Why it holds up
Every report is an assessment and gap analysis, scoped to web content, against EN 301 549 V3.2.1 (2021-03), Chapter 9 (Web) — WCAG 2.1 Level A/AA. It is not a certification, a guarantee of conformance, or a legal opinion. A signed conformance statement is issued only by a named human, and only after counsel has scoped the exact claim wording and professional-liability cover is in place. Until then every artifact is an unsigned, watermarked draft.
Web-only v1 No-fabrication contract