accessibility

Audit web accessibility against WCAG 2.1 and generate remediation checklists.

2|Updated Feb 5, 2026

Search Tags:#accessibility #a11y #wcag #screen-readers #conformance #web-standards #a11y-audits

Ready to run

npx skills add https://github.com/damacus/agent-skills --skill accessibility-damacus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/damacus/agent-skills/tree/main/skills/accessibility
Command: npx skills add https://github.com/damacus/agent-skills --skill accessibility-damacus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

Core Features & Use Cases

Comprehensive WCAG-based guidelines (P, O, U, R) and Lighthouse accessibility audits for web content.
Practical examples for images, color contrast, focus management, and keyboard navigation.
Use Cases: conducting accessibility audits on websites, creating inclusive components, and producing remediation checklists.

Quick Start

Run an accessibility audit against a target webpage and implement the recommended WCAG-compliant fixes.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I run a WCAG 2.1 accessibility audit on my website?▼

To run a WCAG 2.1 accessibility audit, evaluate your web content against guidelines across perceivable, operable, understandable, and robust categories. This process generates a remediation checklist targeting screen-reader readiness, keyboard navigation, and color contrast issues.

What is included in an a11y audit for web compliance?▼

An a11y audit for web compliance includes Lighthouse accessibility checks, WCAG 2.1 guideline validation, and practical tests for keyboard navigation and screen-reader support. It produces actionable fixes and examples for images, color contrast, and focus management.

How do I fix keyboard navigation and focus management issues?▼

Fix keyboard navigation and focus management issues by applying practical accessibility guidelines that ensure logical tab order and visible focus states. Implementing these WCAG-compliant fixes ensures all interactive elements are fully operable without a mouse.

Does this approach check color contrast and screen-reader readiness?▼

Yes, this approach checks color contrast and screen-reader readiness by applying WCAG 2.1 conformance standards. It specifies actionable guidelines drawn from Lighthouse audits to validate visual contrast ratios and semantic HTML structures for assistive technologies.

What is the best way to make website components accessible?▼

The best way to make website components accessible is to build them following WCAG 2.1 guidelines for inclusive design. This involves validating keyboard navigation, ensuring proper ARIA usage, and applying practical examples for images and focus management.

When do I need to check WCAG compliance for my web app?▼

You need to check WCAG compliance for your web app whenever you need to ensure inclusive access for all users. Running an a11y audit against target webpages verifies conformance with web standards and identifies necessary fixes for screen-reader and keyboard support.