antislop-human

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

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/zeeforc/website-lpkpaiton --skill antislop-human-zeeforc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antislop-human
Source: https://github.com/zeeforc/website-lpkpaiton/tree/main/agent/skills/antislop-human
Command: npx skills add https://github.com/zeeforc/website-lpkpaiton --skill antislop-human-zeeforc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated interfaces frequently ship with accessibility defects: low-contrast text, removed focus outlines, mouse-only interactions, and missing loading or error states. This Skill gives coding agents concrete rules and a deterministic contrast checker so these defects are caught before delivery instead of after users complain. ## Core Features & Use Cases - WCAG Contrast Verification: A Python script, formula, and reference table compute exact contrast ratios and return PASS/FAIL verdicts for normal text (4.5:1) and large text (3:1), eliminating guessed AA claims. - Keyboard and Focus Rules: Enforces visible focus indicators, logical tab order, keyboard-operable controls, and Escape-closable dialogs. - State and Mobile Checks: Requires perceivable empty, loading, and error states, 200% text zoom without clipping, and forms that stay visible above the on-screen keyboard. - Use Case: While building a settings page, run the contrast checker on every text/background pairing, then walk the Human Skill Checklist to confirm focus visibility, keyboard access, and state coverage before shipping. ## Quick Start Check whether white text on a #777777 background passes WCAG AA and list any accessibility fixes needed in my UI.

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 contrast ratio between two colors?▼

Run the included Python script with two hex colors, for example python3 contrast-check.py "#FFFFFF" "#777777". It prints the exact ratio and PASS/FAIL verdicts for normal text at 4.5:1 and large text at 3:1, exiting nonzero when either fails.

What contrast ratio is required for WCAG AA text?▼

WCAG AA requires 4.5:1 for normal text and 3:1 for large text of 18px or more. Non-text elements like button borders, icons, and focus indicators need 3:1 against adjacent colors per WCAG 1.4.11.

Can I use the contrast checker as an MCP tool?▼

Yes, the skill ships contrast-mcp.py, a minimal MCP stdio server exposing a check_contrast tool. It accepts foreground and background hex colors and returns the ratio with pass/fail results for both text sizes as JSON.

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

The eye overestimates contrast on grey pairs, so combinations like #777777 on white measure only 4.48:1 and fail the 4.5:1 normal-text threshold. Always compute the ratio with the formula or script instead of judging by appearance.

Does the contrast checker work without the Python script?▼

Yes, the SKILL.md documents the full WCAG 2.x luminance formula and a precomputed reference table of common pairings. The script is a convenience; the formula and table are complete on their own.