ADA Risk on Campaign Microsites Built Outside the Main Theme

Sale microsites and campaign landing pages are often built fast on page builders outside the audited theme, and they inherit none of its fixes. Where the risk concentrates.

The main store gets the audit, the fixes, and the monitoring. Then a campaign team spins up a microsite for a sale or a product launch on a page builder, under a subdomain or a separate path, built in a week, and none of that work applies. New templates, new forms, new popups, none of it tested with a keyboard, all of it carrying the brands name and taking the brands money.

From a shoppers point of view there is no distinction to draw, and from a legal point of view there barely is either. A page the brand operates, links from its own channels, and sells through is the brands page. Title III risk does not stop at the edge of the main theme, even if the remediation programme does.

Why microsites start from zero

Page builders generate their own markup, and their defaults decide headings, buttons, forms, and modal behaviour until someone intervenes. A builder page commonly ships with skipped heading levels, unlabelled icon buttons, a newsletter modal that traps focus, and contrast chosen from a template palette. Each of those is a known, ordinary failure, arriving all at once on the pages a campaign is about to send its largest traffic to.

The microsite also tends to skip the unglamorous assets: no accessibility statement, no feedback route, sometimes not even the same privacy setup. If a shopper hits a barrier and looks for the statement the main site carries, the campaign site has nothing to show them. That absence reads badly in any later correspondence, because it did not have to be that way.

Bring microsites inside the same rules

The practical fix is a short gate, not a second programme. Any page that takes payment, captures personal data, or is linked from the main store goes through the same checks as a theme page before launch: keyboard pass, screen reader pass on the form, heading and label check, contrast check on campaign colours. An hour on a typical landing page, if the team doing it has done it before.

Where possible, build campaigns inside the main theme instead of beside it. A campaign section on audited templates inherits labelled components, working modals, and the statement and monitoring already in place. Page builders feel faster because the cost is deferred, and the deferred cost is paid by disabled shoppers first and by the brand later.

Track them, or they multiply

Keep a register of campaign sites and subdomains, with an owner and a retirement date. Microsites are rarely taken down. Last years sale page, still indexed, still carrying an old offer and an inaccessible form, is a common finding in audits and an embarrassing one, because nobody in the business believes the page still exists until someone shows them the traffic it still receives.

Retirement is part of accessibility work. A page nobody owns gets no fixes, no monitoring, and no updates when the platform changes. Closing a finished campaign site removes its risk entirely, which is more than can be said for most remediation.

Related reading

If this topic is useful, these earlier guides go deeper on connected questions: Testing Target Size: The Small Buttons That Block Mobile Checkout, ADA Risk in Accordion and FAQ Sections: Content Screen Readers Cannot Reach, and Testing Screen Reader Order on Product Bundles and Kits.

Frequently asked questions

Are campaign microsites covered by the same ADA expectations as the main store?

In practice yes. They are operated by the brand, linked from its channels, and used to sell. A shopper barrier there is the brands barrier, regardless of which tool built the page.

What fails most often on page builder landing pages?

Skipped heading levels, unlabelled buttons, focus trapping modals, low contrast campaign palettes, and forms with placeholder only labels. They are the builders defaults, shipped untested.

How can a small team control microsite risk?

Use a short launch gate: keyboard and screen reader passes, heading, label, and contrast checks, for any page that sells or captures data. Build campaigns inside the main theme where possible, and keep a register with owners and retirement dates.

Why retire old campaign sites?

Because unowned pages keep receiving traffic and keep carrying their barriers, with nobody responsible for fixing them. Closing a finished microsite removes that risk completely.