use-of-color

Identify color-only UI indicators and propose WCAG 1.4.1 accessible alternatives.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scamai/scamai-landing --skill use-of-color-scamai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-of-color
Source: https://github.com/scamai/scamai-landing/tree/main/.agents/skills/use-of-color
Command: npx skills add https://github.com/scamai/scamai-landing --skill use-of-color-scamai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies color-only indicators in user interfaces and provides actionable guidance to add non-color cues such as text, icons, or ARIA attributes to meet WCAG 1.4.1.

Core Features & Use Cases

  • Detect color-only signals in UI components, forms, and charts and flag potential accessibility risks.
  • Recommend non-color indicators (text labels, icons, patterns) and ARIA attributes to improve accessibility.
  • Generate remediation guidance and practical implementation steps for frontend teams.

Quick Start

Scan your codebase for color-only indicators and apply accessibility fixes.

Frequently Asked Questions about use-of-color

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix color-only indicators to meet WCAG 1.4.1 accessibility requirements?

To fix color-only indicators for WCAG 1.4.1, add non-color cues like text labels, icons, patterns, or ARIA attributes alongside existing color signals. This ensures UI state information remains accessible to all users regardless of color perception.

What counts as a color-only indicator in UI components and forms?

Color-only indicators in UI components and forms are visual elements that convey state or meaning solely through color, such as red borders for errors or green fields for success. They create accessibility barriers when no supplementary text, icon, or ARIA attribute reinforces the message.

How do I scan my frontend codebase for color-only accessibility issues?

Scan your frontend codebase by analyzing UI state cues across components, forms, and visualizations to detect where color conveys meaning without backup indicators. This process flags potential accessibility risks and documents concrete remediation steps and testing guidance.

Does WCAG 1.4.1 apply to data visualizations and dashboards?

Yes, WCAG 1.4.1 applies to data visualizations and dashboards where color conveys state or meaning. Charts and graphs must include non-color cues like patterns, text labels, or direct labeling to ensure information is accessible without color perception.

What's the best way to add non-color cues to existing UI state indicators?

The best way to add non-color cues is to supplement existing color signals with text labels, icons, or patterns, and apply ARIA attributes for screen readers. This multi-layered approach ensures state information is perceivable across all user contexts.