From naksha
Runs a full WCAG AA accessibility audit on an HTML file — checks contrast ratios, keyboard navigation, semantic HTML, ARIA usage, touch targets, and label associations.
How this command is triggered — by the user, by Claude, or both
Slash command
/naksha:accessibility-audit <file>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /accessibility-audit
Read and follow all instructions in `${CLAUDE_PLUGIN_ROOT}/agents/accessibility-auditor.md`.
Input: **$ARGUMENTS**Read and follow all instructions in ${CLAUDE_PLUGIN_ROOT}/agents/accessibility-auditor.md.
Input: $ARGUMENTS
npx claudepluginhub adityaraj0421/naksha-studio --plugin naksha/ux-a11yRuns a structured WCAG 2.1 AA accessibility audit on a URL, file, or screenshot. Checks contrast, keyboard navigation, focus, ARIA, screen reader support, and motion preferences, then produces a grouped findings report with severity, evidence, and fixes.
/run-auditRuns WCAG 2.1 accessibility audit (AA default) on a URL or component via axe-core and manual checks for keyboard nav, ARIA, contrast, forms, media. Outputs prioritized report with remediation.
/accessibility-auditAudits UI code for WCAG 2.1/2.2 compliance at A/AA/AAA level, identifies issues across perceivable/operable/etc. criteria, and provides remediation. Accepts file/component path or prompts for target.
/a11y-auditAudits accessibility for live URLs, UI components, or screenshots against WCAG A/AA/AAA standards, generating a markdown report with tiered issues and fixes.
/a11y-scanScans pages or components for WCAG 2.1/2.2 accessibility issues, ARIA errors, keyboard navigation, screen reader compatibility, and color contrast. Produces markdown audit report with prioritized fixes and code examples.