Accessibility Auditor

Audit web interfaces against WCAG 2.2 AA criteria with automated and manual assistive technology testing.

110|18|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill accessibility-auditor-travisleeeeee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Accessibility Auditor
Source: https://github.com/TravisLeeeeee/awesome-openclaw-personas/tree/main/personas/testing/accessibility-auditor
Command: npx skills add https://github.com/TravisLeeeeee/awesome-openclaw-personas --skill accessibility-auditor-travisleeeeee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates accessibility guesswork by producing standards-based audits that combine automated scans with real screen reader and keyboard testing to uncover barriers users actually face.

Core Features & Use Cases

  • WCAG 2.2 AA/AAA-aligned auditing with specific success criterion references and POUR coverage.
  • Assistive technology & keyboard verification using VoiceOver, NVDA, and JAWS, plus 200%/400% zoom, reduced motion, and high-contrast checks.
  • Actionable remediation guidance that prioritizes by user impact and includes code-level fix examples for semantic HTML, ARIA patterns, focus management, and live region announcements.
  • Deliverable audit reports using structured templates with severity (Critical/Serious/Moderate/Minor), evidence, and verification steps.

Quick Start

Run an accessibility audit for your target page or user flow and request a remediation-prioritized WCAG 2.2 report that includes both automated and manual assistive-technology findings.

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 AA accessibility audit for my web interface?

Run an accessibility audit by combining automated scans with manual screen reader and keyboard testing. This verifies WCAG 2.2 AA compliance across web interfaces to produce a severity-ranked report with code-level remediation guidance.

What is the best way to test keyboard navigation and focus management for dynamic content?

Testing keyboard navigation and focus management requires manual verification using keyboard-only interactions and screen readers. This identifies dynamic content announcement barriers and focus traps to ensure interactive components are fully operable without a mouse.

How do I fix ARIA and semantic HTML barriers found during an accessibility audit?

Fix ARIA and semantic HTML barriers by applying code-level remediation guidance from the audit report. This provides concrete examples for correcting ARIA patterns, live region announcements, and semantic structure to meet specific WCAG 2.2 success criteria.

Does this accessibility audit include screen reader testing with VoiceOver and NVDA?

Yes, the accessibility audit includes screen reader testing using VoiceOver, NVDA, and JAWS. It verifies dynamic content announcements and interactive component behavior to uncover real barriers that automated scanning alone cannot detect.

How do I verify high-contrast and reduced motion compliance for cognitive accessibility?

Verify high-contrast and reduced motion compliance through manual assistive technology checks including 200% and 400% zoom testing. This evaluates cognitive accessibility and visual clarity against WCAG 2.2 AA design system criteria.

Can I audit specific interactive components or do I need to scan an entire user flow?

You can audit both individual interactive components and entire user flows. The audit evaluates focus management, keyboard-only navigation, and dynamic content announcements to generate a prioritized report with specific success-criterion references.