European Accessibility Act (EAA) & AI Readiness

With the EAA in force, accessibility is no longer an afterthought.

  • Ethics

    It is an ethical and moral duty to users who rely on assistive navigation tools every day.

  • Business

    It is a major business driver, because thousands of websites and mobile apps must now comply and need a capable technology partner.

  • AI-compliant

    It is a strategic advantage, because an accessible site is natively “AI-compliant.” Agentic navigation loves an accessible website.

Anyone in the industry knows just how much work goes into the “accessible transition.” We are here to simplify the process: ZeroAX is the SaaS platform that automates, simplifies, and accelerates accessibility audits and remediation plans at scale.

EN 301 549 AND EAA COMPLIANCE ENGINE

Others stop at syntax checks. We cover the meaning.

Standard scanners stop at code syntax and leave auditors a long manual “Needs Review” backlog. ZeroAX pairs deterministic scanning with a System 1 / System 2 semantic AI loop to speed up triage, manage remediation on a Kanban board and produce white-label EN 301 549 reports for every client.

  • Hosted on AWS in the EU (Milan)
  • No script to install on your site
  • Mobile and desktop
  • Multi-tenant and white-label
  • EN 301 549 checklist
Illustration of the ZeroAX dashboard with sample data: a list of findings, a count of passed checks, a count of items that need review, and a regression detected after a release.

Built around

  • WCAG 2.2 and 2.1
  • EN 301 549 V4.1.1 and V3.2.1
  • European Accessibility Act
  • AgID guidelines

Every audit is measured on the chapter 9 clauses of EN 301 549 that cite a WCAG success criterion, once on desktop and once on mobile: V4.1.1 with WCAG 2.2, or V3.2.1 with WCAG 2.1.

Scanners check the code. People read the meaning.

Rule engines such as axe-core and Lighthouse are the right baseline, and ZeroAX runs both, on mobile and desktop. But a rule can only tell that an attribute exists, not whether it makes sense. Everything else lands in a manual “Needs Review” queue.

A syntax scanner on its own

  • Passes alt="DSC_0921.jpg", because the attribute is not empty.
  • Passes a “Read more” link, because it has text.
  • Passes lang="it" on a page the visitor switched to English.

ZeroAX on top of it

  • Asks whether the text describes the image in its context.
  • Asks whether the link says where it goes.
  • Asks whether the page language matches the language the visitor chose.

An auditor, yours or ours, then confirms what the AI flags. ZeroAX shortens the review; it does not skip it.

SYSTEM 1 / SYSTEM 2

Semantic AI that answers the questions linters can't

A fast first pass (System 1) reads every element of the page's accessibility tree and settles what it can. What it cannot settle can go, at the auditor's request, to a slower and deeper second pass (System 2). What is still open reaches a person with the evidence attached.

  • WCAG 1.1.1 · EN 9.1.1.1

    Does the text actually describe this image?

    A linter passes alt="DSC_0921.jpg" because the attribute is filled in. The System 1 / System 2 loop checks whether the description makes sense where the image is used.

    <img src="team.jpg" alt="DSC_0921.jpg">
  • WCAG 2.4.4 · 2.5.3 · 4.1.2

    Does this button or link say what it does?

    Flags vague links such as “Read more”, custom controls whose ARIA state does not change, and Label in Name mismatches that stop voice control users.

    <a href="/news/42">Read more</a>
  • WCAG 3.1.1 · 3.1.2 · EN 9.3.1.1

    Does the screen reader language match the language on screen?

    Checks that <html lang> and the page text match the language the visitor selected, so a screen reader does not read English with Italian pronunciation.

    <html lang="it"> … Welcome back

How one finding moves through triage

Sample data
  1. Baseline axe-core: the image has an alt attribute. Passed
  2. System 1 The alternative text is a file name. Needs review
  3. System 2 It names a file, not the photo of the team. Proposed as failed for 9.1.1.1. Proposed: failed
  4. Auditor Confirms. An issue opens on the Kanban board with the steps to reproduce it. Failed

White-label EN 301 549 report

Sample data

Your logo, your client's name, and every chapter 9 clause with its result on desktop and mobile. We keep the full report for the demo.

  • 9.1.1.1 Non-text content Failed
  • 9.1.4.3 Contrast (minimum) Passed
  • 9.2.4.4 Link purpose (in context) Failed
  • 9.3.1.1 Language of page Passed

Book a live demo: we'll run the System 1 / System 2 engine on your URL and walk you through a full EN 301 549 report.

Book the live demo

From first scan to final report, in one place

  1. 01

    Scan, on mobile and desktop.

    A cloud crawler checks every page as a desktop browser and as a phone. The Chrome extension reaches what a crawler can't: logged-in areas, citizen portals and staging sites. Nothing is injected into your site.

  2. 02

    Semantic triage on the EN 301 549 checklist.

    System 1 / System 2 sorts the findings, and each one is attached as evidence to its EN 301 549 clause, ready for the auditor to confirm.

  3. 03

    Issues, Kanban and webhooks.

    A failed clause opens an issue with step-by-step reproduction and screenshots, tracked on a built-in Kanban board. Webhooks notify any external system, such as Jira, GitHub, GitLab or an ERP.

  4. 04

    Reports and no-regression monitoring.

    White-label reports ready for your client, in more than one language, and scheduled scans that flag new barriers after each release.

One platform, four ways to use it

Choose the profile closest to yours. The demo starts from it.

For system integrators

Enterprise scale, and integrations that fit the way your clients already work.

  • Webhooks into Jira, GitHub, CI/CD pipelines or an ERP
  • Multi-tenant governance across clients and business units
  • White-label EN 301 549 compliance reports
  • Hosted on AWS in the EU (Milan), with a dedicated deployment in the region of your choice for larger organisations
Book a system integrator demo

For web agencies and resellers

Sell accessibility audits and monitoring under your own name, to every client you manage.

  • A reseller account with a separate workspace per client
  • White-label reports in your clients' languages
  • Semantic triage that cuts the manual review hours eating into audit margins
  • No-regression monitoring for recurring retainers
Book a partner / white-label demo

For public bodies

Measure your services against the standard the law refers to.

  • Measurement on the EN 301 549 checklist and the AgID guidelines
  • Chrome extension to audit authenticated citizen portals, with no script injected
  • Data hosted on AWS in the EU (Milan), or in a dedicated deployment on request
  • Support with the AgID accessibility statement
Book a public sector demo

For private companies

A complete audit by our auditors and a remediation plan your developers can follow.

  • Turnkey audit and remediation plan, on mobile and desktop
  • Step-by-step reproduction for every issue
  • A built-in Kanban board to guide your developers
  • Monitoring after delivery, so fixes stay fixed
Book an audit & remediation demo

ITALY

Support for Italian requirements

For organisations operating in Italy, ZeroAX goes beyond the audit.

  • End-user assessment.

    An evaluation of how the site works for people, not only for scanners.

  • Remediation plan.

    A prioritised list of what to fix and why.

  • AgID accessibility statement.

    Guidance, ready-to-use content and a reminder before the yearly deadline. You submit the statement through the form on the AgID website.

Frequently asked questions

What does ZeroAX check?

Pages are checked against WCAG 2.2 and EN 301 549 v4.1.1 criteria on mobile and desktop: an axe-core and Lighthouse baseline, plus AI-driven semantic analysis.

What do System 1 and System 2 mean?

System 1 is a fast first pass over every element of the page. System 2 is a slower, deeper pass on the cases the first one could not settle, run when the auditor asks for it. Both explain their answer and cite the element they looked at.

Does automation replace manual testing?

No. Automated analysis speeds up the work and covers a large share of the criteria, but some require human judgement, and an auditor, yours or ours, confirms every result.

Can I audit pages behind a login?

Yes. The Chrome extension audits the page you have open, including logged-in areas and staging sites, without adding any script to the site.

Can I resell it under my own brand?

Yes. The platform is white label, multi-tenant and reseller-ready.

Can I manage several clients and domains?

Yes. Each client has its own workspace, and a workspace can cover multiple domains.

How does monitoring work?

The platform keeps checking your pages and flags regressions and new accessibility issues as they appear.

Do you help with the AgID accessibility statement?

Yes. We provide guidance, ready-to-use content and a reminder before the yearly deadline. You submit the statement through the form on the AgID website.

How much does it cost?

Pricing depends on how you plan to use ZeroAX. We'll go through it in the demo.

Book a live demo

We run the System 1 / System 2 engine live on your URL and walk you through a full EN 301 549 report.

Fields marked "required" must be filled in.