accessibility

Audit web accessibility against WCAG 2.1 and generate remediation plans.

Updated May 28, 2022

Search Tags:#accessibility #a11y #WCAG #lighthouse #screen-reader #color-contrast #keyboard-navigation

Ready to run

npx skills add https://github.com/GuiErba/guierba.github.io --skill accessibility-guierba

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/GuiErba/guierba.github.io/tree/main/new/.cursor/skills/accessibility
Command: npx skills add https://github.com/GuiErba/guierba.github.io --skill accessibility-guierba

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". Do NOT use for SEO (use seo), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).

Core Features & Use Cases

Guidance on POUR principles, conformance levels (A/AA/AAA), and practical checks for common accessibility issues.
Templates and examples for semantic HTML, ARIA usage, color contrast, focus management, and keyboard navigation.
Use Case: QA teams, developers, and content creators performing WCAG-compliant audits and remediation across pages, components, forms, and media.

Quick Start

Run a WCAG-aligned accessibility assessment on your page and generate a prioritized remediation plan.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I perform a WCAG 2.1 accessibility audit on my web pages?▼

To perform a WCAG audit, assess semantic HTML, ARIA usage, color contrast, focus management, and keyboard navigation. This process evaluates conformance levels A, AA, and AAA to generate a prioritized remediation plan.

What is the best way to fix screen reader and keyboard navigation issues?▼

Fixing screen reader and keyboard navigation issues requires implementing semantic HTML and proper ARIA attributes. Ensuring logical focus management and accessible naming provides operable keyboard navigation and readable content for assistive technologies.

How does Lighthouse handle color contrast and ARIA checks for a11y compliance?▼

Lighthouse a11y audits evaluate color contrast ratios and validate ARIA usage against WCAG best practices. Running an accessibility assessment identifies failures in contrast and ARIA implementation, producing actionable remediation steps for components and forms.

Can I use this for comprehensive site audits covering SEO and performance?▼

No, this is strictly for accessibility audits and WCAG compliance. For comprehensive site audits covering SEO or performance, use dedicated tools like seo, core-web-vitals, or web-quality-audit instead of this a11y-focused workflow.

When do I need to check focus management during an accessibility audit?▼

Check focus management during an accessibility audit when evaluating keyboard operability and screen reader support. It ensures focus moves logically across dynamic content, forms, and components, satisfying POUR principles and WCAG 2.1 conformance.