agentleFS
imtiazrayhanimtiazrayhan/agentscamp-library/skills/accessibility-regression-auditor/SKILL.md

accessibility-regression-auditor

Skill1 starsChanged 5 days agoMITView on GitHub

Audit a UI change for accessibility regressions by combining automated checks with keyboard, focus, semantic, name-role-value, contrast, zoom, and screen-reader-oriented inspection. Use when reviewing a component or pull request, adding a dialog or form, changing navigation, or investigating an accessibility failure that a linter alone cannot explain.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 project-native automation: Use configured linters, component tests, browser tests, or accessibility scanners.

    line 13
  2. Distinctive:

    Inspect semantics first: Prefer native controls and landmarks.

    line 14
  3. Distinctive:

    Trace keyboard operation: Check reachability, visible focus, logical order, activation, escape behavior, focus trapping, roving tabindex …

    line 15
  4. Distinctive:

    Check dynamic communication: Verify validation errors, async completion, toasts, expanded state, live regions, and route changes are …

    line 16
  5. Distinctive:

    Review visual access: Check text and non-text contrast, focus indicators, 200% zoom, narrow reflow, text spacing, target size, motion …

    line 17
  6. Distinctive:

    Exercise a representative assistive path: When browser or platform tools are available, inspect the accessibility tree and test the …

    line 18

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

Review the changed user journey, not just the component markup or automated score.

Workflow

  1. Define the affected journey. Identify changed pages, components, states, breakpoints, input methods, and user actions. Include loading, empty, error, validation, success, and disabled states.
  2. Run project-native automation. Use configured linters, component tests, browser tests, or accessibility scanners. Preserve tool versions, routes, rules, and raw violations. Treat automation as one evidence layer.
  3. Inspect semantics first. Prefer native controls and landmarks. Verify heading order, labels, descriptions, table relationships, lists, link purpose, and name-role-value. Flag ARIA that replaces or contradicts native behavior.
  4. Trace keyboard operation. Check reachability, visible focus, logical order, activation, escape behavior, focus trapping, roving tabindex where appropriate, and return of focus after dialogs or transient UI closes.
  5. Check dynamic communication. Verify validation errors, async completion, toasts, expanded state, live regions, and route changes are announced without stealing focus or repeating excessively.
  6. Review visual access. Check text and non-text contrast, focus indicators, 200% zoom, narrow reflow, text spacing, target size, motion preferences, and information conveyed only by color, position, hover, or animation.
  7. Exercise a representative assistive path. When browser or platform tools are available, inspect the accessibility tree and test the critical flow with a screen-reader-oriented sequence. Do not claim device coverage that was not performed.
  8. Prioritize and regress. Rank findings by blocked task and affected population. For deterministic defects, recommend the smallest automated regression check; retain manual steps for behavior automation cannot prove.

[!WARNING] A zero-violation automated scan is not a pass. A perfectly valid button named “button” can still make a workflow unusable.

Output

Provide the audited scope, environments and tools, findings with element or file evidence, affected interaction, severity, recommended remediation, and exact verification step. Separate automated, manual, and untested coverage.

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.