accessibility

Audit web projects for WCAG 2.1 accessibility issues and generate remediation plans.

7.8k|770|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/gsd-build/gsd-2 --skill accessibility-gsd-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/gsd-build/gsd-2/tree/main/src/resources/skills/accessibility
Command: npx skills add https://github.com/gsd-build/gsd-2 --skill accessibility-gsd-build

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

  • WCAG 2.1-based guidelines and auditing workflows to identify accessibility issues across perceivable, operable, understandable, and robust criteria.
  • Lighthouse audit checks, color contrast validation, keyboard navigation tests, screen reader considerations, and ARIA pattern recommendations to improve inclusive design.
  • Use Case: teams deliver accessible websites and progressive enhancements by producing remediation tasks and accessibility reports aligned with WCAG conformance levels (A/AA/AAA).

Quick Start

Audit your web project for WCAG 2.1 accessibility issues and generate an actionable remediation plan.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit my website for WCAG 2.1 compliance?

Audit website accessibility by validating HTML structure, color contrast, keyboard navigation, and screen reader readiness against WCAG 2.1 principles to identify conformance issues across perceivable, operable, understandable, and robust criteria.

What is included in an a11y audit for web accessibility?

An a11y audit includes Lighthouse checks, color contrast validation, keyboard navigation tests, screen reader considerations, and ARIA pattern recommendations to produce remediation tasks aligned with WCAG conformance levels A, AA, and AAA.

How do I fix keyboard navigation and screen reader compatibility issues?

Fix keyboard navigation and screen reader compatibility by applying ARIA practices and WCAG Quick Reference guidelines to correct HTML structure, ensuring interactive elements are fully operable without a mouse.

Does this accessibility audit support WCAG conformance levels A, AA, and AAA?

Yes, the accessibility audit supports WCAG 2.1 conformance levels A, AA, and AAA. It evaluates web projects against the POUR principles and generates an actionable remediation report based on the target conformance level.

What's the best way to generate an accessibility remediation plan for a web project?

Generate an accessibility remediation plan by running auditing workflows that evaluate assistive technology compatibility, color contrast, and ARIA patterns, producing structured tasks aligned with WCAG 2.1 conformance requirements.

When do I need to check color contrast and ARIA patterns for web accessibility?

Check color contrast and ARIA patterns whenever you need to ensure inclusive design and progressive enhancements meet WCAG 2.1 standards, particularly if interactive elements or dynamic content updates are present.