skills.rest
GeneralJerel
GeneralJerelCOMMUNITY
Explore all skills by this author →
GitHub

audit-accessibility

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Accessibility Audit skill helps teams identify and document WCAG 2.1 AA conformance gaps for a given feature or component by applying POUR principles, producing actionable remediation guidance.

Core Features & Use Cases

  • POUR-based analysis across Perceivable, Operable, Understandable, and Robust criteria for UI components.
  • Context-aware evaluation that leverages project docs and source code to tailor checks.
  • Deliverables include a prioritized remediation checklist, keyboard interaction notes, and screen reader expectations.

Quick Start

Provide a feature or component name to audit and receive a POUR-based accessibility checklist.

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 web UI component for WCAG 2.1 AA compliance?▼

Perform a WCAG 2.1 AA audit by evaluating the feature against POUR principles, generating a prioritized remediation checklist with specific testing steps for keyboard navigation, screen readers, and color contrast.

What is a POUR-based accessibility audit?▼

A POUR-based accessibility audit evaluates web features across Perceivable, Operable, Understandable, and Robust criteria to identify WCAG 2.1 AA conformance gaps and produce actionable remediation guidance.

How do I test keyboard navigation and screen reader expectations for a feature?▼

Generate keyboard interaction notes and screen reader expectations by running a context-aware accessibility audit that outputs specific testing steps tailored to the provided component's source code.

Can I use existing project docs and source code to check for accessibility issues?▼

Yes, the accessibility audit leverages existing project docs and source code to provide context-aware evaluation and tailor WCAG 2.1 AA checks for the specific UI component.

What's the best way to identify color contrast and responsive behavior gaps in UI forms?▼

Run a POUR-based audit on your UI forms to identify color contrast and responsive behavior gaps, delivering a structured checklist of actionable testing steps and remediation guidance.

Related Skills

Explore More Software Engineering Skills→
Srajangpt1Srajangpt1

write-docs

Generate BrowserOS feature MDX docs from source code and screenshots.

Community
Intermediate
cy-walicy-wali

accessibility-review

Audit Figma designs and pages for WCAG 2.1 AA compliance.

Community
Intermediate
mathemagiemathemagie

accessibility

Audit web accessibility against WCAG 2.1 standards and generate remediation plans.

Community
Basic
89jobrien89jobrien
4

web-accessibility

Audit web content for WCAG 2.1/2.2 conformance and accessibility issues.

Community
Advanced