skills.rest
jerelvelarde
jerelvelardeCOMMUNITY
Explore all skills by this author →
GitHub

audit-accessibility

Audits UI components and pages for WCAG 2.1 AA compliance using POUR principles.

6|Updated Feb 19, 2026
Search Tags:#accessibility#a11y#frontend#audit#compliance#wcag#pour
One-click install
npx skills add https://github.com/jerelvelarde/chalk-skills --skill audit-accessibility-jerelvelarde
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit-accessibility
Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/audit-accessibility
Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill audit-accessibility-jerelvelarde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

WCAG 2.1 AA accessibility checks are often manual, time-consuming, and inconsistent across features. This skill streamlines the process by generating a POUR-based audit that surfaces actionable accessibility gaps.

Core Features & Use Cases

  • Generate POUR-aligned accessibility audits for specific features or UI components, including testing steps and guidance for keyboard, screen readers, and color contrast.
  • Produce a structured checklist with clear pass/fail criteria and remediation recommendations to inform design and development work.
  • Use during feature reviews, PRD validation, and release checks to ensure compliance before shipping.

Quick Start

Prompt the AI to audit a specified feature or component for WCAG 2.1 AA compliance using POUR.

Frequently Asked Questions about audit-accessibility

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

FAQPage Schema
How do I audit a UI component for WCAG 2.1 AA compliance?▼

To audit a UI component for WCAG 2.1 AA compliance, generate a POUR-based audit that surfaces actionable accessibility gaps. This produces a structured checklist with keyboard navigation guidance, screen reader expectations, and remediation suggestions.

What is a POUR accessibility audit and when do I need one?▼

A POUR accessibility audit evaluates features against Perceivable, Operable, Understandable, and Robust principles to ensure WCAG 2.1 AA compliance. You need this during feature PRDs, code reviews, or release checks to identify and resolve accessibility gaps before shipping.

Can I use a POUR audit during PRD validation and release checks?▼

Yes, you can use a POUR audit during PRD validation, code reviews, and release checks. It streamlines manual accessibility testing by producing a structured checklist with clear pass/fail criteria and remediation recommendations for design and development work.

What's the best way to generate an accessibility checklist for frontend features?▼

The best way to generate an accessibility checklist for frontend features is using a POUR-aligned audit. It evaluates UI components and pages against WCAG 2.1 AA standards, providing specific testing instructions, keyboard navigation guidance, and screen reader expectations.

Why does my WCAG 2.1 AA compliance check fail to catch screen reader expectations?▼

WCAG 2.1 AA compliance checks often miss screen reader expectations because manual testing is inconsistent. A POUR-based audit standardizes this by generating structured testing instructions and clear remediation suggestions for each evaluated feature or UI component.

Related Skills

Explore More Software Engineering Skills→
GeneralJerelGeneralJerel
6

audit-accessibility

Audit web UI components for WCAG 2.1 AA conformance using POUR principles.

Community
Advanced
samjhechtsamjhecht
4

frontend-accessibility-verification

Verify frontend UI accessibility compliance with axe-core, keyboard, screen reader, and Lighthouse audits.

Community
Advanced
ofelixdevofelixdev

accessibility

Audit web pages against WCAG 2.1 guidelines with code examples and testing checklists.

Community
Intermediate
Montte-erpMontte-erp
6

wcag-audit-patterns

Audit web pages for WCAG 2.2 violations with automated and manual checks.

Official
Intermediate