If your Ontario business sells to customers in the European Union, there's a third accessibility regime you're now exposed to alongside Ontario's AODA and (for U.S. sales) the ADA: the European Accessibility Act (EAA). It has been applicable since June 28, 2025, and — this is the part most Canadian owners miss — it can reach businesses outside the EU that place products or provide services on the EU market. For a Shopify or e-commerce store in the GTA shipping to Germany, France, or the Netherlands, "we're a Canadian company" is not, by itself, an exemption.
Key facts
- The European Accessibility Act (Directive (EU) 2019/882) has been applicable since June 28, 2025 across EU member states.
- It covers e-commerce services (among others: banking, e-books, ticketing, electronic communications) sold to EU consumers — and applies to economic operators that place those services on the EU market, regardless of where the company is based.
- The technical benchmark is the harmonized standard EN 301 549, which for websites aligns with WCAG 2.1 level AA.
- A microenterprise exemption exists for service providers with fewer than 10 employees and ≤ €2 million in annual turnover — but it is not automatic for every business, and product rules are stricter.
- Penalties are set by each member state and vary; the practical exposure for most SMBs is removal/complaints and the cost of scrambling to fix a live store under pressure.
Why this matters for Ontario
Most Ontario owners think about accessibility as an Ontario problem (the AODA Compliance Report deadline of December 31, 2026 for organizations with 20+ employees) or, if they sell into the U.S., an ADA problem. The EAA adds a third overlapping layer for anyone selling into Europe. The trap is treating them as three separate projects with three separate checklists.
They're not. All three point at the same underlying thing: whether the actual code of your site works for people using a keyboard, a screen reader, or magnification. AODA references WCAG, the ADA is enforced against WCAG in practice, and the EAA's EN 301 549 maps to WCAG. Fix the source code once to a high WCAG bar and you address the substance of all three at the same time.
What an overlay can't do here
A widget bolted onto the page does not change this calculus. After the U.S. FTC fined accessiBe US$1,000,000 in 2025 for unsupported "compliance" claims, leaning on an overlay as your EU, U.S., or Ontario answer is the weakest position to be in — it's the signal that complaint-driven actors and regulators look for, not a defense. The EAA, like the others, is about whether the underlying experience works, which is exactly what an overlay leaves untouched.
What to actually do
- Map your exposure. Do you have 20+ employees in Ontario (AODA report)? Do you sell to the U.S. (ADA)? Do you sell to the EU (EAA)? Most growing Ontario e-commerce brands answer "yes" to at least two.
- Audit the real code, not the widget — against WCAG 2.2 AA, which meets or exceeds what AODA, the ADA-in-practice, and the EAA's EN 301 549 ask for.
- Remediate at the source and document it. Written, dated conformance evidence is what holds up — and it's the same artifact whether the question comes from Toronto, a U.S. plaintiff firm, or an EU market-surveillance authority.
PassProof is a remote-first accessibility-engineering studio serving Ontario. We don't install overlays — we audit and fix the real source code to WCAG 2.2 AA and give you documentation you can stand behind across every market you sell in.
See where your site stands in about 30 seconds — free PassProof Report: getpassproof.com. No obligation.
This article is general information, not legal advice. Obligations under the EAA, AODA, and ADA depend on your size, what you sell, and where — confirm your specific situation with qualified counsel.