---
name: css-color-contrast-assistant
description: Specialized assistant for ensuring accessible, readable UI by adhering to color contrast standards in CSS, following WCAG 2.1 AA/AAA compliance.
title: css-color-contrast-assistant
canonical_url: https://skilld.dev/gh/corey-alix/dwp-hours/css-color-contrast-assistant
last_updated: 2026-10-07T01:30:59.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install corey-alix/dwp-hours/css-color-contrast-assistant`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/css-color-contrast-assistant`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/corey-alix/dwp-hours/css-color-contrast-assistant) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/css-color-contrast-assistant`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/css-color-contrast-assistant --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/css-color-contrast-assistant --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# CSS Color Contrast Assistant

## Description

Specialized assistant for ensuring accessible, readable UI by adhering to color contrast standards in CSS. Prioritizes maintainability via CSS variables and modular design, following WCAG 2.1 AA/AAA compliance for the DWP Hours Tracker project.

## Trigger

Activate when users ask about:

- Color contrast ratios and accessibility
- WCAG compliance for text and non-text elements
- Implementing accessible color schemes in CSS
- Checking or calculating contrast between colors
- Color-related accessibility issues
- Best practices for color contrast in web design

## Response Pattern

Follow this step-by-step approach when assisting with color contrast:

1. **Assess Current Implementation**: Review existing colors, identify potential contrast issues, and check against WCAG 2.1 standards (AA: 4.5:1 for normal text, 3:1 for large text/non-text; AAA: 7:1 for normal text, 4.5:1 for large text)

2. **Calculate Contrast Ratios**: Use the relative luminance formula (L = 0.2126*R + 0.7152*G + 0.0722\*B) and contrast ratio formula ((L1 + 0.05) / (L2 + 0.05)) to verify combinations

3. **Recommend Compliant Combinations**: Suggest color pairs that meet minimum standards, prioritizing the project's design tokens in `tokens.css`

4. **Guide CSS Implementation**: Direct users to use CSS custom properties from `tokens.css`, implement modular color definitions, and follow atomic CSS principles

5. **Address Edge Cases**: Cover hover/focus states, disabled elements, high contrast mode (`prefers-contrast`), and dark mode (`prefers-color-scheme`)

6. **Provide Validation Methods**: Recommend tools like browser DevTools, WebAIM Contrast Checker, WAVE, or automated testing with axe-core/pa11y

7. **Suggest Automation**: Guide integration of contrast checks in build process and CI/CD pipelines

## Examples

Common user queries that should trigger this skill:

- "How do I ensure good color contrast in my CSS?"
- "Check if these colors meet WCAG accessibility standards"
- "What contrast ratio do I need for text on this background?"
- "Help me fix low contrast between my button text and background"
- "How to implement accessible color schemes using CSS variables?"
- "Are my current colors compliant with WCAG 2.1 AA?"

## Additional Context

This skill integrates with the DWP Hours Tracker project's design system:

- Leverages `tokens.css` for centralized color definitions
- Follows atomic CSS principles from `atomic.css`
- Supports project's accessibility goals and WCAG 2.1 compliance
- References existing color contrast policies in project documentation
- Encourages use of CSS custom properties for theme switching and maintainability
- Considers user preferences like `prefers-contrast` and `prefers-color-scheme`
- Promotes automation through build-time contrast validation</content>
  <parameter name="filePath">/home/ca0v/code/corey-alix/dwp-hours/mars/.github/skills/css-color-contrast-assistant/SKILL.md
