accessibility-skill
This skill brings accessibility testing capabilities directly into your automation framework, letting you scan for WCAG violations and usability barriers without leaving your test suite. Built by TestMu AI, it streamlines compliance validation by embedding accessibility checks into existing test pipelines.
accessibility-skill integrates directly into your existing test automation framework—Selenium, Playwright, or Cypress—so you can embed accessibility checks without switching tools. Simply add accessibility-skill scanning calls to your test steps, and it will validate WCAG compliance as part of your normal test execution. This approach lets you catch accessibility violations early in your development cycle while keeping all your tests in one place.
AI-generated summary based on this skill's SKILL.md
Install
LambdaTest/agent-skills/accessibility-skill · repository language: Python
git clone https://github.com/LambdaTest/agent-skills
cp -r agent-skills/accessibility-skill ~/.claude/skills/accessibility-skillFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I add accessibility testing to my test suite?
accessibility-skill integrates directly into your existing test automation framework—Selenium, Playwright, or Cypress—so you can embed accessibility checks without switching tools. Simply add accessibility-skill scanning calls to your test steps, and it will validate WCAG compliance as part of your normal test execution. This approach lets you catch accessibility violations early in your development cycle while keeping all your tests in one place.
Can accessibility-skill verify WCAG 2.1 compliance across web and mobile applications?
Yes. accessibility-skill is designed to verify WCAG 2.1 compliance across both web and mobile applications. It works with your existing test automation setup—whether you're using Selenium for web testing, Playwright for cross-browser scenarios, or Cypress for modern web apps—and can also integrate with Appium for mobile testing. This framework-agnostic approach means you can validate accessibility standards consistently across your entire application portfolio.
How can I integrate accessibility-skill with Playwright?
accessibility-skill enables accessibility scans in Playwright by providing API calls you can insert into your test code. After setting up accessibility-skill in your project, you add scanning directives to your Playwright test steps to check for accessibility issues at key points in your user flows. The skill then returns compliance data that you can assert on or log, making accessibility validation a native part of your Playwright test suite.
Can I generate and retrieve accessibility audit reports programmatically?
accessibility-skill supports programmatic access to accessibility audit results through its API. You can retrieve scan results, filter by severity level, and integrate the data into your reporting pipeline or dashboard. This capability lets you automate compliance tracking, feed accessibility metrics into your CI/CD pipeline, and generate audit reports without manual intervention.
What makes accessibility-skill framework-agnostic for automated a11y testing?
accessibility-skill works with Selenium, Playwright, Cypress, and Appium because it operates as a testing capability layer rather than a standalone tool. Instead of forcing you to adopt a new testing framework, accessibility-skill embeds accessibility scanning into the automation framework you already use. This design means your team can validate WCAG compliance using familiar tools and workflows, reducing training overhead and integration complexity.
How do I configure accessibility scanning rules and severity levels in accessibility-skill?
accessibility-skill allows you to configure which accessibility rules to enforce and set severity thresholds for your scans. You can customize rule sets to match your organization's compliance requirements, adjust severity levels to focus on critical issues first, and tailor the scanning behavior to your application's specific needs. This flexibility ensures accessibility-skill adapts to your compliance strategy rather than imposing a one-size-fits-all approach.
SKILL.md
rendered from the published skill — quoted content, verbatim
Accessibility Testing Skill
Accessibility testing on TestMu AI is layered onto an existing automation suite. You do not install a separate tool: you enable a capability on your driver and either trigger scans at chosen points or let every navigation scan automatically. Results appear on the Accessibility dashboard.
Know the one hard limit up front: the automation capabilities can start a scan, but there is no results API, no exit code, and no build-gating flag. To read a report back programmatically (for example, to fail a build), use the
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
accessibility-skill/SKILL.md
accessibility-skill/reference/playbook.md