alfadocs-accessibility-review

Audit AlfaDocs interfaces for WCAG compliance and accessibility defects.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/alfadocs/ai-harness-instructions --skill alfadocs-accessibility-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alfadocs-accessibility-review
Source: https://github.com/alfadocs/ai-harness-instructions/tree/main/lovable/skills/alfadocs-accessibility-review
Command: npx skills add https://github.com/alfadocs/ai-harness-instructions --skill alfadocs-accessibility-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you review AlfaDocs app interfaces for accessibility problems before release, so you can catch keyboard, contrast, naming, RTL, motion, and translation issues before users do.

Core Features & Use Cases

  • Comprehensive a11y audit: Checks screens, dialogs, drawers, toasts, forms, empty states, loading states, and error states for common WCAG failures.
  • Kit-preserving review: Verifies that the app keeps the built-in accessibility benefits of @alfadocs/ui-kit instead of breaking focus handling, semantics, or overlays with custom overrides.
  • Theme and locale validation: Reviews light, dark, accessible, and RTL behavior so layouts, target sizes, contrast, and directional UI remain usable across locales.
  • Use Case: A pre-ship reviewer can walk through a product and produce a clear list of blockers, warnings, and notes with file and component references.

Quick Start

Review the attached AlfaDocs app for accessibility issues and report any blockers, warnings, and notes with the relevant file and component references.

Frequently Asked Questions about alfadocs-accessibility-review

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

FAQPage Schema
How do I audit my application interface for WCAG compliance before release?

To audit an application interface for WCAG compliance, review screens, dialogs, and forms for keyboard reachability, focus visibility, target size, contrast, and accessible names. This pre-ship process catches accessibility defects across light, dark, accessible, and RTL themes before users do.

What is focus management and how does it work with a UI kit?

Focus management ensures keyboard users can navigate interactive elements logically. It works with a UI kit by preserving built-in semantics and focus handling, verifying that custom overrides do not break keyboard reachability, focus visibility, or overlay behaviors across application states.

How do I check contrast and target size for RTL and dark mode layouts?

Check contrast and target size for RTL and dark mode layouts by validating theme and locale behavior across directional UI. This ensures layouts remain usable, target sizes meet WCAG standards, and logical properties handle translated strings correctly across locales.

Does this accessibility review work with screens, toasts, and empty states?

Yes, this accessibility review works with screens, toasts, and empty states. It comprehensively audits dialogs, drawers, forms, loading states, and error states for common WCAG failures, producing a clear list of blockers, warnings, and notes with file references.

What is the best way to verify reduced motion and translated strings in an a11y audit?

The best way to verify reduced motion and translated strings in an a11y audit is to check logical properties and motion preferences during a pre-ship review. This validates that directional UI remains usable and translated strings render correctly across accessible themes.

Why does overriding the UI kit break accessibility semantics?

Overriding the UI kit breaks accessibility semantics because custom overrides disrupt built-in focus handling, keyboard reachability, and overlay behaviors. A kit-preserving review verifies that the app keeps built-in accessibility benefits instead of breaking them with custom overrides.