European Accessibility Act & WCAG: Who Must Comply and By When

The European Accessibility Act (Directive 2019/882) is an EU directive requiring accessibility for a defined list of products and services, including e-commerce, banking services, transport ticketing and information, e-books, and telecommunications. EU member states transposed it into national law by June 28, 2022, and the compliance deadline for businesses was June 28, 2025 — meaning it's already in effect, not a future deadline.

Microenterprises — fewer than 10 employees and under €2 million annual turnover — are exempt from some obligations when providing services, but this exemption is narrower than it sounds: it generally doesn't apply to products, and larger businesses in scope have no such exemption regardless of how simple their website is.

WCAG (Web Content Accessibility Guidelines) is the W3C's technical standard for web accessibility, organized into three conformance levels: A (minimum), AA (the level referenced by most laws and by the EU's EN 301 549 standard), and AAA (the highest, rarely required in full). When a business says it's targeting "WCAG compliance," it almost always means WCAG 2.1 Level AA.

WCAG 2.2, published in October 2023, adds a handful of new success criteria on top of 2.1 rather than replacing it — most EU regulatory references, including EN 301 549, are still built around 2.1 AA as the operative baseline.

WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text against its background, and 3:1 for large text (roughly 18pt, or 14pt bold) and for UI components and graphical objects. This is one of the most common and most mechanically checkable accessibility failures on real websites — low-contrast text on light or dark themes is easy to introduce and easy to miss visually if you don't have low vision yourself.

No. Automated overlay widgets — the scripts that add a floating accessibility icon and claim to fix issues on the fly — do not achieve WCAG conformance or legal compliance on their own, and accessibility professionals have widely documented cases where they interfere with screen readers or introduce new problems. They can be a reasonable supplementary aid for some specific adjustments, but they're not a substitute for fixing the underlying markup, contrast, and structure.

Yes, though the mechanism varies by jurisdiction. Under the EAA, national market surveillance authorities can require corrective action and, in some member states, impose penalties for non-compliant products and services. Separately, accessibility-related litigation has become common in some jurisdictions — most visibly the US under the ADA — and EU businesses serving those markets face that exposure too. Within the EU, complaint-driven enforcement through national authorities is the more typical path than direct lawsuits.

The mechanically checkable parts — contrast ratios, missing alt text, unlabelled inputs, heading structure, keyboard-focus issues — are exactly what an automated scan is well suited to catch continuously. What a scan can't fully verify is real screen-reader usability and cognitive accessibility, which is why WCAG conformance claims for a business with real legal exposure should still involve manual testing or a professional audit alongside automated checks.