Deep accessibility scorecard for a single Figma component or component set — state coverage (default/hover/focus/disabled/error/active/loading), focus-indicator quality and contrast, non-color state differentiation, target size, annotation completeness, and color-blind simulation (protanopia/deuteranopia/tritanopia), all rolled into per-category 0–100 scores and prioritized recommendations. Use when the user wants to vet ONE component before shipping it: triggers 'audit this component', 'access…
Deep accessibility scorecard for a single Figma component or component set — state coverage (default/hover/focus/disabled/error/active/loading), focus-indicator quality and contrast, non-color state differentiation, target size, annotation completeness, and color-blind simulation (protanopia/deuteranopia/tritanopia), all rolled into per-category 0–100 scores and prioritized recommendations.
Use when the user wants to vet ONE component before shipping it: triggers 'audit this component', 'accessibility score for this button', 'is this component set accessible', 'check the states on this component', 'does my button have a focus state', 'color blind check', 'rate this component for a11y', 'component accessibility scorecard'.
Works on ANY Figma plan.
For a broad sweep over a whole page/frame use figma-lint-design; for CODE-side (HTML) checks use figma-scan-code-accessibility.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Run a deep accessibility audit on a single component or component set and get a weighted 0–100 scorecard with prioritized fixes. Where figma-lint-design sweeps a whole tree for many rule violations, this skill goes deep on one component: it understands variant axes, classifies the component as interactive vs presentational, and scores each a11y dimension accordingly.
All via use_figma, on any plan — it inspects the real variant tree, fills, strokes, effects, and the component description.
Skill boundaries
use_figma rules — load the official figma-use skill first; it is the full Figma Plugin API reference. Essentials these scripts rely on: plain JS with top-level await + return (no IIFE, no figma.closePlugin(); console.log is not returned), inputs inlined as const at the top of each script, colors in 0–1 range, load fonts before any text op, await figma.getNodeByIdAsync(...), and atomic errors (a failed script applies nothing — read the error, fix, retry).
Tree-wide WCAG + design-system lint → use figma-lint-design.
CODE-side a11y (axe-core over HTML) → use figma-scan-code-accessibility.
Design-vs-code drift → use figma-check-design-parity.
Workflow
Target a component. Set NODEID to a COMPONENTSET, COMPONENT, or INSTANCE id (the script
walks INSTANCE → main component → parent set automatically). Leave it null to audit the current single selection.
Set the tap-target minimum.TARGET_SIZE defaults to 24 (WCAG 2.5.8 minimum); pass 44 or 48
for stricter mobile targets.
Run [scripts/audit-accessibility.js](scripts/audit-accessibility.js) via use_figma
(skillNames: "figma-audit-accessibility").
Read the scorecard.overallScore is a classification-weighted blend of the six category
scores. See [references/audit-categories.md](references/audit-categories.md) for each category, its weight, and how to raise it.
Work the recommendations.recommendations[] is already sorted by priority
(high/medium/low) with the WCAG SC named. Fix, then re-run to confirm the score moved.
Key rules
Interactive vs presentational is auto-detected from the component name and variant axes. It
changes which categories are scored and their weights — a badge is not penalized for lacking a focus state; a button is.
