BeginnerAccessibilityFree prompt

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 — no account or payment needed.

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

PRODUCT NAMEPRIMARY COLORSECONDARY COLORNUMBERLIST OF HEX COLORSStark, Color Contrast Analyzer, axe DevTools, Colorblindly, Figma A11y plugin

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].

Current state: [NUMBER] contrast violations identified. Current colors: [LIST OF HEX COLORS].

**1) Current Contrast Audit:**
For each color pair used in the product:
- Text on background: current ratio vs. required (4.5:1 normal, 3:1 large)
- UI components on background: current ratio vs. required (3:1)
- Status: PASS/FAIL for AA and AAA
- Tools: Color Contrast Analyzer, Stark (Figma plugin)

**2) Redesigned Palette:**
For each brand color:
- Original value -> adjusted value (minimum change possible)
- Delta E (perceptual difference) between original and adjusted
- Approval: acceptable adjustment for brand team?
- Light/dark variations that maintain contrast

For semantic colors (success, error, warning, info):
- Values that pass contrast on white AND on dark
- Alternative that doesn't rely on color alone (icon, text, pattern)

**3) Color Blindness Simulation:**
Test each critical combination in:
- Protanopia (no red perception)
- Deuteranopia (no green perception)
- Tritanopia (no blue perception)
- Achromatopsia (no color perception)

For each simulation:
- Color pair that becomes indistinguishable
- Solution: add non-chromatic differentiator (pattern, icon, label, border)

**4) Usage Rules:**
- Allowed pairs (text/background) with documented ratio
- Forbidden pairs (never use together)
- Minimum text size per color pair
- When to use additional border for contrast guarantee
- Charts and data viz: alternative palette with hatch/pattern fills

**5) Accessible Dark Mode:**
- Smart inversion: not simply inverting all colors
- Reduced saturation to reduce visual fatigue
- Text on dark background: white (87% opacity) for primary, 60% for secondary
- Accent colors: adjust lightness to maintain contrast in dark mode

**6) High Contrast Mode:**
- Support for `forced-colors` / Windows High Contrast Mode
- Fallback to outline for elements relying on background color
- Test with browser in high contrast mode

**7) Implementation and Validation:**
- CSS custom properties with fallbacks
- Automated tests: axe-core contrast checks in CI
- Design tokens updated with documented ratios
- Storybook addon-a11y: real-time preview
- Designer checklist before handoff

Recommended 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

  1. 1Replace the key placeholders first: PRODUCT NAME, PRIMARY COLOR, SECONDARY COLOR, NUMBER.
  2. 2Replace any bracketed placeholders like [this] with your own context.
  3. 3Add extra background information when you want more tailored results.
  4. 4Combine multiple prompts in one conversation when you need a richer output.
  5. 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 all

Complete 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).

IntermediateFree prompt

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.

Copy-ready promptOpen prompt

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.

AdvancedFree prompt

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'.

Copy-ready promptOpen prompt

Full Keyboard Navigation for Single-Page Applications

Keyboard navigation implementation for SPAs with focus management, skip links, shortcuts, and assistive technology support.

AdvancedFree prompt

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.

Copy-ready promptOpen prompt

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.

AdvancedFree prompt

Best for

Implement advanced ARIA patterns for rich interface components that lack native HTML equivalents, following WAI-ARIA Authoring Practices 1.2.

Copy-ready promptOpen prompt

Explore other prompt categories

Move sideways into adjacent libraries when the current category is not the full answer.

Every prompt here is free. The course teaches the thinking behind them.

Copy as many prompts as you like. When you want to move from single prompts to a repeatable AI workflow, Learn AI in 30 Days walks through it, one day at a time.

Get the courseSee the 30-day curriculum first

Buy the course once ($15/$20 by length), or go all-access for $10/mo with a verifiable certificate.