a11y

Detect and fix deterministic WCAG 2.2 A/AA accessibility violations in HTML files.

115|13|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Houseofmvps/ultraship --skill a11y-houseofmvps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y
Source: https://github.com/Houseofmvps/ultraship/tree/main/skills/a11y
Command: npx skills add https://github.com/Houseofmvps/ultraship --skill a11y-houseofmvps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping web products with unaddressed accessibility violations exposes teams to legal risk under regulations like the ADA and EU Accessibility Act, while excluding users with disabilities from accessing your content. Most common accessibility failures are deterministic and can be automatically detected and fixed before launch.

Core Features & Use Cases

  • Static HTML Scanning: Detects common structural and labeling issues like missing alt text, unlabeled form inputs, broken heading order, and duplicate IDs in built/static HTML files.
  • Deterministic Auto-Fix: Automatically applies safe, context-aware fixes for flagged issues without inventing content, asking for clarification only when alt text or labels are genuinely ambiguous.
  • Rendered Audit Escalation: For issues that require computed style or interaction checks (like color contrast and focus visibility), escalates to a live browser scan using industry-standard tools.
  • Use Case: A frontend developer preparing a new marketing site for launch can use this skill to catch and fix all accessibility gaps in one workflow, avoiding costly post-launch retrofits and compliance penalties.

Quick Start

Use the a11y skill to scan your project's built HTML files for accessibility issues and automatically apply fixes to all deterministic WCAG 2.2 violations.

Frequently Asked Questions about a11y

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit and fix WCAG 2.2 accessibility issues in my HTML before launch?

You can audit and automatically fix WCAG 2.2 A/AA accessibility violations by scanning built static HTML files for structural issues like missing alt text, unlabeled form inputs, and broken heading order, then applying safe context-aware fixes automatically.

What is the best way to check color contrast and focus visibility for web accessibility compliance?

Checking color contrast and focus visibility requires a rendered browser audit that evaluates computed styles and interaction failures, escalating beyond static HTML scanning to ensure full WCAG compliance coverage for your web project.

Can I automatically fix all detected WCAG violations without manually writing alt text or labels?

You can automatically fix deterministic WCAG violations without manual input, but the tool will ask for clarification only when alt text or labels are genuinely ambiguous to avoid inventing content.

Do I need rendered browser access to detect semantic structure and keyboard navigation issues?

You do not need rendered browser access for semantic structure and keyboard navigation checks; static source code scanning detects broken heading order, duplicate IDs, and labeling issues directly in built HTML files.

Why does my accessibility audit only find structural HTML issues and miss screen reader compatibility failures?

Accessibility audits miss screen reader compatibility failures when only static scanning is used; detecting computed style and interaction failures requires escalating to a live browser scan for full WCAG compliance coverage.