Designing for Colorblindness: Complete Accessibility Guide
Learn to design accessible websites for 300 million colorblind users worldwide. Includes safe color palettes, WCAG guidelines, and testing strategies.

Designing for Colorblindness: Complete Accessibility Guide
Approximately 300 million people worldwide experience some form of color blindness. That's roughly 8% of men and 0.5% of women—likely a significant portion of your users. Designing accessible interfaces isn't just ethical; it's good business. Let's ensure your designs work for everyone.
Understanding Color Blindness
What is Color Blindness?
Color blindness (color vision deficiency) is the decreased ability to see color or perceive color differences. Most color-blind individuals aren't completely blind to color—they struggle to distinguish between specific hues.
Types of Color Blindness
Red-Green Color Blindness (Most Common - 99% of cases):
Deuteranomaly (6% of males):
- Reduced sensitivity to green light
- Green appears more red
- Most common type overall
Protanomaly (1% of males):
- Reduced sensitivity to red light
- Red appears more green and less bright
Deuteranopia (1% of males):
- No green cones
- Can't distinguish red from green
Protanopia (1% of males):
- No red cones
- Can't distinguish red from green
- Red appears darker
Blue-Yellow Color Blindness (Rare):
Tritanomaly (0.01% of people):
- Reduced blue and yellow sensitivity
- Difficulty distinguishing blue from green
Tritanopia (0.001% of people):
- No blue cones
- Blue appears green, yellow appears pink
Complete Color Blindness (Extremely Rare):
Achromatopsia (<0.001%):
- Complete inability to see color
- Sees only shades of gray
- Often accompanied by light sensitivity
The Problem: Color-Only Design
Common Failures
Error Messages:
❌ Red text with no icon: "Invalid email"
✅ Red text + X icon: "❌ Invalid email"
Form Validation:
❌ Green/red borders only
✅ Green checkmark/red X + color
Charts and Graphs:
❌ Color-coded only (red vs green lines)
✅ Different line styles + color (solid, dashed, dotted)
Status Indicators:
❌ Green = online, Red = offline (color only)
✅ Green dot + "Online" label, Gray dot + "Offline" label
Links in Text:
❌ Blue text only (no underline)
✅ Blue + underlined, or bold + underline
WCAG Guidelines for Color
Criterion 1.4.1: Use of Color (Level A)
Requirement: Color is not the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Examples:
- Passes: Required fields have red asterisk + "required" label + bold text
- Passes: Graph with different line patterns + labels + colors
Criterion 1.4.3: Contrast Minimum (Level AA)
Requirement:
- Normal text: 4.5:1 contrast ratio
- Large text (18pt+ or 14pt+ bold): 3:1 contrast ratio
- UI components and graphics: 3:1 contrast ratio
Test all your color combinations with our Contrast Checker.
Problematic Color Combinations
Avoid These Pairs for Colorblind Users
Red & Green (The Worst Offender):
- Invisible to most colorblind people
- Never use for success/error states alone
- Example issue: Traffic lights (solved with position + shape)
Green & Brown:
- Appear similar to red-green colorblind users
- Common in nature-themed designs
Green & Gray:
- Hard to distinguish for deuteranomaly
- Common in inactive/active states
Blue & Purple:
- Confusing for some types
- Less problematic than red/green
Light Green & Yellow:
- Look almost identical to many colorblind users
- Common in "mild warning" designs
Green & Blue:
- Can appear similar, especially lighter shades
- Test with simulators
Blue & Gray:
- Low contrast issue for some
- Ensure sufficient brightness difference
Colorblind-Friendly Color Palettes
Safe Color Combinations
High Contrast Pair 1: Maximum distinction
- Black: #000000
- Orange: #FF8800
High Contrast Pair 2: Colorblind-safe complementary
- Blue: #0066CC
- Orange: #FF8800
High Contrast Pair 3: High contrast, distinguishable
- Purple: #663399
- Yellow: #FFCC00
High Contrast Pair 4: Classic safe pair
- Navy: #000080
- Yellow: #FFDD00
Three-Color Palette 1: Safe triadic
- Blue: #0077BB
- Orange: #EE7733
- Gray: #CCCCCC
Three-Color Palette 2: Works for most
- Purple: #AA3377
- Green: #228833
- Gray: #AAAAAA
Three-Color Palette 3: Distinctive
- Teal: #009988
- Gold: #DDAA33
- Pink: #CC3377
Four-Color Palette 1:
- Navy: #000080
- Orange: #FF8800
- Teal: #008080
- Gray: #808080
Four-Color Palette 2:
- Blue: #0066CC
- Vermillion: #D55E00
- Purple: #6600CC
- Green: #009E73
Test these with our Color Palette Generator to create variations.
IBM Design Color Palette
IBM created a research-backed accessible color palette:
- Blue: #0F62FE
- Cyan: #1192E8
- Teal: #009D9A
- Green: #198038
- Magenta: #D12771
- Purple: #8A3FFC
- Orange: #FF832B
- Gold: #FFB000
These were specifically tested for color vision deficiency.
Design Strategies for Accessibility
1. Use Patterns and Textures
In Charts:
- Solid fill + dots + stripes + crosshatch
- Each data series gets unique pattern + color
- Ensure patterns are distinct at small sizes
Example:
Revenue: Solid blue fill
Expenses: Diagonal stripe pattern
Profit: Dotted pattern
2. Add Text Labels
Always include:
- Labels on chart elements
- Percentages in pie charts
- Values on data points
- Legend with text, not just color
Before: ![Pie chart with colored sections only]
After: ![Pie chart with colors + labels + percentages]
3. Use Icons and Symbols
Status Indicators:
- ✅ Success: Green + checkmark icon
- ⚠️ Warning: Yellow + warning triangle
- ❌ Error: Red + X mark
- ℹ️ Info: Blue + info circle
Form States:
- Valid: Green border + ✓ icon
- Invalid: Red border + ✗ icon
- Required: Asterisk + "required" text
4. Provide Multiple Visual Cues
Link Styling:
- Color (blue)
- Underline
- Bold weight
- Icon (external link →)
Button States:
- Active: Darker + raised shadow
- Hover: Lighter + border
- Disabled: Gray + cursor change + "disabled" text
5. Position and Shape
Traffic Light Pattern:
- Top = Stop (red)
- Middle = Caution (yellow)
- Bottom = Go (green)
Position provides meaning when color fails.
Shape Coding:
- Circles for success
- Triangles for warnings
- Squares for errors
- Hexagons for info
6. Border Weights and Styles
Different states:
- Normal: 1px solid
- Hover: 2px solid
- Active: 3px solid
- Error: 2px dashed
- Success: 2px double
Testing Your Designs
Color Blindness Simulators
Browser Extensions:
- Colorblindly (Chrome/Edge): Real-time simulation
- Let's Get Color Blind (Firefox): Multiple types
- Color Oracle (Desktop app): Cross-platform
Online Tools:
- Coblis Color Blindness Simulator: Upload images
- Toptal Color Blind Filter: Real-time website testing
- Chromatic Vision Simulator: Scientific accuracy
Testing Workflow
- Design normally with your chosen colors
- Test with protanopia simulator (no red cones)
- Test with deuteranopia simulator (no green cones)
- Test with tritanopia simulator (no blue cones)
- Test with monochrome filter (grayscale)
- Verify with real users if possible
If your design works in all simulations, it's accessible.
Automated Accessibility Testing
Tools:
- axe DevTools: Browser extension for WCAG testing
- WAVE: Web accessibility evaluation tool
- Lighthouse: Built into Chrome DevTools
- Our Contrast Checker: Verify color combinations
Real-World Examples
Success Story: Trello
Old Design:
- Color-coded labels only
- Green/yellow/orange/red
- Colorblind users couldn't distinguish
New Design:
- Color + text labels on cards
- Optional colorblind-friendly mode
- Patterns available for labels
Result: Accessible to all users while maintaining visual design.
Success Story: GitHub
Implementation:
- Contribution graph: Green shades + tooltips with exact numbers
- PR status: Icons + color (merged, open, closed)
- Code diff: +/- symbols + green/red backgrounds
Why it works: Never relies on color alone.
Success Story: Tableau
Features:
- Built-in colorblind-safe palettes
- Automatic pattern fills option
- Text labels for all data
- Customizable color schemes
Result: Data visualization accessible to everyone.
Creating a Colorblind-Friendly Design System
Step 1: Choose Base Colors
Select colors that are distinguishable:
- Primary: Blue (#0066CC)
- Secondary: Orange (#FF8800)
- Success: Teal (#008080)
- Warning: Gold (#FFD700)
- Error: Vermillion (#D55E00)
- Info: Purple (#8800CC)
Test with protanopia/deuteranopia simulators.
Step 2: Define Semantic Meanings
Don't rely on color names:
❌ "Use red for errors"
✅ "Use error color (currently red) + error icon + error text"
Step 3: Create Pattern Library
For charts and data:
- 6+ distinct fill patterns
- Works with or without color
- Testable in grayscale
Step 4: Document Alternatives
For every color-coded element, specify:
- Icon alternative
- Text alternative
- Pattern alternative
- Position alternative
Step 5: Test and Iterate
- Test with real colorblind users
- Use simulation tools
- Validate WCAG compliance
- Update based on feedback
Common Questions
"Can I still use red and green?"
Yes, but never alone. Red and green are fine if combined with:
- Icons (checkmark, X)
- Text labels
- Different positions
- Patterns or textures
"Do I need to avoid all color?"
No! Color enhances design. Just ensure it's not the only indicator. Always provide non-color alternatives.
"What about brand colors?"
Keep your brand colors—just supplement them:
- Brand red for logo: Fine
- Brand red for "error" with no other indicator: Not accessible
- Brand red for "error" + error icon + text: Perfectly fine
"How do I make colorful charts accessible?"
- Add data labels to all points
- Use distinct line styles (solid, dashed, dotted)
- Include patterns in bar fills
- Provide data table alternative
- Use accessible color combinations
Checklist for Colorblind Accessibility
- Links are underlined or have non-color indicators
- Form errors include icons and text, not just red borders
- Success states use checkmarks, not just green
- Charts have labels and legends with text
- Important information has 2+ visual indicators
- UI states vary in more than color (size, position, text)
- All text meets WCAG contrast ratios (test with Contrast Checker)
- Color combinations avoid problematic pairs (red/green, blue/purple)
- Design tested with colorblindness simulators
- Graphs use patterns or textures in addition to color
- Navigation doesn't rely on color alone
- Status indicators include text or icons
Conclusion
Designing for color blindness isn't about removing color—it's about ensuring color isn't the only way to convey information. By adding icons, labels, patterns, and other visual cues, you create designs that:
- Work for 300 million colorblind users
- Improve clarity for everyone
- Meet WCAG accessibility standards
- Demonstrate inclusive design practices
The Golden Rule: If your design works in grayscale, it works for colorblind users.
Ready to create accessible color schemes? Use our tools:
- Color Palette Generator - Generate colorblind-safe palettes
- Contrast Checker - Verify WCAG compliance
- Color Converter - Work with accessible color formats
Related Articles
Design accessible, inclusive experiences with MyPaletteTool's free color accessibility tools.