Accessible Color System with Universal Contrast Compliance
Color palette redesign ensuring WCAG AA/AAA contrast across all contexts, including dark mode and color blindness.
Create a color system that is accessible for all types of vision, maintaining brand visual identity and ensuring WCAG AA compliance across all text/background combinations.
At a glance
Access
Free prompt
Open to copy without upgrading.
Prompt objective
Create a color system that is accessible for all types of vision, maintaining brand visual identity and ensuring WCAG AA compliance across all text/background combinations.
Real use case
MegaLoja found that 23% of their e-commerce color combinations fail WCAG AA contrast testing, including promotional prices in orange on white backgrounds. With approximately 8% of the male population being colorblind, they need to redesign the palette without losing brand identity.
Customize these fields first
Replace the placeholders with your own context before you run the prompt. That usually improves the first output more than adding more instructions later.
Prompt
Redesign the color system for [PRODUCT NAME] to ensure WCAG AA compliance while maintaining brand visual identity with primary color [PRIMARY COLOR] and secondary color [SECONDARY COLOR].\\\\\\\\n\\\\\\\\nCurrent state: [NUMBER] contrast violations identified. Current colors: [LIST OF HEX COLORS].\\\\\\\\n\\\\\\\\n**1) Current Contrast Audit:**\\\\\\\\nFor each color pair used in the product:\\\\\\\\n- Text on background: current ratio vs. required (4.5:1 normal, 3:1 large)\\\\\\\\n- UI components on background: current ratio vs. required (3:1)\\\\\\\\n- Status: PASS/FAIL for AA and AAA\\\\\\\\n- Tools: Color Contrast Analyzer, Stark (Figma plugin)\\\\\\\\n\\\\\\\\n**2) Redesigned Palette:**\\\\\\\\nFor each brand color:\\\\\\\\n- Original value -> adjusted value (minimum change possible)\\\\\\\\n- Delta E (perceptual difference) between original and adjusted\\\\\\\\n- Approval: acceptable adjustment for brand team?\\\\\\\\n- Light/dark variations that maintain contrast\\\\\\\\n\\\\\\\\nFor semantic colors (success, error, warning, info):\\\\\\\\n- Values that pass contrast on white AND on dark\\\\\\\\n- Alternative that doesn't rely on color alone (icon, text, pattern)\\\\\\\\n\\\\\\\\n**3) Color Blindness Simulation:**\\\\\\\\nTest each critical combination in:\\\\\\\\n- Protanopia (no red perception)\\\\\\\\n- Deuteranopia (no green perception)\\\\\\\\n- Tritanopia (no blue perception)\\\\\\\\n- Achromatopsia (no color perception)\\\\\\\\n\\\\\\\\nFor each simulation:\\\\\\\\n- Color pair that becomes indistinguishable\\\\\\\\n- Solution: add non-chromatic differentiator (pattern, icon, label, border)\\\\\\\\n\\\\\\\\n**4) Usage Rules:**\\\\\\\\n- Allowed pairs (text/background) with documented ratio\\\\\\\\n- Forbidden pairs (never use together)\\\\\\\\n- Minimum text size per color pair\\\\\\\\n- When to use additional border for contrast guarantee\\\\\\\\n- Charts and data viz: alternative palette with hatch/pattern fills\\\\\\\\n\\\\\\\\n**5) Accessible Dark Mode:**\\\\\\\\n- Smart inversion: not simply inverting all colors\\\\\\\\n- Reduced saturation to reduce visual fatigue\\\\\\\\n- Text on dark background: white (87% opacity) for primary, 60% for secondary\\\\\\\\n- Accent colors: adjust lightness to maintain contrast in dark mode\\\\\\\\n\\\\\\\\n**6) High Contrast Mode:**\\\\\\\\n- Support for \\\\\\\\\\\\\\\\\\\\\\\`forced-colors\\\\\\\\\\\\\\\\\\\\\\\` / Windows High Contrast Mode\\\\\\\\n- Fallback to outline for elements relying on background color\\\\\\\\n- Test with browser in high contrast mode\\\\\\\\n\\\\\\\\n**7) Implementation and Validation:**\\\\\\\\n- CSS custom properties with fallbacks\\\\\\\\n- Automated tests: axe-core contrast checks in CI\\\\\\\\n- Design tokens updated with documented ratios\\\\\\\\n- Storybook addon-a11y: real-time preview\\\\\\\\n- Designer checklist before handoff\\\\\\\\n\\\\\\\\nRecommended tools: [Stark, Color Contrast Analyzer, axe DevTools, Colorblindly, Figma A11y plugin].
Open directly in an AI — the text is pre-filled:
How to use this prompt
- 1Replace the key placeholders first: PRODUCT NAME, PRIMARY COLOR, SECONDARY COLOR, NUMBER.
- 2Replace any bracketed placeholders like [this] with your own context.
- 3Add extra background information when you want more tailored results.
- 4Combine multiple prompts in one conversation when you need a richer output.
- 5Save your best-performing prompts so they are easy to reuse later.
Next best step
Open the guide first, then branch only if you still need more.
A starter guide to the first prompt categories and patterns worth using when you need better output without prompt guesswork.
If this prompt is close but not quite right, generate variants next. If the job is recurring, move into the course library after the guide.
Related prompts
View allComplete WCAG 2.2 Accessibility Audit for Digital Products
Audit checklist based on WCAG 2.2 Level AA criteria, adapted to Brazilian regulatory context (Lei Brasileira de Inclusão - LBI, Law 13.146/2015, which mandates digital accessibility for organizations serving Brazilian users).
Best for
Conduct a comprehensive accessibility audit that identifies WCAG 2.2 AA non-conformities and generates a prioritized remediation plan, with consideration for Brazilian accessibility law requirements.
Screen Reader Optimization with ARIA and Semantic HTML
Practical guide for implementing landmarks, live regions, and ARIA roles and properties to make rich interfaces accessible via screen readers.
Best for
Implement full screen reader support (NVDA, JAWS, VoiceOver, TalkBack) using semantic HTML as the foundation and ARIA as a supplement, following the rule 'no ARIA is better than bad ARIA'.
Full Keyboard Navigation for Single-Page Applications
Keyboard navigation implementation for SPAs with focus management, skip links, shortcuts, and assistive technology support.
Best for
Ensure the entire product is 100% operable via keyboard, serving users with motor disabilities, screen reader users, and power users who prefer keyboard shortcuts.
Advanced ARIA Patterns for Rich Custom Interface Components
Implementation of WAI-ARIA Authoring Practices for complex components: combobox, treegrid, date picker, drag-and-drop, and rich text editor.
Best for
Implement advanced ARIA patterns for rich interface components that lack native HTML equivalents, following WAI-ARIA Authoring Practices 1.2.
Explore other prompt categories
Move sideways into adjacent libraries when the current category is not the full answer.
Free browsing stays open. Premium prompts unlock the reusable workflow layer.
Use the guides and role paths to validate the job first. Upgrade when you want the full prompt text, editable premium prompts, and the surrounding course paths in one place.
Free access
- Browse guides, role paths, and category pages.
- Preview prompts before you decide to upgrade.
- Find the right starting point without friction.
Membership access
- Unlock premium prompts and the full copy text.
- See more workflow paths and course connections.
- Keep the reusable templates in one place.