antislop-human

Validates UI accessibility for contrast, keyboard navigation, focus states, and mobile zoom against WCAG criteria.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/dxiiren/project-skeleton --skill antislop-human-dxiiren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: antislop-human
Source: https://github.com/dxiiren/project-skeleton/tree/main/.claude/skills-optional/anti-slop/antislop-human
Command: npx skills add https://github.com/dxiiren/project-skeleton --skill antislop-human-dxiiren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated UIs frequently ship accessibility defects: low-contrast text, removed focus outlines, mouse-only interactions, and color-only status feedback that exclude users with different vision, motor, and device setups. This Skill gives an AI coding agent concrete rules and a deterministic contrast checker so these defects are caught before delivery. ## Core Features & Use Cases - WCAG Contrast Verification: Ships a Python script (contrast-check.py), the WCAG 2.x luminance formula, and a precomputed reference table so color pairings are computed rather than guessed, with PASS/FAIL verdicts for normal (4.5:1) and large (3:1) text. - Keyboard, Focus, and State Rules: Tell/Why/Fix entries covering focus outlines, tab order, Escape-closable dialogs, non-text contrast (3:1), and perceivable empty/loading/error states. - Mobile Exclusion Checks: Rules for 200% text zoom without clipping and keeping focused inputs visible above the on-screen keyboard. - MCP Server Option: contrast-mcp.py exposes the contrast checker as a Model Context Protocol stdio tool for agents that support MCP. - Use Case: While building a settings page, the agent runs python3 contrast-check.py "#FFFFFF" "#777777", sees normal text FAIL at 4.48:1, and darkens the label before shipping. ## Quick Start Ask the agent to audit your UI's colors and keyboard interactions using the antislop-human checklist and run the bundled contrast checker on every text and background pairing.

Frequently Asked Questions about antislop-human

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

FAQPage Schema
How do I check WCAG color contrast from the command line?

Run the bundled script with two hex colors: python3 contrast-check.py "#FFFFFF" "#777777". It prints the contrast ratio and PASS/FAIL verdicts for normal text (4.5:1) and large text (3:1), exiting 0 only when both pass.

How to calculate WCAG contrast ratio between two hex colors?

Convert each channel to 0-1, linearize with the WCAG formula (divide by 12.92 below 0.03928, else raise ((c+0.055)/1.055) to 2.4), compute luminance as 0.2126R + 0.7152G + 0.0722B, then ratio = (L1+0.05)/(L2+0.05).

What contrast ratio is required for WCAG AA compliance?

Normal text requires 4.5:1 and large text (18px or larger) requires 3:1. Non-text UI components such as button borders, icons, and focus indicators require 3:1 against adjacent colors per WCAG 1.4.11.

Does the contrast checker work without the Python script?

Yes. The skill documentation includes the full WCAG formula and a precomputed reference table of common pairings, so the check can be done manually. The script is a convenience, not a requirement.

Can the contrast checker be used as an MCP tool?

Yes. The skill ships contrast-mcp.py, a minimal Model Context Protocol stdio server exposing a check_contrast tool that takes foreground and background hex colors and returns the ratio with pass/fail verdicts.

Why does grey text on white backgrounds often fail accessibility checks?

The eye overestimates contrast on grey pairs. For example #777777 on white computes to 4.48:1, failing the 4.5:1 normal-text threshold, and #555555 on black is only 2.82:1. Always compute the ratio rather than judging by eye.