agentleFS
VicentehersantVicentehersant/vhs-agents-and-skills/skills/a11y-wcag/SKILL.md

a11y-wcag

Skill0 starsChanged 39 days agoMITView on GitHub

WCAG 2.2 AA accessibility auditing and fixing — contrast, keyboard, ARIA, forms, motion, touch targets. Use on any UI review, before shipping pages, and whenever accessibility is requested.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After fixes: recompute contrast numerically, tab through the page (with a browser tool if available), confirm the reduced-motion path …

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

A11y / WCAG 2.2 AA

Audit checklist (ordered by how often it fails in real projects)

  1. Contrast (1.4.3 / 1.4.11): text 4.5:1 (3:1 large), UI components and borders 3:1. Special cases: text over animated backgrounds/gradients (check the worst frame), brand accents used as text (use a darker -text token), buttons vs page background (may need a distinct surface).
  2. Forms (1.3.1 / 3.3.1 / 4.1.2): <label htmlFor>, aria-invalid, aria-describedby pointing to the error message, errors as text — not color only.
  3. Keyboard: full tab order, visible focus (never outline: none without a replacement), skip link, tabindex="-1" on the <main> skip target, dropdowns/modals trap and restore focus, Escape closes.
  4. Semantics: landmarks (header/nav/main/footer), heading hierarchy, one h1, buttons for actions vs links for navigation, alt text (empty alt for decorative).
  5. Motion (2.3.3): respect prefers-reduced-motion in every animation — skip or reduce the effect, don't just shorten it.
  6. Touch targets: ≥44×44px on mobile, especially bottom navs and icon buttons.

Output format

Table: WCAG criterion · element · severity (Critical/Serious/Moderate) · fix with code. Fix criticals immediately; batch the rest.

Verification

After fixes: recompute contrast numerically, tab through the page (with a browser tool if available), confirm the reduced-motion path exists.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.