color-accessibility
>
Works with
--- name: color-accessibility description: > license: MIT --- # Color Accessibility ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Accessible color design ensures all users, including those with color vision deficiency, can access and understand information. ## When to Use - Creating color palettes - Designing data visualizations - Testing interface designs - Status indicators and alerts - Form validation states - Charts and graphs ## Quick Start Minimal working example: ```yaml 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) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [Color Contrast Standards](references/color-contrast-standards.md) | Color Contrast Standards | | [Color Vision Deficiency Simulation](references/color-vision-deficiency-simulation.md) | Color Vision Deficiency Simulation | | [Accessible Color Usage](references/accessible-color-usage.md) | Accessible Color Usage | | [Testing & Validation](references/testing-validation.md) | Testing & Validation | ## Best Practices ### ✅ DO - Ensure 4.5:1 contrast minimum (WCAG AA) - Test with color blindness simulator - Use patterns or icons with color - Label states with text, not color alone - Test with real users with color blindness - Document color usage in design system - Choose accessible color palettes - Use sequential colors for ordered data - Validate all color combinations - Include focus indicators ### ❌ DON'T - Use color alone to convey information - Create low-contrast text - Assume users see colors correctly - Use red-green combinations - Forget about focus states - Mix too many colors (>5-8) - Use pure red and pure green together - Skip contrast testing - Assume AA is sufficient (AAA better) - Ignore color blindness in testing
More Accessibility skills
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
ui-ux-pro-max
nextlevelbuilder/ui-ux-pro-max-skill
UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

