Marketing and web-design agencies sit in the most exposed position in the entire accessibility-compliance landscape: they ship inaccessible websites to clients, the clients receive the demand letters, and the agencies are then named—or named-and-released—in the indemnification clauses of the resulting settlements. Agency liability has two distinct surfaces. The first is the agency's own site: a marketing agency that publishes case studies, client-portfolio galleries, lead-capture forms, gated content, podcasts, and webinars is itself a public accommodation under ADA Title III, is itself exposed to EAA enforcement when serving EU-based clients, and is itself the recipient of statutory-damages claims under the California Unruh Act. The second is the agency's deliverables: every site the agency builds carries an implicit warranty of merchantability under UCC Article 2A in most states; every Master Services Agreement signed since the 2024 DOJ Title II rule and the EAA's June 2025 effective date now contains accessibility-warranty and indemnification language, often with the agency on the giving end. Agencies also sit at the chokepoint of the most consequential accessibility-decision-making in the small-business economy: a single agency partner's decision to install an overlay widget instead of doing real remediation across forty client sites is a forty-defendant demand-letter campaign waiting to happen, and several plaintiffs' firms have built their intake pipelines explicitly around scraping the agency's case-study pages to identify defendants. This guide covers the dual-track legal exposure, the recurring failures specific to agency sites and agency deliverables, and a concrete compliance checklist that addresses both.

Legal Requirements

Key Accessibility Issues in Marketing & Web Design Agencies

Agency Case-Study Pages That Showcase Inaccessible Client Sites

The case-study page is the agency's primary lead-conversion tool—and is simultaneously the plaintiffs'-firm intake pipeline. Several active demand-letter operations explicitly scrape agency case-study pages to identify targets: the page lists the client name, the live URL, and a screenshot demonstrating that the agency built the inaccessible site. The case-study page therefore creates both direct evidence of the agency's involvement and a trivial one-click path from the agency's marketing to a defendant.

How to fix:

Audit every linked client site with an automated tool (axe DevTools, Lighthouse, WAVE) before publishing or refreshing a case study. If a client site fails, either (a) remediate the client site first, (b) remove the live link from the case study, or (c) link to an archived snapshot from the engagement period. Establish an internal sunset policy: client links older than 24 months should be re-audited or unlinked. The agency's own case-study page must itself meet WCAG 2.2 AA, including alt text on every screenshot, accessible video controls on every embedded reel, and proper heading structure.

Lead-Capture Forms, Gated Content, and Webinar Registration Built in HubSpot, Marketo, and Pardot

Marketing-automation platforms are notorious accessibility hotspots. The default HubSpot, Marketo, Pardot, ActiveCampaign, and Klaviyo embedded forms ship with inconsistent label behavior, custom-styled field components that fail keyboard navigation, modal-overlay form launches that trap focus, and progressive-profiling logic that re-renders the form mid-fill in ways that confuse screen readers. The agency's gated white-paper, webinar-registration, and demo-request pipeline is therefore systematically inaccessible to disabled prospects.

How to fix:

Replace the vendor's default form embed with a custom HTML form posting to the platform's API, where the agency controls labeling, focus management, and validation messaging. If platform-native forms must be used, override the styling with the platform's CSS-customization hooks to enforce visible focus indicators, persistent labels, and 4.5:1 contrast. Provide a plain email address as the documented alternative submission channel. Test the live form with NVDA, VoiceOver, and at 200% zoom.

Agency Deliverables Built Without an Accessibility Acceptance Test

The most common point of failure is structural: the agency's project-management workflow (Basecamp, Asana, ClickUp, Monday) has stages for design review, content review, QA, and client sign-off—but no stage for accessibility review. The site ships, the client signs off, and the demand letter arrives ninety days later. The agency's defense in the indemnification dispute—"the client signed off"—is rarely persuasive because the client lacked the expertise to evaluate accessibility. The absence of an internal acceptance test is the single largest controllable risk on the agency's balance sheet.

How to fix:

Add an explicit accessibility acceptance gate to the project-delivery workflow before client sign-off. At minimum: an automated axe DevTools or Lighthouse run with zero serious or critical violations; a manual keyboard-only walkthrough of the primary user journeys; a 200% zoom check; a screen-reader smoke test of the homepage and one transactional flow. Document the acceptance test in the deliverable package given to the client. For sites built into a regulated environment (government, healthcare, education, EU-targeted commerce), the gate should also include third-party VPAT preparation.

MSA and SOW Language That Pushes All Accessibility Risk to the Client

Agency MSAs frequently include a "client is solely responsible for compliance with all applicable laws" provision intended to shield the agency from accessibility liability. After the 2024 DOJ Title II rule, the EAA effective date, and recent state-court case law, this provision is rarely sufficient and is increasingly unenforceable when the client can show the agency made the design and implementation decisions that produced the failures. Worse, several recent MSAs reverse direction and place all warranty risk on the agency, often without the agency partner reading the modified language.

How to fix:

Have your MSA and SOW templates reviewed by counsel familiar with accessibility law (not generic tech-transactions counsel). Establish a clear allocation: the agency warrants conformance to a specified standard (typically WCAG 2.2 AA) at delivery; the client is responsible for ongoing conformance after the engagement ends. Cap indemnification exposure proportionally to the engagement value. Maintain accessibility errors-and-omissions insurance coverage. Read every client-supplied MSA before signing.

Agency-Standard Component Libraries and Theme Templates That Bake Inaccessibility Into Every Deliverable

Agencies commonly maintain a starter component library—a set of header, footer, hero, card, accordion, and form components reused across client engagements. When that library has accessibility defects—an accordion built with <div>s instead of buttons, a hero with insufficient contrast in the title overlay, a card with a non-keyboard-reachable hover state, a navigation menu that traps focus on mobile—every site the agency ships inherits the defect. A single library issue produces forty defendants.

How to fix:

Audit the agency's component library against WCAG 2.2 AA at least quarterly. Maintain an accessibility-component-library changelog visible to the entire delivery team. When a defect is discovered, push the fix into the library and update every active client engagement that uses the affected component. Document the library's accessibility posture publicly to demonstrate due diligence in the event of an indemnification claim.

Compliance Checklist

  • Agency website itself meets WCAG 2.2 AA — case studies, lead forms, gated content, webinars, podcasts all audited
  • Every linked client site on a case-study page has been re-audited within the past 12 months; failing sites are unlinked or remediated
  • Lead-capture and webinar-registration forms (HubSpot, Marketo, Pardot, etc.) have persistent labels, accessible validation, and a documented email alternative
  • Project-delivery workflow includes an explicit accessibility acceptance gate before client sign-off (automated scan + manual keyboard walkthrough + screen-reader smoke test)
  • MSA and SOW templates have been reviewed by counsel familiar with accessibility law since 2025; warranty and indemnification clauses are balanced and read before signing each engagement
  • Agency component library is audited against WCAG 2.2 AA at least quarterly and library-level fixes are propagated to active client engagements
  • Errors-and-omissions insurance covers accessibility-related indemnification claims; coverage limits match engagement-portfolio exposure
  • Delivery team has had documented accessibility training within the past 12 months
  • Color contrast on the agency site meets 4.5:1 for body text and 3:1 for UI components and large text
  • Accessibility statement is published with contact channel for accommodations, last review date, and the conformance commitment for the agency's own site

Further Reading

Other Industry Guides