Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From ultraship
Audits static HTML for WCAG 2.2 A/AA failures (alt text, labels, keyboard, structure) and auto-fixes deterministic issues. Escalates to rendered scan for contrast and focus.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ultraship:a11y <url-or-directory><url-or-directory>**/*.html**/*.htm**/index.htmlThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
AI builders ship accessibility violations by default — missing alt text, unlabeled inputs, icon-only buttons, no `lang`, broken heading order. These are legally consequential (ADA, EU Accessibility Act) and most are deterministically detectable and fixable. This skill finds them AND fixes them.
AI builders ship accessibility violations by default — missing alt text, unlabeled inputs, icon-only buttons, no lang, broken heading order. These are legally consequential (ADA, EU Accessibility Act) and most are deterministically detectable and fixable. This skill finds them AND fixes them.
Run the static scanner on the project (point it at built/exported HTML, e.g. dist/, build/, out/, .next/, or public/):
node ${CLAUDE_PLUGIN_ROOT}/tools/a11y-scanner.mjs <project-directory>
Parse the JSON: findings[] ({ file, severity, category, rule, message }), summary (counts by severity), and scores.a11y (0–100, or null when no HTML found).
Many pages, each needing fixes? Escalate to a dynamic Workflow (describe the audit and include the word "workflow") so scan → fix → verify runs across pages in parallel instead of one at a time.
Present findings grouped by rule, highest severity first. Map each to its WCAG criterion (already in the message). Make clear which are auto-fixable now vs which need a rendered scan (Phase 4).
Apply the deterministic fix for each finding. Do not invent content — for alt text and labels, derive from nearby context (filename, heading, surrounding copy, name/placeholder); if genuinely ambiguous, ask the user rather than guessing.
| Rule | Fix |
|---|---|
html-missing-lang / html-empty-lang | Add lang="en" (or the document's real language) to <html> |
img-missing-alt | Add alt="<concise description>" from context; use alt="" only if the image is purely decorative |
input-image-missing-alt | Add alt="<what the button does>" |
control-missing-label | Add a <label for="id">, or aria-label/aria-labelledby. A placeholder is NOT a label — keep it but add a real label |
button-no-text | Add visible text, or aria-label="<action>" for icon-only buttons |
link-no-text | Add link text, or aria-label; if it wraps an icon, give the icon alt/aria-label |
link-generic-text | Rewrite "click here"/"read more" to state the destination ("Read the pricing guide") |
positive-tabindex | Change to tabindex="0" (or remove) and fix order via DOM order |
viewport-zoom-disabled | Remove user-scalable=no / maximum-scale=1 from the viewport meta |
duplicate-id | Make each id unique (and update its label/aria references) |
broken-aria-reference | Point aria-labelledby/aria-describedby/for at a real element id, or add the missing element |
empty-heading | Remove the empty heading or give it text |
heading-skip | Insert the missing level or demote the heading so levels don't jump |
missing-title | Add a descriptive <title> in <head> |
missing-main-landmark | Wrap the primary content in <main> |
The static scanner cannot see computed styles or focus behavior. When a URL or running dev server is available, run a rendered audit — these tools need no install (npx fetches them) and cover color contrast (WCAG 1.4.3), focus visibility, and ARIA state:
# Pa11y (axe + htmlcs runners). Use --runner axe for axe-core rules.
npx --yes pa11y --standard WCAG2AA <url>
# or the axe CLI directly
npx --yes @axe-core/cli <url>
If the project uses Playwright (Ultraship bundles the Playwright MCP), prefer injecting axe-core into the live page for per-component results. Report contrast and focus findings the static pass could not catch.
Re-run the scanner and report before/after scores.a11y:
node ${CLAUDE_PLUGIN_ROOT}/tools/a11y-scanner.mjs <project-directory>
node ${CLAUDE_PLUGIN_ROOT}/tools/audit-history.mjs save <project-dir> a11y <score>
alt="" is correct for decorative images — don't add fake descriptions to them.npx claudepluginhub houseofmvps/ultraship --plugin ultrashipAudits and fixes WCAG 2.2 accessibility issues. Report mode: sweep codebase/page for prioritized report. Fix mode: audit-edit-verify loop. Prefers live-DOM via CDP, falls back to browser-MCP or HTML-string audits.
Audits web projects for WCAG 2.2 AA accessibility gaps in HTML, React/TSX, Vue, Svelte components, CSS, and templates. Prioritizes issues by user impact and recommends fixes without code changes.