Design color palettes that are accessible to all users including those with color blindness. Ensure sufficient contrast, meaningful use of color, and inclusive design.
Accessible color design ensures all users, including those with color vision deficiency, can access and understand information.
Minimal working example:
WCAG Contrast Ratios:
WCAG AA (Minimum):
- Normal text: 4.5:1
- Large text (18pt+): 3:1
- UI components & graphical elements: 3:1
- Focus indicators: 3:1
WCAG AAA (Enhanced):
- Normal text: 7:1
- Large text: 4.5:1
- Better for accessibility
---
Testing Contrast:
Tools:
- WebAIM Contrast Checker
- Color Contrast Analyzer
- Figma plugins
- Browser DevTools
Formula (WCAG): Contrast = (L1 + 0.05) / (L2 + 0.05)
Where L = relative luminance
// ... (see reference guides for full implementation)
Detailed implementations in the references/ directory:
| Guide | Contents | |---|---| | Color Contrast Standards | Color Contrast Standards | | Color Vision Deficiency Simulation | Color Vision Deficiency Simulation | | Accessible Color Usage | Accessible Color Usage | | Testing & Validation | Testing & Validation |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/color-accessibility · pinned to the source commit
git clone https://github.com/aj-geddes/useful-ai-prompts.git
cd useful-ai-prompts
git checkout 3f5182cfd739fc113f4af5244a1cf342ad7f7911
mkdir -p ".claude/skills/color-accessibility"
cp -r "skills/color-accessibility" ".claude/skills/color-accessibility"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 3f5182cfd739. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.