DIRECTIVE (EU) 2019/882 · IN FORCE SINCE 28 JUNE 2025 EU-HOSTED · GDPR-CLEAN
EAA Compliance

ACCESSIBILITY

Accessibility statement for eaacompliance.org

PREPARED 1 May 2026 · REVIEWED AT EVERY RELEASE · WE HOLD OURSELVES TO WHAT WE SELL

We sell accessibility monitoring. It would be indefensible to publish a statement about our own site that we would not accept from a customer — so this one is produced the same way theirs are, and it says what is still wrong.

Compliance status

PARTIALLY COMPLIANT This website is partially compliant with EN 301 549 (WCAG 2.1 level AA) due to the non-compliances listed below. The status is computed from our own coverage matrix — we cannot select it, any more than a customer can.
50criteria in scope
31machine-tested
19human-verified
2open items

Known problems

The content listed below is non-accessible, or was until the release named against it. Each item stays here until a scan or a named review confirms the fix — including the ones we have just closed, because a statement that quietly drops its own defects is not evidence of anything.

  • Enforcement map conveyed status through colour alone. Each country tile now carries a visible status glyph as well as its colour, and the list view states the status in words. Fixed 1 May 2026
  • The 90-day history bars on the status page had no text alternative. Each component now has a written summary — days operational, degraded, in outage and not yet measured — visible on the page, not only in an image label. Fixed 1 May 2026
  • Code samples scrolled horizontally and could not be reached by keyboard. Scrollable code regions are now focusable with a visible focus indicator, and wrap rather than scroll on narrow viewports. Fixed 1 May 2026
  • Long data tables in the portal scroll horizontally on small screens. They are reachable and labelled, but we want a genuine responsive layout rather than a scroll region. Open
  • No published EU representative under Article 27. Not a WCAG matter, but a compliance gap on our side, and it belongs in the same list as the others. Open

How we tested

This statement was prepared by self-evaluation on 1 May 2026, using:

  • Our own scanner against every public page, on the same engine our customers use.
  • Keyboard-only traversal of each page and every interactive component, including the portal.
  • Screen-reader passes on the flows that matter most: signing in, adding a domain, reading findings, and taking an export.
  • Manual review of the nineteen criteria that automation cannot decide, recorded as named sign-offs with dates.
Roughly a third of the standard can be checked by machine. That is true of our site as much as anyone’s. Any vendor — including us — claiming a fully automated conformance result is describing about 31 of these 50 criteria. The other 19 were signed off by a person here, by name and date, and we will show you the record.

We monitor ourselves like a customer

eaacompliance.org is a verified domain inside its own platform, on the same scanning schedule as a paying account. Our findings enter the same triage engine, our sign-offs land in the same append-only ledger, and this statement regenerates from that evidence rather than being rewritten by hand.

When we break something, it appears on our own coverage matrix first. That is the point.

Feedback and contact

Report a barrier
[email protected]
Response target
We aim to respond within 5 working days, and to fix or schedule the fix within 20.
Alternative format
Ask and we will provide any document on this site in a format that works for you.

Enforcement procedure

If you are not satisfied with our response, you may contact the market surveillance authority responsible for digital accessibility in the country where you are located. Our enforcement tracker lists the authority and route for each European country, including the one that applies to us.

Where this statement stands today. Our scanning infrastructure is being brought online. Until eaacompliance.org appears in its own coverage matrix with completed scans, the figures above come from manual review and the automated checks we ran during development — and this paragraph stays here saying so. When the matrix is live, this statement regenerates from it and this note goes away.

PREPARED BY EAACompliance.org · REVIEWED AT EVERY RELEASE · THIS DOCUMENT DESCRIBES TESTING AND EVIDENCE; IT DOES NOT CONSTITUTE A COMPLIANCE GUARANTEE