accessibility

Audits web pages for WCAG 2.2 conformance and returns actionable accessibility fixes.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/SteepCraft/Base-de-datos-2 --skill accessibility-steepcraft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/SteepCraft/Base-de-datos-2/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/SteepCraft/Base-de-datos-2 --skill accessibility-steepcraft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility conformance for websites and apps.

Core Features & Use Cases

  • WCAG 2.2 guidance and Lighthouse accessibility patterns for practical implementation.
  • A11Y pattern references and best practices to inform accessible HTML, ARIA, and navigation.
  • Use cases include audits, remediation planning, and compliance reporting for front-end interfaces.

Quick Start

Audit the given page for WCAG 2.2 conformance and return actionable accessibility fixes.

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.2 conformance?

Audit web accessibility by evaluating front-end interfaces against WCAG 2.2 criteria and Lighthouse patterns. It analyzes HTML semantics, ARIA usage, color contrast, keyboard navigation, and skip links, returning actionable fixes and compliance reporting guidance.

What are common ARIA and HTML semantic issues to fix for web accessibility?

Common web accessibility issues involve improper ARIA usage, non-semantic HTML, insufficient color contrast, and missing keyboard navigation. Apply A11Y patterns to correct these barriers, ensuring front-end interfaces meet WCAG 2.2 standards.

Can I use this for accessibility remediation planning and compliance reporting?

Yes, you can use it for accessibility remediation planning and compliance reporting. It evaluates front-end interfaces against WCAG 2.2 and Lighthouse patterns, outputting actionable recommendations and referencing practical A11Y patterns for implementation.

How do Lighthouse accessibility patterns help improve A11Y compliance?

Lighthouse accessibility patterns help improve A11Y compliance by providing a baseline for auditing front-end interfaces. Combined with WCAG 2.2 guidance, they identify issues in HTML semantics, ARIA, and navigation, yielding actionable recommendations.

Do I need specific front-end frameworks to check web accessibility standards?

No specific front-end framework is required. The accessibility audit applies generally to front-end interfaces, evaluating HTML semantics, ARIA usage, color contrast, keyboard navigation, and skip links against WCAG 2.2 and Lighthouse patterns.

What's the best way to fix keyboard navigation and skip links for A11Y compliance?

Fix keyboard navigation and skip links by applying practical A11Y patterns to front-end interfaces. The audit identifies barriers against WCAG 2.2 standards and outputs actionable recommendations to ensure proper focus management and accessible navigation.