accessibility

Audit web content against WCAG 2.1 guidelines and implement accessibility fixes.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/rafael-hc/AoPonto-FoodService --skill accessibility-rafael-hc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/rafael-hc/AoPonto-FoodService/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/rafael-hc/AoPonto-FoodService --skill accessibility-rafael-hc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes 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 standards.

Core Features & Use Cases

  • WCAG 2.1 Compliance: Audit and improve web content against Perceivable, Operable, Understandable, and Robust (POUR) principles.
  • Code Examples: Provides practical HTML, CSS, and JavaScript snippets for implementing accessibility best practices.
  • Testing Guidance: Includes checklists and commands for automated and manual accessibility testing.
  • Use Case: When developing a new website feature, use this Skill to ensure it meets WCAG AA standards, making it usable for users with visual impairments, motor disabilities, and cognitive differences.

Quick Start

Audit the current webpage for accessibility issues based on WCAG 2.1 guidelines.

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 web accessibility by evaluating your content against WCAG 2.1 guidelines, focusing on Perceivable, Operable, Understandable, and Robust principles. This includes checking for missing alt text, insufficient color contrast, keyboard traps, and improper ARIA usage.

What is the best way to fix keyboard traps and improper ARIA usage?

Fix keyboard traps and improper ARIA usage by applying provided HTML, CSS, and JavaScript code examples that implement accessibility best practices. This ensures your web content remains operable and robust for assistive technologies like screen readers.

How does WCAG compliance address common issues like missing alt text and insufficient color contrast?

WCAG compliance addresses missing alt text and insufficient color contrast through the Perceivable principle, ensuring web content is usable by everyone. Practical code examples and testing checklists help resolve these specific accessibility barriers.

What's the best way to test for screen reader compatibility during web development?

Test screen reader compatibility by using included testing checklists and commands for both automated and manual accessibility testing. This verifies your website meets WCAG AA standards for users with visual impairments and motor disabilities.

Do I need specific testing tools to ensure my web content meets accessibility standards?

You do not need specific external testing tools to start, as this provides testing checklists and commands for automated and manual accessibility evaluation. It guides you through auditing webpages against WCAG 2.1 guidelines directly.

What are the limitations of automated accessibility testing for WCAG AA standards?

Automated accessibility testing cannot detect all WCAG AA standard violations, such as complex keyboard traps or contextual ARIA usage. Manual testing checklists are required alongside code examples to ensure web content is fully usable by diverse users.