accessibility-auditor

Audit web applications for WCAG 2.2 compliance with axe-core scans and manual checks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/phishkatlabs/phishkat-crew --skill accessibility-auditor-phishkatlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-auditor
Source: https://github.com/phishkatlabs/phishkat-crew/tree/main/accessibility-auditor
Command: npx skills add https://github.com/phishkatlabs/phishkat-crew --skill accessibility-auditor-phishkatlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits web applications for WCAG 2.2 compliance across interfaces by combining automated axe-core scans with expert manual evaluation, ensuring accessible products and compliance with legal and usability standards.

Core Features & Use Cases

  • Automated WCAG 2.2 scans using axe-core across all routes
  • Manual heuristics, keyboard-navigation checks, and color-contrast reviews
  • Comprehensive reporting with remediation guidance, audit artifacts, and CI-ready hooks

Quick Start

Run a full WCAG 2.2 accessibility audit across all routes with automated axe-core checks and targeted manual evaluations.

Frequently Asked Questions about accessibility-auditor

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

FAQPage Schema
How do I run a WCAG 2.2 accessibility audit on my web application?

Run a WCAG 2.2 accessibility audit using automated axe-core scans across all routes combined with manual keyboard-navigation, color-contrast, and ARIA checks to produce comprehensive reports and CI-ready hooks.

What does automated axe-core scanning check for in WCAG compliance?

Automated axe-core scanning checks WCAG 2.2 compliance by evaluating ARIA semantics, color contrast, and focus management across application routes to identify accessibility violations quickly.

Can I automate keyboard navigation and focus testing for SaaS dashboards?

Yes, you can automate keyboard navigation and focus testing for SaaS dashboards by running Playwright checks to validate tab order, focus visibility, and keyboard traps, ensuring WCAG 2.2 compliance.

How do I validate ARIA attributes and screen reader compatibility?

Validate ARIA attributes and screen reader compatibility by running automated axe-core scans combined with manual heuristics to verify correct ARIA semantics, focus management, and screen reader interactions across interfaces.

Does this approach work for internal tools and marketing sites?

Yes, this approach works for internal tools and marketing sites by applying WCAG 2.2 audits across diverse interfaces, covering keyboard navigation, screen reader compatibility, color contrast, and ARIA semantics.

What's the best way to generate CI-ready accessibility tests and bug templates?

Generate CI-ready accessibility tests and bug templates by running axe-core scans and manual evaluations, producing comprehensive reports with remediation guidance and audit artifacts for pipeline integration.