SkillVaultskills Browse all 1,000+ skills

Frontend · Version 1.4.0 · Reviewed 2026-08-02

Contrast Compliance Auditor

Improve rendered color measurement and interactive state contrast review with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 5 diagnostic checks 7 quality gates

Measures text, icon, focus, border, placeholder, and state contrast against rendered colors across themes, gradients, opacity, hover, disabled, and error states.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Rendered color measurement
  • Interactive state contrast review
  • Theme regression verification

How Contrast Compliance Auditor works

You provide

Obligations, data inventory, and current controls

It inspects

Requirement type and implemented control for rendered color measurement

It decides

A interactive state contrast review gap register with accountable owners

You verify

Each control mapped to evidence an auditor would accept

What it checks first

Contrast Compliance Auditor measures text, icon, focus, border, placeholder, and state contrast against rendered colors across themes, gradients, opacity, hover, disabled, and error states. Use it when the work involves Rendered color measurement, Interactive state contrast review, Theme regression verification.

  1. Whether the obligation is a legal requirement, a contractual commitment, or an internal policy — the escalation path differs.
  2. The specific data categories and lawful basis, rather than a general statement about compliance.
  3. Data flows across jurisdictions and processors, which determine transfer obligations.
  4. Retention and deletion behavior in every downstream copy, including backups and analytics.
  5. Who is accountable for the decision, since a compliance analysis without an owner is not actionable.

Failure modes it recognizes

  • Deletion implemented in the primary store while copies persist in backups, exports, logs, and warehouses.
  • Consent collected for one purpose and reused for another without a valid basis.
  • A subprocessor added without a data-processing agreement or customer notification.
  • Retention policy defined but never enforced by an automated job.
  • A control documented in policy but not implemented in the system it describes.

Answers it will reject

  • Providing a definitive legal conclusion rather than a structured analysis for qualified review.
  • Treating a compliance certification as evidence that a specific control works.
  • Relying on contractual language to mitigate a technical risk that is technically preventable.
  • Presenting risk without severity, likelihood, and the accountable owner.

Decision rules it applies

  • Separate legal requirement, contractual obligation, and internal policy in every finding.
  • Escalate to qualified counsel for anything that constitutes legal advice, and say so plainly.
  • Map every obligation to a specific implemented control and its evidence, or mark it as a gap.
  • Prefer technical enforcement over documented intent, because documented intent is not a control.

Evidence it asks for

  • Build a data inventory: category, source, purpose, basis, location, retention, and downstream copies.
  • Trace one deletion request end to end and enumerate every store it must reach.
  • Record the evidence artifact that would satisfy an auditor for each control.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to rendered color measurement.
  2. Trace concrete failure or abuse paths for interactive state contrast review; do not report checklist items without a mechanism.
  3. Prioritize theme regression verification findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Rendered color measurement assessment
  • Interactive state contrast review decision and action plan
  • Theme regression verification verification checklist

Evidence requirements

  • Interface code, rendered behavior, and user journey
  • Browser/device matrix and accessibility tree
  • Performance and usability observations

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Audit contrast across light and dark themes for text, icons, focus rings, form borders, disabled controls, and status badges.

Expected output

Measure computed foreground and background at the rendered state, including alpha blending and gradients, then classify text size and non-text function correctly. Check hover, focus, selected, error, and forced-colors behavior; recommend token-level corrections that preserve state distinction across every affected component...

Boundaries and compatibility

Ideal for

  • Rendered color measurement: produce a decision or artifact grounded in supplied evidence.
  • Interactive state contrast review: produce a decision or artifact grounded in supplied evidence.
  • Theme regression verification: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Treating automated accessibility scans as complete
  • Changing visual style without preserving behavior

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.