specimin-ui-accessibility

Audit and fix generated UI code for WCAG 2.1 AA compliance.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/timsvoice/specimin --skill specimin-ui-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specimin-ui-accessibility
Source: https://github.com/timsvoice/specimin/tree/main/.claude-plugin/skills/specimin-ui-accessibility
Command: npx skills add https://github.com/timsvoice/specimin --skill specimin-ui-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

Systematically improves generated UI code for WCAG 2.1 AA compliance, catching many accessibility issues automatically while mandating manual validation.

Core Features & Use Cases

  • Automated audit: fix semantic HTML, ARIA usage, keyboard navigation, and focus management.
  • Manual testing checklist: provides a comprehensive QA checklist that must be completed by humans.
  • Reporting: produces an accessibility report and integrates with the feature directory.

Quick Start

After UI code generation, run the accessibility agent and complete the mandatory manual testing checklist.

Frequently Asked Questions about specimin-ui-accessibility

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

FAQPage Schema
How do I ensure AI-generated UI code meets WCAG 2.1 AA compliance?

WCAG 2.1 AA compliance for generated UI requires automated audits of semantic HTML, ARIA attributes, keyboard navigation, and focus management, followed by manual validation. This Skill performs structured semantic HTML audits and produces an accessibility report with a mandatory QA checklist to catch issues automation cannot detect alone.

Can I automate accessibility checks for generated components?

Yes. Automated accessibility audits fix semantic HTML, validate ARIA usage, check keyboard navigation, and verify focus management in generated UI components. However, full accessibility validation requires completing a mandatory manual testing checklist, since automated tools cannot verify all user experience aspects.

What does a semantic HTML audit check in accessibility review?

A semantic HTML audit verifies proper landmark usage, navigation structure, form control labeling, and heading hierarchy in your code. This Skill enforces semantic HTML where possible and applies ARIA attributes only when necessary to improve accessibility of AI-generated UI code.

How do I test keyboard navigation and focus management in my UI?

Keyboard accessibility testing verifies all interactive elements are reachable and operable via keyboard, and focus moves predictably through the interface. This Skill includes automated checks for keyboard navigation and focus management, plus a comprehensive manual testing checklist you must complete to validate real-world keyboard usability.

Do I need manual testing after automated accessibility fixes?

Yes. Automated audits catch many issues, but accessibility requires human validation with assistive technologies and manual keyboard testing. This Skill enforces a mandatory manual testing checklist alongside automated fixes to ensure generated components are truly accessible.

What output do I get after running an accessibility review?

You receive an accessibility report documenting all fixes applied, a mandatory QA testing checklist, and corrected code on your feature branch. The report covers WCAG 2.1 AA compliance status, semantic HTML improvements, ARIA implementations, and keyboard navigation fixes.