team-visual-a11y

Orchestrate visual accessibility QA workflows with WCAG mapping and fix verification.

76|5|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catlog22/pi-maestro-flow --skill team-visual-a11y-catlog22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-visual-a11y
Source: https://github.com/catlog22/pi-maestro-flow/tree/main/.pi/skills/team-visual-a11y
Command: npx skills add https://github.com/catlog22/pi-maestro-flow --skill team-visual-a11y-catlog22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns a manual accessibility review into a coordinated QA workflow, helping teams find contrast, typography, keyboard, and ARIA issues that are hard to catch reliably in a single pass.

Core Features & Use Cases

  • Parallel auditing: Runs color, typography, and focus checks at the same time so issues are discovered faster and with clearer ownership.
  • Remediation planning: Consolidates audit findings into a prioritized fix plan with WCAG mappings and code-level guidance.
  • Fix verification: Supports implementation follow-up and re-audit loops to confirm that accessibility fixes actually work in rendered UI.
  • Use case: A product team can audit a page, generate a remediation backlog, apply fixes, and then verify keyboard focus, color contrast, and text readability after changes.

Quick Start

Ask the skill to audit the target page or component for visual accessibility and tell it whether you want audit-only or full fix-and-verify mode.

Frequently Asked Questions about team-visual-a11y

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

FAQPage Schema
How do I run a WCAG accessibility audit for contrast, keyboard navigation, and ARIA on a web page?

A WCAG accessibility audit evaluates rendered interfaces for contrast, typography, keyboard navigation, focus visibility, skip links, ARIA, and target-size compliance. This Skill coordinates that visual accessibility QA workflow, running parallel checks across multiple roles to map issues to WCAG standards and generate actionable reports.

What's the best way to verify accessibility fixes after remediating contrast and ARIA issues?

Verifying accessibility fixes requires a re-audit loop on the rendered UI. This Skill supports fix verification by re-running visual checks for keyboard focus, color contrast, and text readability after code changes are applied, confirming that remediation actually meets WCAG standards.

Can I use this accessibility audit workflow for both source components and fully rendered interfaces?

Yes, the visual accessibility audit workflow applies to both rendered interfaces and source components. It executes coordinated multi-role checks for typography, focus management, and ARIA mapping across audit, remediation, and re-audit scenarios for either target type.

How do I generate a prioritized remediation plan with WCAG mappings from accessibility audit findings?

Generating a prioritized fix plan involves consolidating audit findings into a backlog with WCAG mappings and code-level guidance. This Skill automates that remediation planning step, translating parallel visual audit results into an actionable, prioritized list of accessibility fixes for the development team.

Does parallel accessibility auditing actually find keyboard and focus management issues faster than a single pass?

Parallel auditing runs color, typography, and focus checks simultaneously rather than sequentially. This coordinated visual accessibility workflow assigns clear ownership and discovers contrast, keyboard navigation, and ARIA issues faster and more reliably than a manual single-pass review.