CTA buttons have sufficient visual contrast
Why it matters
A CTA button that fails WCAG 2.2 SC 1.4.11 (Non-text Contrast, 3:1 minimum against adjacent background) and SC 1.4.3 (Text Contrast, 4.5:1 minimum for normal text) is invisible to users with low vision — and to many typical users on bright screens or in direct sunlight. Beyond accessibility compliance, contrast failure directly suppresses conversion: if the primary action doesn't visually demand attention, visitors scan past it. A low-contrast CTA is the single cheapest conversion kill in a marketing page.
Severity rationale
High because a CTA that fails to register visually eliminates the conversion path for a measurable fraction of visitors, including users with visual impairments covered by WCAG 2.2.
Remediation
Replace the low-contrast color combination with a brand color that achieves at least 3:1 button-to-background contrast and 4.5:1 text-to-button contrast. In Tailwind, indigo-600 on white clears both thresholds:
<Button className="bg-indigo-600 text-white hover:bg-indigo-700 focus-visible:ring-2 focus-visible:ring-indigo-500">
Get Started
</Button>
Verify contrast ratios with the WebAIM contrast checker before shipping. If your hero section uses a background image or gradient, test the button against both the lightest and darkest regions of that background.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Conversion Optimization Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- wcag:2.2 · 1.4.3 — Contrast (Minimum)
- wcag:2.2 · 1.4.11 — Non-text Contrast
Taxons
History
- 2026-04-18·v1.0.0·Initial import from marketing-conversion·automated