accessibility-audit
Skill1 starsChanged 28 days agoMITView on GitHub
Run automated axe-core accessibility checks in Playwright, Selenium, or Cypress against WCAG 2.x A/AA, triage violations, and list the manual checks automation cannot cover.
- Installs packages
55 other projects use a version of this.
Adopted by
Most recently taken up by
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- ainurdev/mystical-assistanttheir own version, first seen Nov 8, 2026
- mzeleniuk/ClaudeVueProjectTemplatetheir own version, first seen Nov 8, 2026
- Smaui94/ClaudeSkillCollectiontheir own version, first seen Nov 8, 2026
- memi-design/design-skillstheir own version, first seen Nov 8, 2026
- Cure-Consulting-Group/ProductEngineeringSkillstheir own version, first seen Nov 4, 2026
Used with
Projects with it also use design-system-audit, api-design-review and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jpoindexterSkilldesign-system-audit
Audit code for design system violations - grid spacing, tokens, existing components
Also in 4 projects that use this
tekumaraSkillapi-design-review
Reviews REST API design by inventorying routes, finding overlapping functionality, comparing payloads and pagination, and checking resource naming, URL structure, identifiers, errors, idempotency, and timestamps. Use when asked to review API routes, compare endpoints, find redundant or superseding operations, assess contract consistency, or run a REST API design review.
Also in 3 projects that use this
BufferoverflovvSkillobservability-setup
Add production observability to a FastMCP server: request IDs, slow-request logging, structured log fields, and optional Prometheus metrics. Use when: hardening logging for production, adding request tracing or correlation IDs, setting up slow-request alerts, adding a /metrics endpoint, or improving structured log output beyond the base middleware.
Also in 3 projects that use this
mmondoraSkillinfrastructure-as-code
Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.
Also in 3 projects that use this
OpenAISkilldesign-qa
Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to audit.
Also in 3 projects that use this
Sagargupta16Skillupgrade-dependencies
Upgrade a project's dependencies one at a time, running the test suite after each bump and reverting the ones that break it. Use it during routine dependency maintenance, when a batch of updates has accumulated; before a major release, to go into it on current and patched dependencies; when Renovate or Dependabot PRs have piled up and you want them resolved locally in one sitting; when a security advisory means you need the patched version in, and you need to know what it breaks.
Also in 3 projects that use this
Other versions55 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 55
- me2resh/apexyard★ 542same name
- github/replica★ 230same name
- cuellarfr/design-skills★ 94same name
- adityareddy-dev/deskstudio★ 43same name
- launchapp-dev/animus-cli★ 39same name
- kumaran-is/claude-code-onboarding★ 35same name
- 5throck/ai-workspace-standards★ 25same name
- Indium-AI-Labs/indium-agentkit★ 18same name
- Ionate-Technologies/indium-agentkit★ 17same name
- ishandutta2007/Awesome-Claude-Skills★ 16same name
45 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- api-test-generatorSkill
- automation-code-reviewSkill
- bug-report-writerSkill
- ci-cd-and-test-dataSkill
- device-cloud-setupSkill
- flaky-test-triageSkill
- framework-scaffolderSkill
- greenbuild-getting-startedSkill
- llm-app-testingSkill
- mobile-automationSkill
- performance-test-starterSkill
- regression-health-digestSkill
- release-readiness-checklistSkill
- test-plan-from-requirementsSkill
- tools-and-librariesSkill
- visual-testingSkill
The file
Files
Accessibility audit
- Scope: the pages and states (modals, errors, logged in), plus the target level (default WCAG 2.1/2.2 AA).
- Playwright TS (
npm i -D @axe-core/playwright):
import AxeBuilder from '@axe-core/playwright';
test('home is accessible', async ({ page }) => {
await page.goto('/');
const r = await new AxeBuilder({ page })
.withTags(['wcag2a','wcag2aa','wcag21a','wcag21aa'])
.exclude('#third-party-widget').analyze();
expect(r.violations).toEqual([]);
});- Python options:
axe-playwright-python(Playwright) oraxe-selenium-python(Selenium). Cypress:cypress-axe(cy.injectAxe(); cy.checkA11y()). - Triage each violation by rule id, impact (critical/serious/moderate/minor), the affected nodes and the fix hint. Group violations by component, because one fix in a shared component often clears dozens.
- Gate CI on critical and serious violations first. Keep a dated baseline for the rest and burn it down instead of ignoring it.
- Automation catches only part of WCAG. Always add manual checks: keyboard-only navigation and focus order, visible focus, screen reader pass (NVDA/VoiceOver), zoom to 200% and reflow at 320px, meaningful alt text and link text, captions, and errors announced.
- Output: a summary table (rule | impact | count | pages | fix), a manual checklist, and a suggested test to add.
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
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.

