Emaration.AI · EAA Ready

Methodology

How the assessment is designed.

EAA Ready is a mapping and labeling layer on top of real accessibility checks. It does not invent a new scanner, and it does not assert conformance for anything it did not measure.

The pipeline

The steps below are the design.

  1. 1 — Render & scan (out of isolate)

    You give us one public URL. The page is rendered in a real headless browser on the Browser Rendering engine, where axe-core runs and the computed text/background colour pairs are extracted. A Cloudflare Worker cannot launch a browser, so this step runs on the api gateway / ada-watch engine and returns the raw evidence.

  2. 2 — Evaluate contrast (in isolate)

    We compute the genuine WCAG 2.1 AA contrast ratio for each sampled pair against the required threshold. A colour we cannot parse is skipped, not failed — we never fabricate a verdict from a value we could not read.

  3. 3 — Label to EN 301 549

    Each finding is tagged with its WCAG success criterion and the EN 301 549 Chapter 9 clause that re-references it (clause 9.x.y.z corresponds to WCAG x.y.z). Every clause number comes from the published standard; none is invented.

  4. 4 — Build the register & render the draft

    All web clauses get a per-clause conformance status, with machine-verified rows kept visibly separate from the rows that require manual review. The output is an unsigned, watermarked draft report carrying the locked EOCS receipt.

The honesty contract

Not evaluated is not a pass

A clause outside automated coverage reads Not Evaluated — manual review required. No clause reads Supported from automation — not even Contrast (1.4.3): the contrast math measures the text/background pairs it can sample, and text over an image, a gradient or an overlapping layer is not among them, so a clean sample reads Partially Supported and says what it did not measure.

Automation is partial by nature

Independent studies put fully-automated detection at roughly 30–40% of accessibility issues. Keyboard operation, screen-reader flow, captions, reflow and cognitive aspects are left for a qualified human evaluator, and the report says so on every uncovered clause.

Unsigned until counsel scopes it

The conformance statement is signed by a single named human, only after counsel scopes the exact claim and professional-liability cover is in place. Technical analysis never substitutes for the signature.

The standard & sources

Assessed against EN 301 549 V3.2.1 (2021-03), Chapter 9 (Web) — WCAG 2.1 Level A/AA.