Building Color Palettes That Work in Low Light
Learn how to select accent colors and backgrounds that maintain readability with reduced eye strain during evening browsing sessions.
Read ArticleEverything you need to know about WCAG contrast requirements, why they matter more in dark mode, and tools to verify your colors meet standards.
Dark mode has become essential for modern web design. Users appreciate the reduced eye strain during evening browsing, and designers love the aesthetic possibilities. But here’s the thing — dark backgrounds introduce unique contrast challenges that aren’t always obvious.
When you’re designing for dark environments, the contrast requirements don’t change. WCAG standards remain the same. What changes is how you achieve them. Light text on dark backgrounds seems straightforward, but subtle color choices can make text unreadable for people with low vision or color blindness. We’ve seen countless dark mode implementations where the design looks great to the designer but fails accessibility tests completely.
WCAG (Web Content Accessibility Guidelines) defines specific contrast ratio requirements that apply regardless of whether you’re using light or dark mode. The standards are straightforward, but they’re often misunderstood.
Required for normal text and most content. This is the minimum you should aim for.
Recommended for body text, especially in dark mode where eye strain is a concern.
Text 18pt+ or 14pt+ bold can use lower ratios, but don’t push this in dark mode.
The ratio is calculated as: (L1 + 0.05) / (L2 + 0.05), where L1 and L2 are the relative luminance values. You don’t need to calculate this manually — tools handle it for you — but understanding the concept helps you make better color choices.
This article provides educational information about WCAG contrast standards and dark mode design principles. It’s not a substitute for professional accessibility consultation. Specific project requirements may vary based on your audience, jurisdiction, and regulatory requirements. For critical applications, we recommend working with accessibility specialists to ensure full compliance with relevant standards and guidelines.
Theory’s useful, but what really matters is applying these standards to actual interfaces. Dark mode requires a different approach than you might think.
Start with a background color around #0c0a09 to #1c1917. Too light and you lose the dark mode appeal. Too dark (pure black #000000) and you create contrast extremes that can cause eye strain.
Pure white (#ffffff) often creates too much contrast and can feel harsh. Slightly warmer whites like #fff7ed or #f1f5f9 maintain readability while reducing eye strain. Test with actual users when possible.
Accent colors in dark mode need special attention. A bright blue that works on light backgrounds might be too saturated on dark. Desaturate slightly and test the contrast ratio against your dark background.
You’ll need at least three text color levels: primary (high contrast), secondary (medium contrast), and muted (still above 3:1 but noticeably dimmer). This creates visual hierarchy without sacrificing accessibility.
You shouldn’t rely on visual judgment alone. These tools make testing quick and reliable.
The industry standard. Paste your hex colors and instantly see the contrast ratio and WCAG level. Simple, free, and trusted by accessibility professionals everywhere.
Best for: Quick validation of individual color pairs
Built-in contrast checking as you design. You’ll see accessibility issues in real-time across multiple screen sizes. It’s a bit of an investment but saves hours of manual testing.
Best for: Continuous development and design iteration
Right-click any element, inspect, and you’ll see contrast ratios calculated automatically. Often overlooked but incredibly useful when you’re actively building.
Best for: Testing during development
Desktop app that lets you sample colors directly from your screen. Perfect for testing live websites and design mockups without copying hex codes.
Best for: Testing live sites and screenshots
Contrast looks different depending on the device and viewing conditions. What you see on your monitor might not be what your users see.
Test your dark mode on actual devices in different lighting conditions. Check on phones in bright sunlight — this is where contrast problems become obvious. Test on older monitors that don’t have the same color accuracy. Ask colleagues with color blindness to review the interface. Don’t just rely on tools; use real people and real conditions.
For dark mode specifically, test in dim lighting. That’s when your users will be using it. A contrast ratio that passes automated tests might still cause discomfort in low light if the colors are too harsh or if there’s too much variation in brightness across the interface.
Dark mode isn’t just about aesthetics or energy savings — it’s about creating interfaces that work for everyone, in every lighting condition. When you get the contrast right, the dark mode becomes genuinely better to use, not just different.
Start with the WCAG standards, but don’t stop there. Use the tools to verify your choices, test with real devices, and most importantly, test with real people. The effort you put into getting contrast right will show in user satisfaction and accessibility compliance.
You’re building for Singapore’s diverse digital landscape. Some users will be browsing on older devices, others in bright sunlight, others late at night. Good contrast standards ensure everyone gets a quality experience, no matter where they are or what they’re using.