a11y-pass

Audits rendered web interfaces for WCAG 2.2 AA accessibility compliance and generates a repair ledger.

3|3|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/KyaniteLabs/tastecheck --skill a11y-pass-kyanitelabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-pass
Source: https://github.com/KyaniteLabs/tastecheck/tree/main/skills/a11y-pass
Command: npx skills add https://github.com/KyaniteLabs/tastecheck --skill a11y-pass-kyanitelabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill addresses the gap between automated accessibility audits and real-world usability, ensuring that web interfaces are truly functional for users relying on assistive technologies or keyboard navigation.

Core Features & Use Cases

  • Manual Verification Framework: Provides a structured, evidence-based approach to testing keyboard operability, screen reader compatibility, and visual accessibility.
  • Automated Measurement: Includes a diagnostic script to identify contrast, tap target, and semantic structure failures that automated scanners often miss.
  • Use Case: Use this skill to audit a complex form or navigation menu before a release, ensuring that focus management, ARIA labels, and color contrast meet WCAG 2.2 AA standards.

Quick Start

Run the a11y-pass skill to audit the current page for WCAG 2.2 AA compliance and generate a repair ledger.

Frequently Asked Questions about a11y-pass

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

FAQPage Schema
How do I test keyboard navigation and screen reader compatibility for web interfaces?

Keyboard navigation and screen reader compatibility are tested through a structured verification framework that evaluates operability, semantic HTML structure, and dynamic content announcement to identify real-world accessibility barriers.

What is the best way to audit WCAG 2.2 AA compliance on a complex frontend form?

Auditing WCAG 2.2 AA compliance involves running an automated diagnostic script to detect contrast, tap target, and semantic structure failures, followed by manual verification of focus management and ARIA labels.

Does this accessibility audit verify visual contrast and semantic HTML structure?

Yes, visual contrast and semantic HTML structure are verified by applying a diagnostic script that measures failures against WCAG 2.2 AA standards, ensuring requirements for visual accessibility and structural semantics are satisfied.

Can I use this to identify focus management and ARIA label failures before a release?

Yes, you can identify focus management and ARIA label failures by applying the manual verification framework to complex navigation menus or forms, ensuring assistive technology functionality meets WCAG 2.2 AA standards.

How do I generate a repair ledger for accessibility barriers on a rendered page?

To generate a repair ledger, run an accessibility audit on the current rendered page, which will compile contrast, tap target, and focus management failures into a structured list for remediation.

Why do automated accessibility scanners miss real-world usability barriers?

Automated scanners miss real-world barriers because they cannot fully evaluate manual keyboard operability or screen reader compatibility, requiring a structured evidence-based approach to verify true functionality for assistive technology users.