agentleFS
smukhsmukh/a11y-agent-skills/skills/accessible-component-review/SKILL.md

accessible-component-review

Skill8 starsChanged 2 months agoMITView on GitHub

Review every supported state and input path of one reusable component. 1. Inventory states, variants, input methods, content slots, and expected semantics. 2. Select the native element that already provides the behavior. Use ARIA patterns only when native HTML cannot provide the required interaction. 3. Apply references/component-checklist.md to each state. 4. Run deterministic rules, keyboard behavior, forced-colors, reduced-motion, zoom/reflow, and pointer target checks. Record manual judgment separately. 5. Trace failures to the component source and repair the smallest shared layer…

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Run deterministic rules, keyboard behavior, forced-colors, reduced-motion, zoom/reflow, and pointer target checks.

    line 25
  2. Distinctive:

    Add tests for user-visible behavior and verify consuming examples do not regress.

    line 29
  3. Distinctive:

    Do not add ARIA that duplicates or conflicts with native semantics.

    line 34

≈ “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

Accessible component review

Review every supported state and input path of one reusable component.

Workflow

  1. Inventory states, variants, input methods, content slots, and expected semantics.
  2. Select the native element that already provides the behavior. Use ARIA patterns only when native HTML cannot provide the required interaction.
  3. Apply references/component-checklist.md to each state.
  4. Run deterministic rules, keyboard behavior, forced-colors, reduced-motion, zoom/reflow, and pointer target checks. Record manual judgment separately.
  5. Trace failures to the component source and repair the smallest shared layer that owns the defect.
  6. Add tests for user-visible behavior and verify consuming examples do not regress.

Boundaries

Do not add ARIA that duplicates or conflicts with native semantics. Do not treat a single Storybook example as coverage of every consumer. Do not assert that an accessible name is meaningful without content context.

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.