Are You Using a Color Contrast Checker Too Late? Start Defining Contrast at the Palette

I recently finished a web app project that looked good at first glance. The layout was clean the palette was minimal and all the main components were in place. The mockups were approved quickly, and initial testing didn’t raise any major issues. Later, when I took a closer look at color contrast and accessibility I started noticing small problems. Some primary buttons didn’t stand out as much as they should. The text hierarchy wasn’t very easy to scan. A few CTAs technically worked, but they didn’t naturally pull attention. Nothing was broken, but the interface felt a bit harder to use than it needed to be. I adjusted the color palette improving contrast clearly defining primary and secondary colors and using color more intentionally to support hierarchy. I did not change the layout or structure at all. The difference was immediate. The interface felt clearer smoother and easier to understand. It was a good reminder that color isn’t just about making things look nice. It plays a big role in usability, accessibility, and how confident users feel when interacting with a product. Even a well-designed UI can feel heavy if color is NOT working properly. now I usually check color accessibility and experiment with palettes using tools like chromos or coolers to make sure nothing slips through. Interested how others handle this do you think about color roles early, or mostly at the final UI stage? submitted by /u/RecognitionBest8058 [link] [comments]

Source: https://www.reddit.com/r/userexperience/comments/1rcq5qe/are_you_using_a_color_contrast_checker_too_late/