accessibility

Audit web pages for WCAG 2.1 compliance and implement accessibility fixes.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/felipebrgs1/skills --skill accessibility-felipebrgs1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/felipebrgs1/skills/tree/main/other/accessibility
Command: npx skills add https://github.com/felipebrgs1/skills --skill accessibility-felipebrgs1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make web content accessible to all users, including those with disabilities, by adhering to established accessibility guidelines.

Core Features & Use Cases

  • WCAG Compliance: Provides guidance on meeting Perceivable, Operable, Understandable, and Robust (POUR) principles.
  • Code Examples: Demonstrates best practices for text alternatives, color contrast, keyboard navigation, focus visibility, and ARIA usage.
  • Testing Checklists: Includes automated and manual testing strategies and screen reader command references.
  • Use Case: When developing a new web application, use this Skill to audit and implement features that ensure compliance with WCAG 2.1 AA standards, making the application usable for a wider audience.

Quick Start

Use the accessibility skill to audit the provided webpage for WCAG 2.1 compliance.

Frequently Asked Questions about accessibility

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

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

To audit web accessibility for WCAG 2.1 compliance, evaluate your application against the Perceivable, Operable, Understandable, and Robust principles using the provided automated and manual testing checklists.

What are the WCAG 2.1 guidelines for keyboard navigation and focus states?

WCAG 2.1 guidelines for keyboard navigation require ensuring all interactive elements are operable via keyboard and maintain visible focus states. Best practices include managing focus visibility and implementing correct ARIA attributes for dynamic content.

How do I test web accessibility using a screen reader?

To test web accessibility with a screen reader, use the included screen reader command references to navigate and verify content. This manual testing approach ensures text alternatives and live regions are properly announced to users.

Does this accessibility audit cover color contrast and alt text requirements?

Yes, this accessibility audit covers color contrast and alt text requirements by providing code examples that demonstrate best practices for text alternatives and visual readability under the Perceivable principle of WCAG 2.1.

What is the best way to implement ARIA attributes and live regions?

The best way to implement ARIA attributes and live regions is to follow the provided code examples, which demonstrate proper usage for dynamic content updates, ensuring web content is robust and understandable for screen reader users.

Can I use this to ensure my web content is usable by everyone?

Yes, you can use this to ensure web content is usable by everyone by auditing and improving your application against WCAG 2.1 AA standards, addressing keyboard navigation, screen reader compatibility, and visual accessibility.