EAA Readiness Checker for the European Accessibility Act

What the EAA readiness checker actually does

AccessGuard is an automated accessibility scanner. It crawls the pages you point it at, runs machine-testable checks against the Web Content Accessibility Guidelines (WCAG 2.1 Level AA), and maps the results into readiness signals framed around the technical expectations most commonly associated with the EAA. You get a prioritized list of detected issues, the elements involved, and developer fix guidance for each one.

These are readiness signals, not a compliance verdict. Automated tools reliably catch a meaningful share of accessibility barriers, such as missing alt text, low color contrast, unlabeled form fields, missing document language, and broken heading structure. They cannot judge everything a human would, including whether alternative text is actually meaningful, whether a complex widget is usable with a screen reader end to end, or whether your content makes sense to a real assistive-technology user.

Use the checker to find and remove obvious barriers fast, to track progress over time, and to brief your developers with concrete, reproducible findings. Treat it as the automated layer of a broader accessibility program that also includes manual testing and, where appropriate, professional and legal review.

Who the European Accessibility Act applies to

The EAA (Directive (EU) 2019/882) is EU law that has been transposed into national law across all 27 Member States. It targets a defined set of consumer-facing products and services rather than every website in existence. Covered digital services commonly include e-commerce platforms, consumer banking and financial services, electronic communications, audiovisual media services such as streaming, transport services including websites, apps, and electronic ticketing, and e-books and their reading software.

Scope follows the market, not just the head office. Economic operators that place covered products on the EU market or provide covered services to EU consumers can fall within scope regardless of where the business is legally based. That means a company outside the EU selling to European customers may still need to consider the EAA.

There is a narrow microenterprise consideration for services. Businesses providing services with fewer than 10 employees and annual turnover or balance sheet total at or below 2 million euros may be exempt from certain service accessibility requirements, but this does not extend to products, and the details depend on national implementation. Whether the EAA applies to your specific organization is a legal question, and you should confirm your obligations with qualified counsel.

The 2025 deadline and the transition timeline

Enforcement of the EAA began on 28 June 2025. New products and services placed on the market or provided from that date are generally expected to meet the applicable accessibility requirements.

There are transitional arrangements for some products and services that were already on the market before the deadline, with a further period running toward 28 June 2030, and some contracts and self-service terminals have their own timelines. These transition rules are specific and fact-dependent, so do not assume a general grace period applies to your situation.

Enforcement is handled at the Member State level, and penalties vary by country. Authorities can require corrective action, order accessibility audits, restrict non-compliant offerings, and impose fines that differ substantially between jurisdictions. Early enforcement activity has already begun in some Member States. The practical takeaway is simple: the sooner you find and fix real barriers, the smaller your exposure and the better the experience for your users.

How EAA readiness maps to WCAG and EN 301 549

The EAA itself does not spell out line-by-line technical rules. For information and communication technology, the harmonized European standard EN 301 549 provides the technical requirements, and it incorporates WCAG Level A and AA success criteria for web content. Conforming to the relevant harmonized standard creates a presumption of conformity with the underlying requirements, which is why WCAG conformance sits at the center of most practical readiness work.

AccessGuard tests against WCAG 2.1 AA, which is the current foundation reflected in EN 301 549. A newer version of the standard aligning with WCAG 2.2 is expected as the ecosystem evolves, and our checks are updated as guidance matures. Because EN 301 549 also reaches non-web software, documents such as PDFs and office files, hardware, and telecommunications equipment, an automated web scan covers an important part of the picture but not all of it.

That is the honest boundary of any scanner. Meeting every WCAG success criterion an automated tool can detect is necessary groundwork, but full readiness also depends on manual testing, assistive-technology review, and non-web elements the scanner does not touch.

Practical steps to improve your EAA readiness

Start with a clear inventory. Identify which of your services are consumer-facing and potentially in scope, then confirm your obligations with qualified counsel rather than guessing. Knowing whether you are in scope, and under which transitional timeline, shapes everything that follows.

Run a scan to establish a baseline. AccessGuard gives you a prioritized issue list and readiness signals across your key user journeys, such as browsing, account creation, checkout, and support. Fix the high-impact, machine-detectable issues first, because they are the easiest wins and the most common findings: contrast, labels, alt text, focus order, and document language. Then layer in manual and assistive-technology testing for the interactions automation cannot fully judge.

Make accessibility ongoing rather than a one-time cleanup. Re-scan after each release, keep a documented record of what you tested and fixed, and build accessibility checks into your development workflow. If your team lacks the bandwidth, VASTROX can help with accessibility repair, web development, WordPress maintenance, and hosting, so remediation actually ships instead of sitting in a backlog.

• Confirm whether your services are in scope with qualified legal counsel
• Scan your key journeys with AccessGuard to get a WCAG-based baseline
• Fix high-impact automated findings first: contrast, labels, alt text, language, focus order
• Add manual and screen-reader testing for complex components and flows
• Cover non-web assets too, including PDFs and downloadable documents
• Re-scan on every release and keep a record of what you tested and fixed

Important disclaimer on legal compliance

VASTROX AccessGuard provides an accessibility scanner, WCAG issue detection, EAA readiness signals, and developer fix guidance. It does not provide legal advice and does not guarantee legal compliance with the European Accessibility Act, EN 301 549, WCAG, or any other law or standard.

No automated tool can certify legal compliance, because compliance depends on your specific scope, jurisdiction, content, user experience with assistive technology, and factors that require human and legal judgment. Our readiness signals are designed to help you find and prioritize real barriers, not to replace a formal audit or legal counsel.

For decisions about your obligations under the EAA and how they apply to your organization, consult a qualified accessibility professional and a lawyer. Use AccessGuard as a fast, practical way to identify issues and guide fixes, alongside the human review that genuine readiness requires.

Frequently asked questions

More accessibility checkers