WCAG Accessibility for Marketing Sites
Two business cases, one fix
The Web Content Accessibility Guidelines (WCAG) are usually framed purely as a legal-risk topic — avoiding lawsuits over inaccessible websites, which have become increasingly common in the US under disability-rights laws applied to digital properties. That framing undersells it for marketing sites specifically: a landing page that's hard to use with a screen reader, has poor color contrast, or requires precise mouse control to complete a form is also harder to use for a meaningful slice of the general visitor population — not just people who identify as having a disability, but also people on small screens, in bright sunlight, with a temporary injury, or simply in a hurry. Accessibility fixes on marketing pages tend to show up twice: once as reduced legal exposure, and again as a measurable bump in conversion rate, because many of the same changes that help assistive technology also reduce friction for everyone.
Accessibility issue vs. its conversion-rate side effect
| Accessibility issue | Who it blocks directly | Conversion-rate side effect for everyone |
|---|---|---|
| Low color contrast text | Low-vision users, screen glare situations | Harder to read for all users on mobile outdoors |
| No focus indicators | Keyboard-only users | No one can tell where they are mid-form |
| Missing form labels | Screen reader users | Confusing form fields for all users |
| Tiny tap targets | Motor-impairment users | Mis-taps and frustration on any mobile visitor |
| No alt text on key images | Screen reader and slow-connection users | Lost context if images fail to load |
| Autoplay video with sound | Cognitive/attention-sensitive users | Widely disliked by nearly all visitors |
What WCAG conformance levels actually mean
WCAG is organized into success criteria at three conformance levels — A (minimum), AA (the level most legal standards and policies reference as the practical target), and AAA (the highest, often not fully achievable for all content types without compromising design intent). When a marketing team hears "we need to be WCAG compliant," the practical target is almost always AA; AAA is typically reserved for specific high-stakes contexts and isn't a realistic blanket target for a full marketing site. Conformance is also evaluated per page, not per site as an abstract whole, which matters for a marketing team — a beautifully accessible homepage doesn't cover a campaign landing page built later by a different team on a different template.
High-impact, low-effort fixes for marketing pages (WCAG 2.1/2.2 AA):
[ ] Text contrast ratio >= 4.5:1 for normal text, 3:1 for large text
[ ] Every form input has a visible, associated <label>
[ ] All images carry meaningful alt text (empty alt="" for decorative)
[ ] Visible focus indicator on every interactive element (don't
strip default focus outlines without replacing them)
[ ] Tap targets sized for touch (roughly 44x44px minimum)
[ ] No content conveyed by color alone (e.g. red-only error states)
[ ] Headings in logical order (H1 > H2 > H3), not chosen by font size
[ ] Autoplay media muted by default, with an obvious pause control
[ ] Page usable and navigable with keyboard alone, no mouse
[ ] Animations respect prefers-reduced-motion where feasibleAccessibility overlay widgets are not a substitute for real fixes
Legal risk is real and has been rising
Website accessibility litigation in the US, generally brought under disability-rights law theories applied to digital properties, has increased substantially over the past several years, and marketing and ecommerce pages — being public-facing, high-traffic, and often built quickly for campaigns — are a frequent target. The specific legal standards, which laws apply, and what counts as sufficient conformance vary by jurisdiction and have been actively litigated and clarified over time; this is an area where the conceptual direction (WCAG AA as a practical benchmark, documented remediation effort as a risk-reduction signal) is more durable than any specific legal citation, and a team facing real exposure should get current counsel input rather than rely on general guidance like this module.
Where accessibility review typically happens vs. where it should
| Stage | Typical reality | Better practice |
|---|---|---|
| Design | Accessibility unconsidered until QA | Contrast/structure checked at design review |
| Build | Accessibility bolted on after launch complaint | Semantic markup and labels built in from the start |
| New campaign landing pages | Built from a template, assumed covered | Spot-checked per page, not assumed inherited |
| Third-party embeds (forms, widgets, chat) | Rarely audited for accessibility | Vendor accessibility checked before adoption |
Automated scanners catch a fraction of real issues
What's next
Accessibility and privacy compliance share a pattern: both are framed as legal obligations but pay off in trust and usability well beyond the legal floor. For how consent requirements intersect with the pages these fixes live on, see Cookie Consent Banner UX →, or revisit GDPR & CCPA Marketing Compliance for the broader regulatory landscape this track covers.
I build these systems professionally.
Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.