Skip to content
emailrules.today
In forceContentIn force 28 Jun 2025Verified 1 Aug 2026

The Accessibility Act covers your shop, not obviously your newsletter

Does the European Accessibility Act apply to marketing emails?

European Union

In one sentence

The EU Accessibility Act as written targets e-commerce services (sites/checkout) — it does not name marketing email as a covered product.

Emailrules interpretation

Vendors sold panic that every newsletter must be WCAG-perfect by June under the European Accessibility Act. The Directive text focuses on e-commerce services (website and checkout style products), not a line that says “all marketing email.” Accessible email is still good practice and may be required by contracts or other rules — but do not confuse sales decks with the statute.

Why it matters. Budget the right work: fix the storefront path the law covers; improve email accessibility for users without paying for fake urgency.

Dotted words open definitions. See how email actually works.

What to do

Your move — not a lecture

Good to know — nothing to fix

Changes a number you report or a risk you carry, not today's task list.

Nothing to do, because the obligation being sold to you does not clearly exist for marketing email. Your advertising accessibility-ready templates is a nice-to-have, not compliance.

Your part: Judgement at the edges. Where an email is itself the mechanism for concluding or confirming the contract, the scope argument is much stronger. And accessible email is worth doing anyway: about one in six people has a disability and your emails render for them too.

What to do first

Nothing urgent. If you want the actual win, fix your text-to-image ratio and use semantic headings in your master template, because that pays off in Apple Mail summaries whether or not the Directive ever reaches you.

You can skip this if: You do not sell to consumers in the EU.

Who this applies to

Businesses selling to EU consumers. The obligation attaches to the covered service, so the strength of the argument depends on how close a given email sits to the actual transaction.

Checklist

  • 01Read Article 3(30) before you accept a vendor's scope claim. The definition is narrow and specific.
  • 02Treat order confirmations and mail as the higher-risk case, not the promotional newsletter.
  • 03Do the accessibility basics regardless: semantic headings, real text, alt text, contrast. They also fix how Apple summarises you.
  • 04Ask any vendor quoting this at you to name the Article. Most cannot.

That’s enough to act. The exact wording, the enforcement record and the primary source sit under Proof & sources, for counsel, bosses, or AI tools that need a citation. Not legal advice.

Proof

Exact position, enforcement, sources

For records and people who will check you. Skip if Monday’s move is already clear.

Source fact

Directive (EU) 2019/882 has applied since 28 June 2025 and covers six categories of service, one of which is e-commerce. Article 3(30) defines an e-commerce service as one provided at a distance through websites and mobile applications with a view to concluding a consumer contract. Marketing email is not named anywhere in the Directive, and the widely repeated claim that every newsletter had to meet WCAG 2.1 AA by that date is not supported by the text.

What happens if you do not

Enforced by member states, and Germany's transposition, the Barrierefreiheitsstärkungsgesetz, carries fines up to 100,000 euros. We have found no enforcement action anywhere against a marketing email on accessibility grounds. The urgency around this one has been manufactured largely by people selling audits.

Source

  • Directive (EU) 2019/882 on the accessibility requirements for products and services, Articles 2 and 3(30)
    Published 17 Apr 2019Read primary source

History of this page

  • Added, specifically to state the scope limit. The prevailing advice in the market overstates what the Directive says about email.

Related

Take this with you

GET https://emailrules.today/rules/eu-accessibility-act-marketing-email?format=json

Same URL, same answer, every field including the ones behind the Proof tab. An Accept: application/json header on the plain URL does the same thing. All the endpoints.