function normalizeChannel(value: number): number {
  const normalized = value / 255;
  return normalized <= 0.03928
    ? normalized / 12.92
    : Math.pow((normalized + 0.055) / 1.055, 2.4);
}

function calculateLuminance(r: number, g: number, b: number): number {
  const rLinear = normalizeChannel(r);
  const gLinear = normalizeChannel(g);
  const bLinear = normalizeChannel(b);
  return 0.2126 * rLinear + 0.7152 * gLinear + 0.0722 * bLinear;
}

type WCAGLevel = 'AA' | 'AAA';
type TextSize = 'normal' | 'large';

interface ContrastResult {
  ratio: number;
  passesAA: boolean;
  passesAAA: boolean;
  recommendedAdjustment: string;
}

export function evaluateContrast(
  foregroundHex: string,
  backgroundHex: string,
  textSize: TextSize = 'normal'
): ContrastResult {
  const fg = hexToRgb(foregroundHex);
  const bg = hexToRgb(backgroundHex);
  
  const l1 = Math.max(calculateLuminance(...fg), calculateLuminance(...bg));
  const l2 = Math.min(calculateLuminance(...fg), calculateLuminance(...bg));
  
  const ratio = (l1 + 0.05) / (l2 + 0.05);
  
  const aaThreshold = textSize === 'large' ? 3.0 : 4.5;
  const aaaThreshold = textSize === 'large' ? 4.5 : 7.0;
  
  return {
    ratio: Number(ratio.toFixed(2)),
    passesAA: ratio >= aaThreshold,
    passesAAA: ratio >= aaaThreshold,
    recommendedAdjustment: ratio < aaThreshold 
      ? `Increase contrast by darkening foreground or lightening background to reach ${aaThreshold}:1`
      : 'Compliant'
  };
}

function hexToRgb(hex: string): [number, number, number] {
  const sanitized = hex.replac

e('#', ''); const bigint = parseInt(sanitized, 16); return [(bigint >> 16) & 255, (bigint >> 8) & 255, bigint & 255]; }

### Step 3: Build-Time Token Validation

The architectural rationale for build-time validation is straightforward: runtime checks introduce bundle bloat and cannot catch design-time decisions. By integrating the contrast engine into a token compilation step, teams enforce constraints before CSS generation.

```typescript
// token-validator.config.ts
import { evaluateContrast } from './contrast-engine';

const designTokens = {
  palette: {
    primary: '#2563EB',
    surface: '#FFFFFF',
    textMuted: '#767676',
    textBody: '#1F2937',
  },
  components: {
    button: {
      fg: '#FFFFFF',
      bg: '#2563EB',
      size: 'normal' as const,
    },
    caption: {
      fg: '#767676',
      bg: '#FFFFFF',
      size: 'normal' as const,
    }
  }
};

export function validateTokenSet(tokens: typeof designTokens): void {
  const violations: string[] = [];
  
  for (const [key, component] of Object.entries(tokens.components)) {
    const result = evaluateContrast(component.fg, component.bg, component.size);
    if (!result.passesAA) {
      violations.push(`❌ ${key}: ${result.ratio}:1 fails AA (${result.recommendedAdjustment})`);
    }
  }
  
  if (violations.length > 0) {
    console.error('Token validation failed:\n' + violations.join('\n'));
    process.exit(1);
  }
  
  console.log('✅ All contrast tokens meet WCAG AA thresholds');
}

Architecture Decisions & Rationale:

• Why sRGB gamma correction? Human vision perceives light non-linearly. Skipping gamma correction yields inaccurate luminance values, causing false positives in compliance checks.
• Why build-time over runtime? Runtime validation requires shipping the math library to the browser, increasing bundle size. Build-time validation catches violations during development and CI, aligning with shift-left accessibility principles.
• Why type-safe token mapping? Hardcoded hex values in CSS files drift over time. Centralizing definitions in a typed configuration enables automated auditing, theme generation, and documentation synchronization.

Pitfall Guide

1. The "Safe Grey" Illusion

Explanation: Developers frequently select mid-tone greys like #767676 for secondary text, assuming they sit safely above the 4.5:1 threshold. In reality, this specific shade yields approximately 4.1:1 against pure white, failing WCAG AA by a narrow margin. Fix: Establish a minimum luminance delta in your design system. Use #595959 or darker for body text, or implement a token generator that automatically darkens muted shades until they cross the 4.5:1 boundary.

2. Opacity Masking Drift

Explanation: CSS opacity or rgba() blending alters the effective foreground color by compositing it with the background. A #555555 text element with opacity: 0.5 over white renders at roughly #AAAAAA, dropping the contrast ratio below 2:1. Fix: Never rely on opacity for text hierarchy. Instead, define explicit color tokens for each visual weight (e.g., textPrimary, textSecondary, textTertiary) and calculate contrast against the actual rendered composite color.

3. Brand Palette Mismatch

Explanation: Vibrant brand colors frequently fail when paired with white text. Coral (#FF6B6B) yields ~3.0:1, and gold (#FFD700) drops to ~1.7:1. These fail AA for normal text and often fail even large text requirements. Fix: Implement a brand color adaptation layer. If a primary brand shade fails contrast, automatically generate a UI-safe variant by shifting hue or reducing saturation while preserving brand recognition. Use the brand color for backgrounds with dark text instead.

4. Image/Gradient Worst-Case Ignorance

Explanation: WCAG contrast rules assume flat backgrounds. Automated tools like axe or Lighthouse cannot sample per-pixel luminance across complex images or gradients. Text placed over a gradient may pass in light areas but fail catastrophically in dark zones. Fix: Apply a semi-transparent scrim (linear-gradient or backdrop-filter) to guarantee a minimum contrast floor, or use a solid background strip behind text blocks. Validate using manual sampling at the darkest expected pixel coordinate.

5. Color-Only State Signaling

Explanation: WCAG 1.4.1 explicitly prohibits conveying information solely through color. A red error state and green success state are indistinguishable to users with deuteranopia or protanopia, regardless of contrast ratio. Fix: Always pair color with a secondary signal: icons, text labels, border patterns, or shape variations. Ensure the secondary signal also meets contrast requirements independently.

6. Size Threshold Blind Spots

Explanation: Teams often apply the 4.5:1 rule universally, missing the relaxed 3:1 threshold for large text (≥18pt regular or ≥14pt bold). Conversely, they may assume 3:1 is acceptable for body text, which violates AA. Fix: Map font sizes and weights to WCAG categories in your token system. Enforce 4.5:1 for anything below the large text threshold, and document the breakpoint clearly in component specifications.

7. Automated Tool False Negatives

Explanation: Static analysis tools evaluate computed styles at a single point in time. They miss dynamic theme switches, hover states, focus rings, and overlay modals that introduce new background/foreground combinations. Fix: Supplement automated audits with manual state traversal testing. Use visual regression tools that capture multiple interaction states, and enforce contrast checks on all pseudo-class variants (:hover, :focus, :disabled).

Production Bundle

Action Checklist

• Centralize all color definitions in a type-safe token configuration file
• Implement gamma-corrected luminance calculation using the WCAG sRGB curve
• Build a contrast ratio validator that outputs AA/AAA pass/fail status
• Integrate token validation into the pre-commit hook and CI pipeline
• Replace opacity-based text hierarchy with explicit contrast-safe tokens
• Audit all brand colors against white and dark backgrounds; generate UI-safe variants
• Add secondary signals (icons, borders, labels) to all color-dependent states
• Verify text-over-image components using worst-case pixel sampling or scrim overlays

Decision Matrix

Scenario	Recommended Approach	Why	Cost Impact
Static Marketing Site	Build-time token validation + manual gradient audit	Predictable backgrounds, low dynamic complexity	Low (one-time setup)
Enterprise SaaS Dashboard	Centralized token system + CI gate + runtime theme fallback	High component density, frequent theme switches	Medium (pipeline integration)
Dynamic Data Visualization	Runtime contrast adapter + manual worst-case sampling	Colors generated from data ranges, unpredictable combinations	High (requires adaptive logic)
Legacy Codebase Refactor	Incremental token migration + axe DevTools scanning	Existing inline styles, scattered hex values	High (phased rollout required)

Configuration Template

// design-tokens/contrast.config.ts
export const contrastThresholds = {
  normalText: { AA: 4.5, AAA: 7.0 },
  largeText: { AA: 3.0, AAA: 4.5 },
  uiComponents: { AA: 3.0, AAA: 4.5 },
};

export const tokenValidationRules = {
  failOnAAViolation: true,
  warnOnAAAViolation: true,
  ignorePseudoStates: false,
  maxBundleSizeKB: 0, // Build-time only
};

export const brandAdaptationStrategy = 'darken-on-failure'; // Options: 'darken', 'lighten', 'shift-hue'

/* Generated output: design-tokens/contrast-variables.css */
:root {
  --color-text-primary: #1F2937;
  --color-text-secondary: #4B5563;
  --color-text-muted: #6B7280;
  --color-surface-default: #FFFFFF;
  --color-surface-inverse: #111827;
  
  /* Contrast-safe pairings validated at build */
  --pair-body: var(--color-text-primary) on var(--color-surface-default); /* 12.6:1 */
  --pair-caption: var(--color-text-muted) on var(--color-surface-default); /* 5.7:1 */
}

@media (prefers-color-scheme: dark) {
  :root {
    --color-surface-default: #111827;
    --color-text-primary: #F9FAFB;
    --color-text-secondary: #D1D5DB;
    --color-text-muted: #9CA3AF;
  }
}

Quick Start Guide

1. Install the validator: Create a contrast-engine.ts file containing the gamma-corrected luminance and ratio calculation functions. Export evaluateContrast() for use across your project.
2. Define your token map: Replace scattered hex values with a centralized configuration object mapping component states to foreground/background pairs.
3. Add a build script: Create a validate-tokens.ts entry point that imports your token map, runs evaluateContrast() on each pair, and exits with a non-zero status if AA thresholds are breached.
4. Hook into CI: Add the validation script to your package.json as a prebuild or lint:tokens command. Configure your CI pipeline to block merges when the validator returns failures.
5. Verify locally: Run npm run lint:tokens after any palette change. The output will list exact token names, calculated ratios, and recommended adjustments until all pairs pass WCAG AA.