Selling into Europe? The Accessibility Act Deadline Is Eight Months Out

A compliance date is making the crossing this quarter from legal memo to project plan, and this post is the escort. June 28, 2025. That is when the European Accessibility Act, Directive 2019/882, adopted five years ago and since written into member-state law, starts applying to a defined set of products and services offered to consumers in the EU market. Prominently included: e-commerce, consumer banking, transport booking, and e-books.

The jurisdictional reach that matters most to this audience, put plainly: the obligation follows the market, not the headquarters. A U.S. university selling programs to EU consumers through its online channels. A U.S. retailer shipping to European customers. A SaaS product with EU consumer users. The act’s scope questions reach them all. Member-state enforcement, varying by country and with real penalties, attaches.

The eight months remaining are, for institutional speeds, exactly the width our usual accessibility advice requires. Enough for a practice-mode team to pull its papers together. Barely enough for a project-mode organization to build what the documentation describes. Scope first, honestly drawn. Then the delta for teams already practicing. Then the paperwork that is genuinely the new work. In order, with the pattern note this series has been building toward at the end.

Scope, honestly drawn

The boundaries, as the directive and the emerging member-state guidance draw them, with the usual reminder that we are practitioners and your counsel owns the final reading. In scope: the listed consumer-facing services offered into the EU market. E-commerce is the broad gate most of this readership enters through. If EU consumers can buy, book, or enroll through your digital channels, the analysis starts. Consumer banking and payment interfaces. Booking and info services for passenger travel. E-books and their reading platforms. And the consumer-terminal tiers, ATMs, kiosks, for organizations that run them.

Largely out: pure B2B services, since the directive is consumer-protection law. Purely domestic operations with no EU market offering. And microenterprises: the carve-out for service providers under ten staff and under two million euros.

The standing caution: ‘offered into the EU market’ is a facts-and-circumstances question. Currency, shipping, language aim, marketing. It deserves counsel’s hour now rather than a regulator’s letter later. The scoping exercise itself is this quarter’s first assignment. List which properties, flows, and services touch EU consumers, with the same census rigor our governance coverage prescribes. The duties attach to surfaces you can only judge if you have listed them.

The delta for teams already practicing, and the paperwork

• The technical baseline lands on familiar ground: the EAA’s technical rules flow through EN 301 549, the European standard whose web parts fold in WCAG. 2.1 AA remains the practical floor, with 2.2 the current target per last year’s coverage. Teams running the practice covered here since 2010 are looking at a modest technical delta. The conformance work is largely the work already done or underway.

• The paperwork is the new work, and it is real: what the EAA adds beyond WCAG conformance is the compliance apparatus. Conformity assessment and documentation: the technical file showing how requirements are met. Accessibility statements: public, specific, kept fresh. The EU public-sector category, now arriving for private services. Complaint and feedback channels: staffed, responsive, documented. Plus the ongoing-duty mindset. Accessibility as a thing you keep up, not a launch-day trophy. Practice-mode teams already hold it. Project-mode teams find it culturally new.

• The vendor tier inherits the duty: the platforms, payment providers, booking engines, and embedded services inside your in-scope flows are part of your compliance story. The procurement-documentation habit, conformance papers requested and kept, becomes essential, and the vendor letters should go out this quarter with the June date attached.

Accessibility law converges on WCAG

This deadline completes a shift we have tracked for nearly fifteen years. Accessibility law is going global on shared WCAG foundations. The EAA now. The U.S. Title II rulemaking landed this spring for public entities, WCAG 2.1 AA, with dated compliance windows, for state and local government digital services. The sector rules piling up: transportation, healthcare, procurement. The ADA litigation baseline unchanged. And the international spread running the same direction. Different laws, different enforcement, one technical base. Exactly the consolidation last year’s coverage anticipated when it called WCAG version literacy a compliance-planning skill.

The strategic consequence is the series’ oldest sorting, now at global scale. Practice-mode teams absorb each new regime as paperwork. The same conformant site, described in each jurisdiction’s required paperwork. The EAA’s technical file, the Title II timeline, the procurement attestations. All drawing on one maintained practice.

Project-mode teams meet each regime as a fresh crisis. The re-audit, the re-fix, the re-panic. Multiplied now by jurisdiction. The arithmetic between the modes widens with every statute. The statutes are visibly not finished arriving. Eight months is practice-building time, barely, but truly, for organizations that start with the scoping inventory this quarter and the conformance-paperwork assembly next.

The assignment sequence

Compressed for the planning meeting this post should convene. The scoping inventory and counsel’s hour this quarter: which properties and flows are in. The gap check against the practice you already run: modest, if the advice in this series has been followed, sizable and urgent if not. The vendor letters with the June date. The documentation assembly through the winter: the technical file, the statements, the feedback channels. And the June 28 date entering the site’s compliance calendar beside the ones it joins.

And the series note. We have taught accessibility as audience, as craft, and as quality engineering since 2010. Also as legal risk and as mission. Always with the same underlying claim. The work is one work, done once, properly, as practice. Every frame (the letters, the rulings, the statutes, now the global convergence) keeps arriving to re-price the same investment upward.

Eight months out, the claim holds. The practice-mode readers are assembling paperwork for sites already built to code. The door remains open, as it always has been, at exactly the width of the time remaining. Start. The regulators post their standards. The teams that built to code all along just file the forms.