accessibility

Name: accessibility
Availability: InStock
Author: RepairYourTech

Audit web accessibility against WCAG 2.1 guidelines and provide code examples.

6|1|Updated Feb 27, 2026

Search Tags:#accessibility #a11y #screen reader #web development #WCAG #usability

Ready to run

npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill accessibility-repairyourtech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/RepairYourTech/cfsa-antigravity/tree/main/.agent/skills/accessibility
Command: npx skills add https://github.com/RepairYourTech/cfsa-antigravity --skill accessibility-repairyourtech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make web content usable by everyone, including individuals with disabilities, by auditing and improving adherence to accessibility standards.

Core Features & Use Cases

WCAG 2.1 Auditing: Checks 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 automated and manual testing checklists, along with screen reader commands.
Use Case: A developer needs to ensure their new web application meets WCAG AA standards before launch. They can use this Skill to identify and fix issues related to keyboard navigation, color contrast, and ARIA implementation.

Quick Start

Audit the accessibility of the provided website URL according to 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 web application for WCAG 2.1 compliance?▼

Audit web accessibility by checking your application against WCAG 2.1 guidelines across Perceivable, Operable, Understandable, and Robust principles. This process identifies issues in semantic HTML, ARIA usage, keyboard navigation, color contrast, and media alternatives.

What is the best way to implement ARIA roles and semantic HTML for screen reader compatibility?▼

Screen reader compatibility relies on proper semantic HTML and ARIA usage. You need to implement ARIA roles correctly and use semantic HTML elements to ensure web content is perceivable and operable for users relying on assistive technologies.

How do I test keyboard navigation and color contrast for usability?▼

Test keyboard navigation and color contrast using automated and manual testing checklists. This ensures your web application meets WCAG AA standards by verifying that all interactive elements are accessible via keyboard and text remains legible.

Does this approach provide specific screen reader commands for manual accessibility testing?▼

Manual accessibility testing requires specific screen reader commands to verify compliance. The process includes comprehensive checklists and screen reader commands to validate that web content meets WCAG 2.1 standards for visually impaired users.

What are the limitations of automated accessibility testing versus manual testing?▼

Automated accessibility testing cannot catch all usability issues, necessitating manual testing checklists. While automated tools identify basic WCAG 2.1 violations like missing alt text, manual testing is required to validate keyboard navigation and screen reader interactions.