The ADA Risk Hiding in Your Marketing Emails and Texts

Stores audit their storefront and forget their campaigns. Image only emails, inaccessible landing pages, and text programs carry their own exposure.

Accessibility work concentrates on the storefront, and understandably so: that is where shoppers buy. But the campaigns that bring shoppers there are part of the customer experience too, and they are built by different people, in different tools, with none of the storefront's checks. Image only emails, campaign landing pages thrown up in a builder, and SMS programs with web based terms all carry exposure most stores have never assessed.

This is not a call to audit every send like a product launch. It is a map of where campaign accessibility actually fails, and the proportionate checks that fit a marketing team's pace.

Image only emails are the classic failure

The promotional email built as one large image, or a stack of image slices, still exists because it guarantees the design renders exactly as approved. For a recipient using a screen reader, or anyone with images blocked, that email is a blank page with a link. Every word of the offer, including its terms, lives inside pixels. The fix is unglamorous: real text for the offer and the terms, images marked up with genuine alt text, and image off reading as a standard QA step.

The same pattern repeats in the details: buttons built as images with no accessible name, contrast chosen from a brand palette without a check, and reading order that follows the visual layout rather than the message. None of these require a redesign. They require the email tool and the QA checklist to treat accessibility as part of 'does this send work', the same as links and rendering.

Campaign landing pages escape the storefront process

The storefront went through remediation, templates were fixed, and the team learned the checks. Then marketing spins up a campaign page in a page builder for a weekend promotion, and none of that applies: fresh templates, unreviewed apps, a countdown widget, a form. These pages are public, indexed, promoted to the whole list, and built entirely outside the process that made the main site safer.

The proportionate control is a template, not a review board. Give campaigns an approved accessible page template with the storefront's patterns built in, and require anything custom to pass the same short checklist as a theme change. Marketers keep their speed. The store stops shipping unaudited public pages under its own domain every time a promotion launches.

SMS programs and their web edges

Text messages themselves are plain and largely accessible by nature. The edges are where problems live: sign up flows in popups that a keyboard cannot complete, terms pages published as image based PDFs, short link destinations that land on inaccessible campaign pages, and preference centers built as an afterthought. A shopper who cannot manage their messaging preferences has an accessibility problem and, often, a compliance one too.

Include the messaging program in the accessibility inventory the way you include apps: named owner, surfaces listed, checked when vendors or templates change. Programs that live entirely in a vendor's tool still live under your brand, and complaints will arrive addressed to you.

Build the lightweight campaign checklist

Five checks fit a marketing workflow without slowing it. Real text for offers and terms in every email. Alt text that says something. Contrast checked on the campaign palette once, then reused. Landing pages built on the approved template or passed through the storefront checklist. Image off and keyboard only passes on the final send, done by the person building it, in the tool they already use.

Document that the checklist exists and is used. As with the storefront, the record of a working process matters: it shows the campaigns were part of the program, not a forgotten annex. When a complaint does mention a campaign, a store that can show its checks is in a different conversation from one discovering its emails are images.

Related reading

If this topic is useful, these earlier guides go deeper on connected questions: What an ADA Settlement Usually Requires: Timelines, Monitoring, and Reporting, ADA Risk in Marketplace and Third-Party Seller Pages You Do Not Control, and A Second Demand Letter After You Fixed the First: Why It Happens and What It Means.

Frequently asked questions

Do marketing emails really need to be accessible?

Yes. They are part of how customers shop with you, and an image only email is unreadable to screen reader users and to anyone with images off. The fixes are modest: real text for offers and terms, meaningful alt text, checked contrast, and an image off QA pass before sending.

What is the biggest campaign accessibility risk?

The landing page built outside the storefront process. Campaign pages in builders bypass every check the main site went through while being public and heavily promoted. An approved accessible template for campaigns closes most of the risk without slowing launches.

Are SMS programs an accessibility concern?

The texts themselves are plain, but the surrounding surfaces are not: popup sign up flows, image based terms pages, short link destinations, and preference centers. Those edges belong in the accessibility inventory with a named owner, checked when templates or vendors change.

How do we check campaigns without slowing marketing down?

A five item checklist used by the builder: real text, real alt text, known good contrast, approved landing template, and an image off plus keyboard pass on the final send. It adds minutes per campaign and produces the record that campaigns were inside the program.