accessibility-compliance-accessibility-audit

Audit web interfaces for WCAG compliance using automated scans and manual testing checklists.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Eng-suso/BK-GPT --skill accessibility-compliance-accessibility-audit-eng-suso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-compliance-accessibility-audit
Source: https://github.com/Eng-suso/BK-GPT/tree/main/.claude/skills/accessibility-compliance-accessibility-audit
Command: npx skills add https://github.com/Eng-suso/BK-GPT --skill accessibility-compliance-accessibility-audit-eng-suso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Digital products often contain accessibility barriers that exclude users with disabilities and create legal compliance risk. This Skill provides a structured audit workflow that identifies WCAG violations, maps them to severity and user impact, and delivers concrete remediation guidance. ## Core Features & Use Cases - Automated Scanning: Run axe-core based audits via Puppeteer to collect baseline violations with impact scoring across WCAG 2.0/2.1 A and AA criteria. - Manual Verification: Test keyboard navigation, focus indicators, screen reader compatibility, heading structure, form labels, and color contrast against defined checklists. - Remediation & Reporting: Generate HTML audit reports with severity-ranked violations, accessible component code examples, and CI/CD integration via GitHub Actions and pa11y. - Use Case: Before launching a new checkout flow, run a full audit to detect missing form labels, insufficient contrast ratios, and keyboard traps, then re-test after fixes to produce compliance evidence for stakeholders. ## Quick Start Audit the attached page or component for WCAG 2.1 AA compliance and report violations with remediation steps.

Frequently Asked Questions about accessibility-compliance-accessibility-audit

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

FAQPage Schema
How do I run an automated WCAG accessibility audit on a web page?▼

Use axe-core with Puppeteer to load the page, run analysis filtered by wcag2a, wcag2aa, wcag21a, and wcag21aa tags, and collect violations with impact levels. The audit returns a score calculated from weighted violation severities.

What tools are used for accessibility testing in this workflow?▼

The workflow uses axe-core with Puppeteer for page scans, jest-axe for React component unit tests, and pa11y for CI/CD command-line checks against WCAG2AA. Manual checklists cover keyboard, screen reader, visual, and cognitive criteria.

Can accessibility tests run in a CI/CD pipeline?▼

Yes, the included GitHub Actions workflow builds the app, starts a local server, runs axe-based tests and pa11y with a zero-violation threshold, then uploads an HTML report as a build artifact on every push or pull request.

Why do automated accessibility scans miss some violations?▼

Automated tools cannot judge context-dependent issues like meaningful alt text quality, logical focus order, or whether error messages are actually announced. Manual testing with keyboards and screen readers is required to cover these gaps.

How do I fix color contrast failures for WCAG AA?▼

WCAG AA requires a 4.5:1 contrast ratio for normal text and 3:1 for large text. Compute the ratio from relative luminance of foreground and background colors, then adjust the palette or add high-contrast media query overrides.