accessibility-testing

Test web and mobile applications for WCAG 2.1/2.2 AA conformance using automated tools and manual techniques.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/a53ali/ai-dev --skill accessibility-testing-a53ali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-testing
Source: https://github.com/a53ali/ai-dev/tree/main/skills/qa/accessibility-testing
Command: npx skills add https://github.com/a53ali/ai-dev --skill accessibility-testing-a53ali

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires axe, lighthouse, pa11y, axe-core, jest-axe, playwright, pa11y-ci, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you ensure that your web and mobile applications are accessible to users with disabilities, reducing legal risk and improving user experience.

Core Features & Use Cases

  • Automated Testing: Use tools like axe, Lighthouse, and Pa11y to identify common accessibility issues.
  • Manual Testing: Perform in-depth testing with keyboard navigation, screen reader testing, and more.
  • CI Integration: Integrate accessibility checks into your continuous integration pipeline.
  • Legal Compliance: Ensure your applications meet WCAG 2.1/2.2 AA standards and legal requirements.

Quick Start

Run the accessibility-testing skill with the command 'accessibility-testing run --url https://example.com'.

Frequently Asked Questions about accessibility-testing

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

FAQPage Schema
How do I test my web application for WCAG 2.1 AA conformance?

To integrate accessibility checks into your continuous integration pipeline, you can use pa11y-ci to automate WCAG 2.1 AA testing. Running automated tools like axe and Lighthouse within CI workflows ensures ongoing web accessibility compliance and reduces legal risk.

Can I use Playwright and jest-axe together for automated accessibility testing?

Yes, you can use Playwright and jest-axe together for automated accessibility testing. Combining these tools helps identify common accessibility issues in web applications by running axe-core rules within your Playwright testing environment to verify WCAG conformance.

What is the difference between automated and manual screen reader testing?

Automated accessibility testing uses tools like axe and Pa11y to scan for common code-level issues, while manual screen reader testing verifies actual user navigation experiences. Combining both ensures comprehensive WCAG 2.1/2.2 AA conformance and legal compliance for your applications.

When do I need manual keyboard navigation testing for mobile app accessibility?

Manual keyboard navigation testing is needed when verifying mobile app accessibility beyond automated tool capabilities. It ensures real users can navigate interactive elements without a mouse, which is required for full WCAG 2.1/2.2 AA conformance and comprehensive legal compliance.

How do I run an accessibility test on a specific URL?

You can run an accessibility test on a specific URL by executing the command 'accessibility-testing run --url https://example.com'. This initiates automated WCAG 2.1/2.2 AA checks using axe, Lighthouse, and Pa11y to identify accessibility issues.