antislop-human

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

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/daxrpm/epn-tracker --skill antislop-human-daxrpm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antislop-human
Source: https://github.com/daxrpm/epn-tracker/tree/main/.claude/skills/antislop-human
Command: npx skills add https://github.com/daxrpm/epn-tracker --skill antislop-human-daxrpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated and hand-built UIs frequently ship with 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 conditions. This Skill provides concrete rules and a contrast checker to catch these defects before delivery. ## Core Features & Use Cases - Contrast Verification: A bundled Python script, the WCAG 2.x luminance formula, and a precomputed reference table to verify text (4.5:1) and non-text (3:1) contrast ratios instead of eyeballing them. - Keyboard & Focus Rules: Enforces keyboard-operable controls, visible focus indicators, logical tab order, and Escape-closable dialogs. - State & Mobile Checks: Requires perceivable empty/loading/error states, 200% text zoom without clipping, and forms that stay visible above the on-screen keyboard. - Use Case: While building a React settings page, run the contrast checker on every text/background pairing, then walk the Human Skill Checklist to confirm focus rings, keyboard access, and state messaging before shipping. ## Quick Start Ask the agent to review this UI component against the antislop human accessibility rules and verify all color pairings with the contrast checker.

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 ratios for text?▼

Run the bundled contrast-check.py script with two hex colors to get the ratio and pass/fail verdict for normal and large text. Alternatively, apply the WCAG 2.x relative luminance formula or consult the precomputed reference table of common pairings.

What contrast ratio is required for WCAG AA compliance?▼

Normal text requires 4.5:1 against its background, large text (18px+) requires 3:1, and non-text UI components like icons, borders, and focus indicators require 3:1 against adjacent colors per WCAG 1.4.11.

How do I make a UI fully keyboard accessible?▼

Ensure every interactive element is reachable by Tab in visual order, activatable with Enter or Space, and that dialogs close with Escape. Never remove the focus outline without a visible replacement meeting 3:1 contrast.

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

The eye overestimates contrast on grey pairings; for example #777777 on white is only 4.48:1, failing the 4.5:1 normal-text threshold. Always compute the ratio with the formula or script rather than asserting a pairing passes.

Does this skill cover responsive layout and breakpoints?▼

No, layout mechanics like breakpoints, grids, and tap targets belong to the separate antislop-layoutmobile skill. This skill covers only the mobile details that exclude people: text zoom to 200% and the on-screen keyboard covering focused inputs.