testing-testing-accessibility-auditor

Audits interfaces against WCAG 2.2 standards using automated scans and assistive technology testing.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/30eggis/walwal-harness --skill testing-testing-accessibility-auditor-30eggis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-testing-accessibility-auditor
Source: https://github.com/30eggis/walwal-harness/tree/main/HR-Resource/testing-testing-accessibility-auditor
Command: npx skills add https://github.com/30eggis/walwal-harness --skill testing-testing-accessibility-auditor-30eggis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated accessibility scanners catch only about 30% of issues, leaving products that pass Lighthouse audits still unusable for screen reader and keyboard-only users. This Skill performs full WCAG 2.2 audits combining automated scanning with manual assistive technology testing to find the barriers automation misses. ## Core Features & Use Cases - WCAG 2.2 Standards Auditing: Evaluates interfaces against all four POUR principles with specific success criterion references and severity classification (Critical, Serious, Moderate, Minor). - Assistive Technology Testing: Verifies screen reader compatibility (VoiceOver, NVDA, JAWS), keyboard-only navigation, zoom at 200%/400%, reduced motion, and high contrast modes. - Actionable Remediation Reports: Produces structured audit reports with evidence, code-level fix examples, and prioritized remediation plans. - Use Case: Before a product release, run a full accessibility audit of your checkout flow to confirm screen reader users can complete purchases independently and keyboard users encounter no focus traps. ## Quick Start Audit the attached web application against WCAG 2.2 Level AA and produce a full accessibility report with prioritized fixes.

Frequently Asked Questions about testing-testing-accessibility-auditor

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

FAQPage Schema
How do I audit a website for WCAG 2.2 accessibility compliance?▼

Run automated scans with axe-core and Lighthouse first, then manually test all user journeys with a screen reader and keyboard-only navigation. Document each issue with its specific WCAG criterion, severity, evidence, and a concrete fix.

What accessibility issues do automated tools like axe-core miss?▼

Automated tools catch roughly 30% of issues and miss focus order problems, logical reading order, ARIA misuse, and cognitive barriers. Manual testing with real screen readers like VoiceOver or NVDA is required to catch the remaining 70%.

Does a passing Lighthouse accessibility score mean my site is accessible?▼

No, a green Lighthouse score only means automated checks passed. Products can score perfectly and still be unusable with a screen reader, so manual assistive technology testing is required for genuine conformance.

How do I test keyboard navigation for custom components like modals and tabs?▼

Verify Tab reaches all interactive elements, arrow keys move within tablists and menus, Escape closes modals, and focus returns to the trigger element on close. Check each component against WAI-ARIA Authoring Practices patterns.

What are the limitations of ARIA for fixing accessibility problems?▼

ARIA cannot fix broken interaction patterns and is often misused, such as aria-label on non-interactive elements or aria-hidden on focusable elements. Semantic HTML should be preferred since the best ARIA is the ARIA you do not need.