Do Emails Need to Be ADA Compliant? The Honest Legal Answer

Short answer: yes, treat your emails as covered. No U.S. regulation names email marketing, and we could not find a published court decision that turns on a promotional email alone — but the ADA covers how a business open to the public communicates with its customers, and the Department of Justice already lists accessible electronic documents among the aids businesses may need to provide. If your website has to work for a blind customer, the email that brought them there does too.

That’s the honest version of an answer most ranking pages fudge. Overlay vendors imply there’s settled email case law (there isn’t), and email platforms imply their templates handle it (they don’t). Here’s what the law actually says, what the data shows, and how to fix your Mailchimp or Klaviyo templates this week.

What the law actually says about email

The ADA never mentions email — it never mentions websites either. Title III requires that businesses open to the public provide “full and equal enjoyment” of their goods and services to people with disabilities, and the Department of Justice’s web guidance confirms it “does not have a regulation setting out detailed standards” for how businesses meet that online. Businesses can choose how they comply, and the DOJ points to WCAG as the reference.

Email fits through a second door as well: effective communication. Under the DOJ’s effective communication requirements, the auxiliary aids a covered business may need to provide include “accessibility features in electronic documents and other electronic and information technology that is accessible (either independently or through assistive technology such as screen readers).” An HTML email is an electronic document. If it carries an offer, a code, or an appointment detail a screen-reader user can’t extract, that’s a communication failure in exactly the sense the regulation describes.

The direction of travel matters too. In 2024 the DOJ formalized WCAG 2.1 AA as the required standard for state and local government web content — we break down what that means in our Title II web rule explainer. For private businesses the standard is still informal, but every DOJ signal for a decade has pointed at the same benchmark.

Has anyone actually been sued over an email?

Not over an email alone, as far as the public record shows. The thousands of digital-accessibility lawsuits filed each year overwhelmingly target websites and mobile apps — we track the filing data in our 2025 lawsuit numbers breakdown. Be skeptical of any vendor page that implies email case law is settled. It isn’t.

But “nobody has lost a case over email yet” is thin protection, for two reasons. First, the legal theory that wins website cases — a covered business, a digital barrier, a customer who couldn’t complete the same transaction a sighted customer could — applies to email without modification. Nothing in the statute distinguishes a message you send from a page you host.

Second, and more practically: your email is step one of a journey that ends on your website. A subscriber who can’t read your promotion, or who clicks through to a checkout that breaks under a screen reader, has hit the same wall twice. Plaintiffs’ testers document the whole journey, and the destination page is where the complaint gets written. That’s why email accessibility and ecommerce accessibility are the same project wearing two shirts.

Almost every marketing email fails — including yours, statistically

The email channel is in worse shape than the web. According to the Email Markup Consortium’s 2026 accessibility report, 99.88% of the 376,348 HTML emails it analyzed between May 2025 and May 2026 contained “Serious” or “Critical” accessibility defects. Exactly 8 emails — from three brands — passed every automated check. Every email the project collected from Substack, Shopify, and Beehiiv failed.

This isn’t a niche audience problem. Litmus’s 2026 email accessibility guide notes that one in four U.S. adults has a disability, citing CDC data. If your list has 4,000 subscribers, a four-figure slice of it is affected by decisions as small as your link labels.

Here are the most common failures the EMC found, mapped to the WCAG success criteria they violate:

Two of those five — the language attribute and the presentation role — live in your template code and get fixed once. The other three are content habits you build into every send.

The 7-point accessible email checklist

Apply WCAG 2.1 AA to an email and it collapses into seven habits:

1. Write alt text for every meaningful image. Describe what the image communicates — “40% off all running shoes, ends Sunday” — not “banner image.” Our alt text guide covers the judgment calls.
2. Never send an image-only email. If the offer exists only inside a JPG, subscribers with images blocked and every screen-reader user get nothing. Keep offers, dates, and codes in HTML text — this is also what 1.4.5 Images of Text requires.
3. Check your contrast. Brand-gray text on white fails constantly. Run your text and background colors through our color contrast checker — you need 4.5:1 for body text.
4. Label links by destination. “Shop the sale” beats “click here.” A screen-reader user pulling up a list of links hears the label with zero surrounding context.
5. Use real heading structure. One main heading, logical subheads, applied through your editor’s heading styles — not bolded body text.
6. Set the language and font size in your template. A missing lang attribute makes some screen readers guess the pronunciation rules. And keep body text at 16px or larger.
7. Keep the plain-text version, but don’t hide behind it. Most clients render the HTML version by default, so the HTML version is the one that has to work.

How to fix it in Mailchimp

Mailchimp’s builder supports every item on that checklist — it just doesn’t do the work for you. The platform’s own accessibility guidance tells senders to add alt text, use HTML heading levels for hierarchy, write descriptive links, and keep contrast high, and it generates a plain-text alternative automatically.

The mechanics: every image block has an alt text field — Mailchimp’s alt text help doc says to keep it to a sentence or two, use punctuation so screen readers pause naturally, and mark purely decorative images as decorative. Heading styles live in the text block’s style dropdown. What Mailchimp won’t stop you from doing: sending an all-image email, pasting “LEARN MORE” as your only link text, or choosing a pale gray that fails contrast. Those are your calls, every send.

How to fix it in Klaviyo

Klaviyo publishes an accessibility best-practice reference that is unusually blunt for an ESP: add alt text to all images, avoid image-only emails, avoid using images to convey key details, use starkly contrasting colors, separate ideas with headers, and write descriptive links — its own example is “Shop the collection” instead of “Click here.”

In the template editor, the alt text field sits in each image block’s settings, and heading styles are in the text block toolbar. Klaviyo also supports text-only emails for senders who want a maximally compatible fallback. Same caveat as Mailchimp: the fields exist, but the EMC data above shows almost nobody fills them in. Ten extra minutes per campaign puts you ahead of 99.88% of senders.

The email is the front door — check where it leads

Fixing your templates is the fast half of this job. The slow half is the destination: every link in an accessible email still lands on your product page, your booking form, your checkout. If those break under a screen reader, you’ve built a smooth on-ramp to a locked building — and the landing page, not the email, is what shows up in demand letters.

So pair the checklist above with a look at your site itself. Our free accessibility scan checks the pages your campaigns point to and shows you, in plain language, what a subscriber with a disability hits after the click.