accessibility-testing

Automates WCAG 2.2 compliance checks using axe-core and Playwright with manual keyboard/screen-reader testing for QA processes.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/JaiminVadadoriya/Distributed-Cloud-Storage---Sync-Platform --skill accessibility-testing-jaiminvadadoriya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-testing
Source: https://github.com/JaiminVadadoriya/Distributed-Cloud-Storage---Sync-Platform/tree/main/.agents/skills/accessibility-testing
Command: npx skills add https://github.com/JaiminVadadoriya/Distributed-Cloud-Storage---Sync-Platform --skill accessibility-testing-jaiminvadadoriya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @axe-core/playwright, playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring software accessibility compliance by automating tests against the WCAG 2.2 standards, streamlining the process of making digital products usable for all users.

Core Features & Use Cases

  • Automated and Manual Testing: Combines automated testing with axe-core and manual keyboard and screen reader tests for comprehensive coverage.
  • WCAG 2.2 Compliance: Checks for compliance with accessibility guidelines to meet legal requirements and provide an inclusive user experience.
  • Use Case: Use this Skill to run automated tests on a new feature and manually test it for accessibility, ensuring it meets accessibility standards and regulations.

Quick Start

Run the accessibility-testing skill on the current page to identify and fix accessibility issues.

Frequently Asked Questions about accessibility-testing

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

FAQPage Schema
How do I automate accessibility testing for WCAG 2.2 compliance?

Automate accessibility testing for WCAG 2.2 compliance by running axe-core checks via Playwright to identify violations, then manually test keyboard and screen reader interactions for comprehensive coverage.

What's the best way to run automated and manual screen reader tests?

The best way to run screen reader tests is combining automated axe-core checks through Playwright to catch programmatic violations with manual keyboard and screen reader testing for full WCAG conformance.

Does Playwright work with axe-core for ARIA and accessibility checks?

Yes, Playwright works with axe-core to perform automated accessibility checks, validating ARIA roles and WCAG 2.2 compliance directly within your QA automation scripts.

Why do automated accessibility tests need manual keyboard testing?

Automated accessibility tests need manual keyboard testing because axe-core catches programmatic violations, but manual testing is required to validate actual screen reader behavior and keyboard navigation for complete WCAG conformance.

Can I use this for QA processes to ensure software meets legal accessibility standards?

Yes, you can use this for QA processes to ensure software meets legal accessibility standards by verifying WCAG 2.2 compliance through combined automated testing and manual screen reader validation.

What are the limitations of automated accessibility testing for WCAG conformance?

The limitation of automated accessibility testing is that axe-core cannot verify actual user experience, requiring manual keyboard and screen reader tests to achieve full WCAG conformance and ensure inclusive software.