gaia-a11y-testing

Generate WCAG 2.1 accessibility test plans with automated and manual checks.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-a11y-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-a11y-testing
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-a11y-testing
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-a11y-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Accessibility testing and conformance planning are time-consuming and error-prone when done ad hoc; this Skill provides a structured approach to create WCAG 2.1 AA compliant test plans, automate checks, and produce traceable artifacts.

Core Features & Use Cases

  • Automated planning: outlines automated checks (axe-core, pa11y) and manual procedures (keyboard navigation, screen reader testing) for projects.
  • Artifact generation: outputs a comprehensive accessibility report and accompanying artifacts to a predictable path.
  • Knowledge-driven: reuses knowledge fragments (wcag checks, axe-core patterns) to guide testing and remediation priorities.

Quick Start

Provide a story key or project context to generate the initial WCAG 2.1 AA accessibility test plan.

Frequently Asked Questions about gaia-a11y-testing

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

FAQPage Schema
How do I generate a WCAG 2.1 accessibility test plan for my project?

To generate a WCAG 2.1 accessibility test plan, provide your project context or story key to produce automated checks for axe-core and pa11y, manual procedures like keyboard navigation, and a prioritized remediation report.

What is included in a WCAG 2.1 AA accessibility audit?

A WCAG 2.1 AA accessibility audit includes automated checks using axe-core and pa11y, manual testing procedures for keyboard navigation and screen readers, ARIA audits, and a written remediation prioritization report.

How do I automate pa11y and axe-core checks for accessibility compliance?

Automate pa11y and axe-core checks by configuring a structured test plan that executes automated validations, performs ARIA audits, and outputs traceable artifacts to a predictable project path.

Does automated accessibility testing cover screen reader and keyboard navigation checks?

Automated accessibility testing covers axe-core and pa11y validations, but screen reader usage and keyboard navigation checks require manual testing procedures outlined within the generated WCAG 2.1 compliant test plan.

What's the best way to prioritize accessibility remediation for ARIA audits?

Prioritize accessibility remediation for ARIA audits by generating a WCAG 2.1 AA compliant test plan that integrates knowledge fragments to guide testing and produce a structured remediation prioritization report.

Can I reuse WCAG check patterns across different accessibility testing projects?

Yes, you can reuse WCAG check patterns and axe-core patterns across projects because the testing process integrates knowledge fragments to guide testing, enforce configuration, and ensure repeatable results.