accessibility-testing-specialist

Automate accessibility testing for web applications with Playwright and axe-core scans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Whaleylaw/llm-lawyer --skill accessibility-testing-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-testing-specialist
Source: https://github.com/Whaleylaw/llm-lawyer/tree/main/.claude/skills/accessibility-testing-specialist
Command: npx skills add https://github.com/Whaleylaw/llm-lawyer --skill accessibility-testing-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces manual and inconsistent accessibility checks by providing systematic guidance and test patterns to detect WCAG violations, screen reader incompatibilities, keyboard navigation failures, ARIA misconfigurations, and insufficient color contrast.

Core Features & Use Cases

  • Automated scanning guidance for integrating axe-core with Playwright or Lighthouse to detect accessibility violations across pages and components.
  • Interaction and focus tests for keyboard navigation, modal focus trapping, skip links, and returns of focus after dialogs.
  • Semantic and assistive tech checks for heading hierarchy, alt text, ARIA roles and states, live regions, and form error announcements.
  • Color contrast validation and remediation reporting to meet WCAG AA thresholds.
  • Use Case: Run CI-accessibility scans on pull requests to block regressions, export prioritized violation reports, and validate keyboard/screen reader flows before release.

Quick Start

Run an axe-core Playwright scan against the target page and return a prioritized list of WCAG violations with remediation guidance.

Frequently Asked Questions about accessibility-testing-specialist

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

FAQPage Schema
How do I automate WCAG violation detection with Playwright and axe-core?

Run an axe-core scan within your Playwright end-to-end tests to automatically detect WCAG violations, ARIA misconfigurations, and insufficient color contrast. This yields a prioritized report with actionable remediation guidance for each issue.

What is automated accessibility testing for keyboard navigation and screen reader compatibility?

Automated accessibility testing systematically checks keyboard navigation, modal focus trapping, and ARIA live regions to verify screen reader compatibility. It validates heading hierarchy and form error announcements to ensure assistive technology support.

Does this accessibility testing approach support CI integration to block regressions on pull requests?

Yes, this approach supports CI integration by running automated accessibility scans on pull requests to block regressions. It validates keyboard and screen reader flows before release and exports prioritized violation reports for focused remediation.

Can I use Lighthouse scanning to validate color contrast and meet WCAG AA thresholds?

Yes, Lighthouse scanning can validate color contrast to meet WCAG AA thresholds. The testing process generates remediation reports identifying insufficient contrast ratios and provides actionable guidance to fix color violations across web applications.

What's the best way to test ARIA roles, states, and form error announcements for screen readers?

The best way to test ARIA roles, states, and form error announcements is through semantic and assistive tech checks. This validates heading hierarchy, alt text, live regions, and error announcements to ensure screen reader compatibility.