4.5:1 contrast
Contrast is the most boring accessibility requirement on paper and one of the most expensive ones in practice.
4.5:1 contrast mastery and why it keeps showing up in ADA website lawsuits
Contrast is the most boring accessibility requirement on paper and one of the most expensive ones in practice.
Every ADA website lawsuit in 2025 included contrast somewhere in the complaint. Sometimes it was central. Sometimes it was filler. Either way, it was there. Low contrast text. Faint placeholders. Disabled buttons that vanished into the background. Links that looked fine on a designer’s monitor and failed everywhere else.
The standard at the center of this mess is simple: 4.5:1.
That ratio has been around for years. It’s not new. It’s not obscure. And yet, it keeps breaking sites that otherwise look “clean” and score well on automated tools.
This article explains what 4.5:1 contrast actually requires, why teams keep getting it wrong, how courts and plaintiffs treat it, and why “fixing contrast” often turns into a larger design and engineering problem than anyone expects.
No polish. Just how it works.
Where 4.5:1 comes from and how it’s enforced
The contrast requirement comes from Web Content Accessibility Guidelines 2.1, Success Criterion 1.4.3, Contrast (Minimum).
The rule is narrow:
- Normal text must have a contrast ratio of at least 4.5:1 against its background
- Large text can drop to 3:1
- Decorative text and logos are exempt
That’s it.
Courts don’t debate the math. They debate whether text qualifies as “normal,” whether it’s essential, and whether users could reasonably read it.
The U.S. Department of Justice has repeatedly pointed to WCAG contrast criteria in settlement agreements and enforcement actions. Not as guidance. As expectation.
No federal statute says “4.5:1.” Judges still accept it.
Why contrast failures are so easy to sue over
Contrast violations are visible. They’re measurable. They don’t require complex user journeys to demonstrate.
A plaintiff tester can load a page, sample colors, and document failure in minutes. No scripting. No speculation. Just screenshots and ratios.
That’s why contrast shows up even when it didn’t block the user completely. It’s a clean allegation that courts understand.
Defense attorneys know this. Many settlements quietly include contrast remediation even when the core dispute was something else.
Contrast ratio is calculated using relative luminance, not visual brightness. Two colors that look “far apart” to a designer can still fail.
Light gray text on white fails almost every time.
Muted brand palettes fail constantly.
Disabled states fail more than active states.
Placeholder text fails so often that some auditors assume it’s broken unless proven otherwise.
None of this is subjective. The formula is published. The tools are free.
Teams still rely on eyeballing.
A real example from a retail site audit
In February 2025, a regional home goods retailer underwent an accessibility audit after receiving a demand letter. The design team insisted contrast was “fine.”
The audit found:
- Body text at 3.8:1
- Form placeholders at 2.2:1
- Disabled buttons at 1.9:1
The text was readable to most users in ideal conditions. It still failed WCAG.
The site settled a lawsuit three weeks later. Contrast fixes were item one on the remediation list.
Why 4.5:1 breaks modern design systems
Modern design systems favor subtlety. Soft neutrals. Thin fonts. Low visual noise.
4.5:1 doesn’t care.
Thin fonts don’t get a pass. Light weights don’t count as “large text.” Aesthetics don’t change the math.
Design systems built without contrast baked in end up requiring exceptions everywhere. Overrides pile up. Consistency breaks.
That’s when teams start making trade-offs they didn’t plan for.
The trade-off nobody advertises
Raising contrast often changes brand perception.
Marketing teams notice. Executives notice. The site looks heavier. Louder. Less refined.
Accessibility teams push back. Legal teams get nervous. Design gets squeezed.
Some companies accept the change. Others try to thread the needle with micro-adjustments that barely pass.
That second group shows up in lawsuits more often.
Why “large text” exemptions don’t save most sites
WCAG allows 3:1 contrast for large text. Designers lean on that.
The problem is the definition.
Large text means:
- 18pt (24px) regular weight, or
- 14pt (18.66px) bold
Most body copy doesn’t qualify. Most navigation doesn’t qualify. Most form labels don’t qualify.
Auditors check computed values, not design specs. If it doesn’t meet the threshold in the browser, it fails.
Contrast failures love dynamic states
Static pages are the easy part.
Contrast breaks during:
- Hover states
- Focus states
- Disabled states
- Error messages
- Success confirmations
Buttons that pass in default state fail on hover. Error text fails against tinted backgrounds. Focus outlines disappear entirely.
Automated tools catch some of this. Manual testing catches more.
Plaintiffs cite whichever is easiest to explain.
A lawsuit example centered on contrast
In August 2025, a California-based fitness studio chain was sued under the ADA. The site’s main issue wasn’t navigation or forms. It was contrast.
Class schedules used light gray text on a white background. The contrast ratio averaged 3.6:1.
The plaintiff alleged inability to read schedules using a screen magnifier. The complaint included color samples and ratios.
The studio settled for $8,500. The only required fix was contrast.
Why contrast issues cluster with font choices
Design teams often pair low contrast with:
- Thin font weights
- Small font sizes
- Tight letter spacing
Each choice compounds the problem.
WCAG evaluates contrast independently, but users experience all of it together. Courts are sympathetic to that reality.
Even if text technically passes 4.5:1, poor typography can still support a broader accessibility claim when combined with other issues.
Automated tools and the false sense of security
Tools like Lighthouse flag contrast issues. They don’t catch everything.
They miss:
- Text over gradients
- Text over images
- Text injected dynamically
- Canvas-rendered text
A page can score 100 and still fail contrast in real use.
Defense attorneys have stopped leaning on automated contrast reports. Plaintiffs don’t care.
How designers try to game the ratio
Some teams tweak colors just enough to pass on paper.
They darken text slightly. They lighten backgrounds slightly. They run the numbers and stop.
That works until:
- Brand colors change
- Background images load differently
- User styles override defaults
Contrast regressions are common. They’re rarely monitored.
Plaintiffs test live pages, not design files.
Contrast and color blindness don’t overlap neatly
Contrast is about luminance, not hue. Color blindness is about hue discrimination.
Teams often conflate the two.
A color combination can pass contrast and still be confusing for color-blind users. The reverse is also true.
ADA lawsuits usually focus on contrast because it’s easier to prove. That doesn’t mean other issues don’t exist.
Government sites and the stricter lens
State and local government sites face even more pressure due to DOJ enforcement under Title II.
Many agencies failed contrast checks in 2024 and 2025 during remediation efforts.
Public-facing PDFs were especially bad. Light gray text, scanned documents, poor tagging.
Government settlements reinforced the message. 4.5:1 applies everywhere text conveys meaning.
A municipal example that shows the cost
A mid-sized city in the Midwest rebuilt its website in 2024. Brand colors were approved. The site launched.
In 2025, an accessibility review found contrast failures across headings, buttons, and alerts. Fixing them required revisiting the entire color system.
The redesign cost $180,000. The remediation cost another $60,000.
Contrast was the driver.
Why contrast fixes often ripple outward
Changing text color affects:
- Icons
- Borders
- Focus outlines
- Charts
- Data tables
Teams underestimate the scope. One fix reveals ten more.
That’s why contrast remediation often stalls or ships half-done. And half-done fixes still get cited in complaints.
How plaintiff firms document contrast failures
Plaintiff firms use the same tools auditors do.
They sample colors. They capture ratios. They annotate screenshots.
The language in complaints is straightforward:
“Text displayed in light gray (#B3B3B3) on a white background (#FFFFFF) has a contrast ratio of 2.1:1, below the required 4.5:1.”
Judges understand that sentence. They don’t need more.
Defense arguments that don’t work anymore
Defendants used to argue that text was “readable enough.”
Courts stopped entertaining that years ago.
If it fails WCAG, it fails. Subjective readability arguments rarely survive motions.
The only defenses that sometimes land involve misclassification of text as essential versus decorative. Even those are narrow.
Why logos and branding don’t get you out of it
WCAG exempts logos from contrast requirements. That exemption is limited.
If logo text conveys critical information, courts may still scrutinize surrounding context.
More importantly, most contrast failures aren’t logos. They’re buttons, links, labels, and instructions.
Brand arguments don’t apply.
How contrast affects real users, not just lawsuits
Low contrast doesn’t just affect blind users.
It affects:
- Older users
- Users with low vision
- Users in bright environments
- Users on low-quality displays
Courts don’t require proof of widespread harm. One affected user is enough.
Why contrast mastery is harder than it sounds
“Just meet 4.5:1” sounds simple.
In practice, it requires:
- Design systems built with contrast from the start
- Tokens and variables that enforce ratios
- Testing beyond static mocks
- Ongoing monitoring
Most sites don’t have that discipline. They patch.
Patches break.
A final example that ties it together
In late 2025, a national service company received a demand letter citing contrast failures. The design team insisted fixes were done months earlier.
An audit showed that a recent content update reintroduced low contrast text inside a CMS component.
No one noticed.
The lawsuit didn’t care about intent. It cared about what users saw.
Where 4.5:1 contrast mastery actually stands
4.5:1 isn’t a design preference. It’s a line courts accept.
Teams that treat it as a checkbox chase it forever. Teams that build around it fight fewer fires.
Contrast failures remain one of the easiest ADA claims to file and one of the hardest to eliminate permanently.
Not because the rule is complex.
Because discipline is.