Accessibility Vendor & Compliance Hub Cohort (n=30)
Practice What You Preach: Auditing Accessibility Vendors & ADA Info Hubs Against WCAG 2.2 AA
Verdict
Even organizations dedicated to digital accessibility suffer regressions when marketing teams paste third-party scripts onto otherwise clean sites. Across our 30-site accessibility vendor and compliance hub cohort (representative specimen score: 86/100), core product documentation generally passed WCAG 2.2 AA, while 37% of tested marketing landing pages failed on third-party cookie consent banners, unlabeled "Work Email" newsletter bars, or low-contrast legal footnotes.
- Critical / serious
- 0 / 1
- Moderate / minor
- 0 / 0
- Keyboard
- Partial
- Overlay script
- None
axe-core rules triggered: color-contrast · Scanned
Key findings
- Core Docs vs. Marketing Scripts: Documentation subpages built in clean Markdown/HTML passed at 3x the rate of campaign landing pages carrying ad-tech and CRM embeds.
- Cookie Banner Traps: Third-party consent managers accounted for nearly half of all keyboard focus order and button-contrast defects in the cohort.
- Placeholder-Only Lead Bars: Embedded CRM forms frequently hid <label> elements visually via display: none instead of a screen-reader-accessible clip-path utility.
- Lesson for Every Team: Accessibility is a continuous CI and content discipline, never a one-time launch certificate.
Breakdown
| Page Surface | Pass Rate (0 axe AA Violations) | Most Frequent Defect |
|---|---|---|
| Technical Documentation Pages | 83% (25 of 30) | Occasional unlabelled scrollable <pre> code blocks |
| Homepage & Product Overview | 67% (20 of 30) | Third-party cookie consent modal contrast & focus order |
| Webinar / Demo Campaign Pages | 57% (17 of 30) | CRM embed inputs using placeholder without <label> |
Failing markup and the fix
<form class="demo-bar">
<input type="email" name="email" placeholder="Enter your work email*">
<span style="color:#94a3b8">By clicking Book Demo you consent to emails.</span>
<button type="submit">Book Demo</button>
</form><form class="demo-bar" action="/api/demo" method="post">
<label for="work-email">Work email</label>
<input id="work-email" name="email" type="email" autocomplete="email" aria-describedby="demo-consent" required>
<p id="demo-consent" class="consent-note">We reply once to schedule your walkthrough.</p>
<button type="submit">Book Walkthrough</button>
</form>What does this cohort teach engineering and marketing teams?
No team is immune to HTML drift. An engineering team can ship a 100/100 WCAG 2.2 AA site on Monday, and by Thursday a tag-manager snippet, webinar registration embed, or seasonal banner can introduce three serious axe-core violations.
The cure is running automated WCAG 2.2 AA checks in continuous integration on every pull request and scanning live production URLs on a recurring schedule.
Questions
Does ADA Site Review audit its own DOM with the exact same gate?
Yes. Every build of adasitereview.com runs Playwright + Deque axe-core across WCAG 2.0, 2.1, and 2.2 Level A & AA tags at 1440px, 390px, and 320px in both light and dark modes, failing the build on a single violation.
Has a vendor release fixed something above? Request a free re-test or read how we test.