evinced-web-sdk

Integrate Evinced SDK accessibility scanning into Playwright test suites.

5|Updated Mar 11, 2026

Search Tags:#automation #testing #accessibility #wcag #playwright #web sdk

Ready to run

npx skills add https://github.com/SteveFeldman/agents-skills --skill evinced-web-sdk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evinced-web-sdk
Source: https://github.com/SteveFeldman/agents-skills/tree/main/skills/evinced-web-sdk
Command: npx skills add https://github.com/SteveFeldman/agents-skills --skill evinced-web-sdk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @evinced/js-playwright-sdk, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill integrates automated accessibility scanning into your existing Playwright test suite, ensuring WCAG compliance and identifying critical issues before they reach users.

Core Features & Use Cases

Automated Accessibility Scanning: Leverages the Evinced SDK to scan web pages for accessibility violations.
Playwright Integration: Seamlessly adds accessibility checks to your current Playwright scripts.
WCAG Compliance: Helps meet Web Content Accessibility Guidelines standards.
Use Case: Integrate this skill into your CI/CD pipeline to automatically flag accessibility bugs in new features during automated testing.

Quick Start

Add the --evinced and --upload=TRUE flags to your Playwright command to enable Evinced scanning and platform upload.

Frequently Asked Questions about evinced-web-sdk

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

FAQPage Schema

How do I add automated accessibility scanning to my Playwright test suite?▼

You can integrate automated accessibility scanning into your Playwright test suite using the Evinced Web SDK to check for WCAG compliance and identify accessibility violations during browser tests.

What is the best way to automate WCAG compliance checks during web testing?▼

Automating WCAG compliance checks is best handled by integrating an accessibility SDK into your existing Playwright test framework to flag critical web accessibility issues before deployment.

Do I need the Evinced js-playwright-sdk to run web accessibility tests?▼

Yes, you need the @evinced/js-playwright-sdk dependency and Playwright version 1.25 or higher to run automated web accessibility scanning within your test suites.

Can I use automated accessibility scanning in my CI/CD pipeline?▼

Yes, you can integrate this accessibility scanning into your CI/CD pipeline by adding specific Evinced runtime flags to your Playwright commands to automatically flag accessibility bugs in new features.

How does the Evinced Web SDK identify accessibility issues?▼

The Evinced Web SDK identifies accessibility issues by leveraging the Evinced platform to scan web pages actively during automated Playwright browser testing and reporting violations against WCAG standards.

What are the limitations of using Evinced for Playwright accessibility testing?▼

Evinced accessibility testing is limited to the Playwright framework environment, requiring Playwright 1.25+ and the specific js-playwright-sdk, meaning it cannot scan web pages outside of automated browser test executions.