Text and UI components have sufficient color contrast
Why it matters
Low-contrast text is the most common WCAG failure and directly excludes users with low vision, color blindness, or anyone reading in suboptimal lighting conditions. WCAG 2.2 SC 1.4.3 requires a 4.5:1 ratio for normal text and 3:1 for large text at Level AA; SC 1.4.11 extends the same 3:1 requirement to non-text UI components. Failing this standard exposes SaaS products to ADA Title III litigation, which is disproportionately targeted at e-commerce and fintech.
Severity rationale
Critical because contrast failures exclude real users from reading content at all — not a minor UX friction but a hard functional barrier that violates WCAG 2.2 SC 1.4.3 at Level AA.
Remediation
Measure every text/background color pair in your CSS, Tailwind config, and component styles. Replace any combination that fails the 4.5:1 threshold for normal text or 3:1 for large text.
/* Before — fails at 2.85:1 on white */
.helper-text { color: #999999; }
/* After — passes AA at 4.62:1 on white */
.helper-text { color: #707070; }
For Tailwind projects, audit your tailwind.config.ts theme extension. Use the WebAIM Contrast Checker or Chrome DevTools Accessibility panel to measure computed values. When colors are defined as CSS custom properties that cannot be statically resolved, add a comment directing manual verification rather than assuming compliance.
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 Accessibility WCAG Compliance 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
- section-508:2018-refresh · 302.5 — Without Visual
Taxons
History
- 2026-04-18·v1.0.0·Initial import from accessibility-wcag·automated