Skip to content
Testing
Skill

/accessibility-regression-detector

Compare audits across commits to find new, fixed and regressed issues.

From plugin
accessibility-agents
431113 skills7 hooks

Claude Code

$ npx -y skills add Community-Access/accessibility-agents --skill accessibility-regression-detector --agent claude-code

SKILL.md

accessibility-regression-detector.SKILL.md
name: accessibility-regression-detector
description: Compare audits across commits to find new, fixed and regressed issues.
license: MIT
disable-model-invocation: true
metadata:
  tier: specialist
  domain: cross-cutting
  output: findings
  effort: medium
  title: Accessibility Regression Detector

Accessibility Regression Detector

You detect accessibility regressions - issues previously fixed that have returned, or new issues from recent changes.

Detection Modes

1. **Audit Report Comparison** - Compare two audit reports, classify issues as New/Persistent/Fixed/Regressed 2. **Git History Analysis** - Scan changed files for accessibility anti-patterns 3. **Baseline Management** - Compare against `.a11y-baseline.json` known-good state

Regression Classification

Each category, with its definition and priority.

| Category | Definition | Priority | |----------|-----------|----------| | Regressed | Was fixed, has returned | Highest | | New | Not in previous audit | High | | Persistent | Exists in both audits | Medium | | Fixed | Resolved since baseline | Track |

Anti-Patterns in Diffs

Flag: `outline: none` without `:focus-visible`, div/span with click handlers, `<img>` without `alt`, positive `tabindex`, `aria-hidden` on focusable elements, heading level skips, missing label associations.

Output

Regressed and new issues go in `findings`, regressed first. Put the score delta and the new/fixed/regressed/persistent counts in `notes`, and list fixed checks in `passed`; the findings schema has no other place for them.

Output contract

Return only JSON matching `skills/a11y-core/schemas/findings.schema.json`. No prose, no summary, no restated instructions. One object, one array of findings.

Shared rules, dispatch contract and schemas: `skills/a11y-core/SKILL.md`. Authoritative specifications for this skill: `skills/a11y-core/references/sources.md`.

Read more
@community-access
Ships withaccessibility-agents

WCAG 2.2 AA enforcement for agentic coding, as a set of Agent Skills. One package, read natively by Claude Code, Codex, GitHub Copilot, Gemini CLI and Antigravity, with no per-client copies. Models forget accessibility while generating code.

Stars on GitHub

Momentum

stars in total
431
Star history of Community-Access/accessibility-agents on GitHub, a chart by star-history.com

Other skills on accessibility-agents.

More skills from other plugins.

api-review

api-review

Produce the "Playwright 1.xx API Review" artifact for a range of commits - the public API additions and the breaking or behavior…

@microsoft@microsoftInstall Skill
add-e2e-selectors

add-e2e-selectors

Add reliable @grafana/e2e-selectors to interactive elements and key containers in the Grafana frontend. Use when adding e2e…

grafanatoday78k
@grafana@grafanaInstall Skill
promptfoo-evals

promptfoo-evals

Write, refine, run, and QA promptfoo evaluation suites: promptfooconfig.yaml, prompts, providers, vars, tests, assertions,…

@promptfoo@promptfooInstall Skill
deepeval

deepeval

DeepEval evaluation workflow for AI agents and LLM applications. TRIGGER when the user wants to evaluate or improve an AI agent,…

@confident-ai@confident-aiInstall Skill

Questions about accessibility-regression-detector.

Which coding agents can use accessibility-regression-detector?
accessibility-regression-detector installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.