a11y-validator

Re-run accessibility tests and verify acceptance criteria against magentaa11y-mcp.

1|Updated Dec 17, 2025

Search Tags:#testing #accessibility #a11y #QA #validate #acceptance-criteria #magentaa11y-mcp

Ready to run

npx skills add https://github.com/joe-watkins/a11y-devkit --skill a11y-validator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: a11y-validator
Source: https://github.com/joe-watkins/a11y-devkit/tree/main/packages/a11y-validator
Command: npx skills add https://github.com/joe-watkins/a11y-devkit --skill a11y-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps QA and development teams confirm that accessibility fixes actually resolve reported issues and align with acceptance criteria, reducing regression risk.

Core Features & Use Cases

Re-run accessibility tests after fixes using a11y-tester to verify current violations are resolved.
Acceptance criteria verification by querying magentaa11y-mcp to obtain component criteria and ensure compliance.
Audit-ready results categorizing outcomes as fixed, needs-manual, or still-failing for traceable reporting.

Quick Start

Apply fixes to the codebase, then run the a11y-validator workflow to re-test and verify acceptance criteria against magentaa11y-mcp.

Frequently Asked Questions about a11y-validator

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

FAQPage Schema

How do I verify accessibility fixes after updating my code?▼

To verify accessibility fixes, re-run automated testing on the post-fix code to confirm reported violations are resolved. You can validate the updated components against acceptance criteria to generate audit-ready results categorizing issues as fixed, needs-manual, or still-failing.

What is the best way to confirm a11y compliance for QA auditing?▼

The best way to confirm a11y compliance for auditing is to re-test post-fix code and query component acceptance criteria. This generates structured audit-ready reporting that categorizes each accessibility outcome as fixed, needs-manual, or still-failing.

Does the a11y-validator check acceptance criteria automatically?▼

Yes, the a11y-validator checks acceptance criteria automatically by querying magentaa11y-mcp to obtain component criteria. It re-tests your post-fix code with a11y-tester to ensure the implementation aligns with required accessibility compliance standards.

Can I use automated accessibility testing for post-fix validation?▼

Yes, you can use automated accessibility testing for post-fix validation by re-running tests on the updated codebase. This workflow verifies that previously reported violations are resolved and outputs structured results detailing any unresolved or manual issues.

Why are some accessibility issues marked as needs-manual after re-testing?▼

Accessibility issues are marked as needs-manual after re-testing when automated checks cannot fully verify the resolution. The validator outputs these structured audit results to indicate issues requiring human review alongside fixed or still-failing items.