Is Accessibility Audit safe and trustworthy?

tashan scores Accessibility Audit on public evidence — tashan score 48.0/100, it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Accessibility Audit?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Accessibility Audit?

3 GitHub contributors, source: VilnaCRM-Org/claude-plugins.

‹ The Index

Accessibility Audit

skill

- Adversarial, authorized accessibility deep-audit loop for a React frontend you own — fans out one accessibility-auditor subagent per WCAG 2.2 principle / a11y family in parallel, each probing the RUNNING stack (axe-core on the rendered DOM, keyboard-only traversal, and accessibility-tree / accessible-name / screen-reader semantic checks) AND inspecting the JSX/ARIA source (jsx-a11y lint, semantic-HTML + ARIA-pattern audit), verifies every candidate by reproducing the barrier against the running stack (no false positives), maps it to a WCAG 2.2 Success Criterion + conformance level + severity band, then drives root-cause, suppression-free fixes through react-implementer with a. …

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Dev Tools & CI — see all ranked ›

Install (Claude Code):

cp -r accessibility-audit ~/.claude/skills/

tashan score: 48.0
Adoption: 2 repos
Upkeep: 95.0
Freshness: 90.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 3

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when to use it, shows worked examples, covers setup and states a limitation.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Accessibility Audit scores 48 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/skill-vilnacrm-org-accessibility-audit.svg)](https://tashan.sh/capability/skill-vilnacrm-org-accessibility-audit.html)

source ↗ · skill:VilnaCRM-Org/accessibility-audit

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-08-20 · scorer s5 · how · something wrong here?