agentleFS
seancabalseseancabalse/agentic-playbook/skills/a11y-audit/SKILL.md

a11y-audit

Skill0 starsChanged 15 days agoMITView on GitHub

Audit a screen or a release for WCAG 2.2 AA accessibility. Use for each new screen and before a release.

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use perf-audit, design-tokens and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • WhatIfWeDigDeeperSkill

    perf-audit

    Profile and optimize React application performance

    Also in 4 projects that use this

  • ilikescienceSkill

    design-tokens

    Expert in design tokens using the DTCG specification. Use this skill when users ask about design tokens, DTCG format, token validation, formatting, transformation, color spaces (sRGB, Display P3, OKLCH), references and aliasing, resolvers, theming with modifiers/contexts, multi-platform design systems, accessibility, or working with tools like jq, jsonata, and terrazzo. Helps with token file creation, resolver configuration, structure, naming conventions, and best practices.

    Also in 4 projects that use this

  • Sagargupta16Skill

    dependency-audit

    Audit project dependencies for security vulnerabilities, licensing issues, maintenance health, and optimization opportunities. Use it during regular security audits (monthly or quarterly); before a major release when you want to ensure the dependency tree is clean; when evaluating whether to adopt or replace a dependency; after a security advisory affects one of your dependencies; when your install times or bundle sizes have grown noticeably.

    Also in 3 projects that use this

  • lbednerSkill

    i18n

    Use when a code or template change introduces a new translation message key, in either the framework CLI (aegis/i18n/locales/) or a generated project's CLI (the app/i18n/locales/ template tree). Covers adding the real English string, stubbing the same key into every other locale for parity, and the separate translation PR that later replaces placeholders with reviewed native text.

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 5 projects that use this

  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Every interactive element has a role and a label (plus a hint where useful).

    line 17
  2. Distinctive:

    No raw strings; plurals and selects in ICU.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “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 audit

Playbook files named here: when the project has its own copy at .playbook/local/<same path>, use that copy instead.

Scope: $ARGUMENTS

Principles: ${CLAUDE_PLUGIN_ROOT}/principles/05-accessibility-i18n.md. Report shape: ${CLAUDE_PLUGIN_ROOT}/templates/audit-report.md.

Static pass (code)

  • Every interactive element has a role and a label (plus a hint where useful); decorative art is hidden; people and things are named fully.
  • No raw strings; plurals and selects in ICU; no concatenated sentences; no pronoun inferred from a name.
  • Selected, error and required states aren't colour-only. Text and UI contrast comes from the tokens (4.5:1 for text, 3:1 for large text and UI).
  • Text is sized in relative units; text in fixed art scales with the art and is mirrored in an accessible name; rows wrap; button rows stack at narrow widths and high zoom.
  • Targets are at least 24 × 24 CSS px (44 recommended), or padding extends the hit area.
  • Animations respect reduce motion, including entering animations, which never leave content at opacity 0.
  • Semantic elements, labelled form fields, focus management on dialogs and route changes, no tabindex > 0, skip link; axe has no violations.

Live pass (browser)

  1. The largest text size: 200% zoom (1.4.4), and reflow at 320 CSS px (400% zoom, 1.4.10). Screenshot each screen and look for clipping, overlap, truncation and sideways scrolling.
  2. Screen reader: NVDA (Windows) or VoiceOver (macOS). Swipe through each screen: order, labels, roles, state announcements, nothing unreachable.
  3. Reduce motion on: nothing moves continuously, and nothing is invisible.
  4. Keyboard: Tab through everything, focus is visible, no traps, Escape closes dialogs.
  5. Reset every setting you changed.

Output

A dated audit doc with findings per WCAG criterion: severity, screen, evidence (screenshot), fix. Each finding becomes a ticket labelled accessibility. Include "checked and fine" so the next audit can compare.

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.