agentleFS
smukhsmukh/a11y-agent-skills/skills/accessibility-regression-test/SKILL.md

accessibility-regression-test

Skill8 starsChanged 2 months agoMITView on GitHub

Protect the user-facing behavior that failed, after the repair has been verified in the original state. 1. Read the before evidence and verified after evidence. State the barrier in terms of user behavior. 2. Choose the narrowest reliable layer with references/test-selection.md. 3. Make the test fail against the known broken behavior when practical, then pass with the repair. 4. Assert outcomes such as focus destination, exposed error, accessible name, or absence of the original fingerprint. Do not assert only that…

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:

    Read the before evidence and verified after evidence.

    line 20
  2. Distinctive:

    Keep manual-only outcomes as an explicit review record rather than a misleading automated test.

    line 31
  3. Distinctive:

    Do not snapshot raw axe output, browser versions, run IDs, or timestamps.

    line 36

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

Accessibility regression test

Protect the user-facing behavior that failed, after the repair has been verified in the original state.

Workflow

  1. Read the before evidence and verified after evidence. State the barrier in terms of user behavior.
  2. Choose the narrowest reliable layer with references/test-selection.md.
  3. Make the test fail against the known broken behavior when practical, then pass with the repair.
  4. Assert outcomes such as focus destination, exposed error, accessible name, or absence of the original fingerprint. Do not assert only that an attribute string exists.
  5. Control route, state, viewport, reduced motion, and data so the test is repeatable.
  6. Keep manual-only outcomes as an explicit review record rather than a misleading automated test.

Boundaries

Do not snapshot raw axe output, browser versions, run IDs, or timestamps. Do not weaken a rule, baseline away a new issue, hide content, or remove functionality to make a test pass. A regression test protects its scoped behavior; it does not certify the component or page.

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.