agentsclimarketplace

A11y scan

Skill badass-courses/a11y-agent/source/skills/a11y-scan

Accessibility expertise for AI coding agents.

Install
npx -y skills add badass-courses/a11y-agent --skill a11y-scan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run automated accessibility scan using axe-core via Playwright. Captures WCAG violations, tracks progress over time. Use when asked to "scan for accessibility", "run axe", or "check a11y automatically".

SKILL.md

2.2 KB, as published. Nobody here has run it

Run an automated accessibility scan on {{url}} scoped to {{scope}} if specified.

→ Consult the a11y-agent skill for accessibility standards and patterns.

Process

  1. Check if Playwright and @axe-core/playwright are available (npx playwright --version)
  2. If not installed, suggest: npm install -D @axe-core/playwright playwright && npx playwright install chromium
  3. Generate the scan script from reference/axe-scan.md and write to a temp file
  4. Execute the scan against the target URL
  5. Parse results into severity categories (critical, serious, moderate, minor)
  6. If previous scan results exist in a11y-scan-results/, compare and note changes
  7. Store results in a11y-scan-results/YYYY-MM-DD.json
  8. Present human-readable report with fix suggestions per violation

What Automated Scans Catch (30-50% of issues)

Can detect:

  • Missing alt text, labels, ARIA attributes
  • Color contrast violations (computed styles)
  • Duplicate IDs, missing lang, landmark issues
  • Invalid ARIA roles and attributes
  • Missing form labels

Cannot detect:

  • Keyboard operability (use a11y-test or manual testing)
  • Focus management logic (does focus return on close?)
  • Screen reader UX quality (is the reading order logical?)
  • Whether heading hierarchy is logical (only structural validity)
  • Whether alt text is meaningful (only that it exists)
  • Dynamic state issues (only tests what's rendered at scan time)

Always pair with manual testing via a11y-audit.

Scan Tips

  • Scan with menus/modals open — axe only tests what's rendered on screen
  • Scope rules with {{scope}} to reduce noise from known third-party widget issues
  • Run scans at multiple viewport sizes to catch responsive accessibility issues
  • For CI integration, use cy.checkA11y() at the integration test level — see a11y-test
  • Compare scan results over time to track remediation progress

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.