It happens on almost every project: the client has a strong opinion about a color choice that is either inaccessible, aesthetically problematic, or both. Saying "that is wrong" damages the relationship. Silently complying produces a bad result. The answer is redirection through demonstration.
Why Clients Push Bad Colors
Usually it is not stubbornness. Clients push colors for legitimate emotional reasons: "this yellow makes me happy," "my competitor uses this and they are successful," or "my daughter picked this color for our logo ten years ago." Dismissing the emotional connection is dismissing the client. Acknowledge it first.
Show, Do Not Tell
Words like "that fails accessibility" sound abstract. Showing the color applied to their actual site content makes the problem concrete. PaletteRx's Live Preview feature is designed for exactly this moment. Apply their requested color and let them see yellow text on white: "Can you read this paragraph comfortably?"
Offer Alternatives, Not Rejections
Instead of "we cannot use that yellow," try: "I love the energy of that yellow. Let me show you how it works as a highlight color on buttons and banners, where it really pops, while we use a darker tone for text so everything stays readable." You have preserved their color while redirecting its usage to where it actually works.
The Data Card
If showing does not work, the accessibility compliance angle provides objective ground. "WCAG requires a 4.5:1 contrast ratio for text. This yellow on white is 1.1:1. Using it for text could create legal liability. But here is where it shines..." PaletteRx's contrast numbers provide the objective evidence.
When to Compromise
Sometimes the client's color works in limited contexts. A bright yellow CTA button on a dark background is perfectly accessible and eye-catching. Finding the context where their preferred color excels turns a conflict into a win for everyone.