agentleFS
Sign inStart free
SnoozleStudioSnoozleStudio/opencode-wp-settings/skills/wp-accessibility/SKILL.md

wp-accessibility

Skill4 starsChanged 3 days agoMITView on GitHub

Enforce WCAG 2.2 AA and WordPress accessibility-ready standards in themes, plugins, and front-end work. Use when building or reviewing templates, menus, forms, modals, animations, or any UI. Loads the accessibility checklist and audits markup for contrast, keyboard operability, semantics, ARIA, focus, and reduced motion.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Forms: every input has <label> (placeholder is NOT a label).

    line 19
  2. Distinctive:

    All controls keyboard-operable: menus, modals, accordions (focus trap in modals, Escape closes, focus returns)

    line 27
  3. Very specific:

    Read the markup/template output (or use chrome-devtools MCP a11y tree when available)

    line 39
  4. Distinctive:

    Never claim "accessible" without running the checklist — a passing build proves nothing about accessibility.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Accessibility — WCAG 2.2 AA

Load docs/accessibility.md for the full checklist. Every theme/plugin ships accessible — it is not optional.

Template checklist (PHP)

  • Skip link: first element in wp_body_open(), visually hidden until keyboard focus
  • Landmarks: <header>, <nav>, <main>, <footer>; aria-current="page" on active nav items (nav walkers)
  • Headings: logical hierarchy (h1 once, no skipped levels), not presentational
  • Links: descriptive text (never "click here" / bare URLs); underlined or 3:1 contrast
  • Images: descriptive alt; decorative alt="" or CSS background
  • Forms: every input has <label> (placeholder is NOT a label); <fieldset>+<legend> for groups; error messages perceivable and near the control
  • Contrast: 4.5:1 body text, 3:1 large text/UI; color never the only differentiator
  • Zoom: everything usable at 200% without multi-directional scrolling; relative units
  • JS-off: content usable with JS disabled (<noscript> fallbacks for enhanced UI)

Interaction checklist (JS/CSS)

  • All controls keyboard-operable: menus, modals, accordions (focus trap in modals, Escape closes, focus returns)
  • Focus styles never removed without a more visible replacement
  • prefers-reduced-motion honored: gate Lenis, GSAP ScrollTrigger anims, marquees, auto-playing media (use gsap.matchMedia or window.matchMedia gate)
  • Touch targets ≥ 44×44px
  • Icon-only buttons: aria-label
  • aria-expanded + aria-controls on toggles; inert on closed panels
  • No * { transition: all }; no animation of non-compositor properties

Audit procedure

  1. Read the markup/template output (or use chrome-devtools MCP a11y tree when available)
  2. Walk the WCAG 2.2 principles: Perceivable, Operable, Understandable, Robust
  3. Report findings: element/selector, principle violated, exact fix
  4. WordPress-specific: verify Theme Review a11y minimums (skip link, focus, contrast, semantic headings, keyboard nav)

Never claim "accessible" without running the checklist — a passing build proves nothing about accessibility.

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.

Check your setup, free