accessibility

Audit webpages for WCAG 2.1 compliance and implement accessibility fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make digital content usable by everyone, including individuals with disabilities, by adhering to established accessibility standards.

Core Features & Use Cases

  • WCAG Compliance: Provides guidelines and checks based on the Web Content Accessibility Guidelines (WCAG) 2.1 POUR principles.
  • Audit & Improvement: Helps identify and fix issues related to perceivability, operability, understandability, and robustness.
  • Use Case: When developing a new website feature, use this Skill to ensure it meets AA conformance levels for screen reader support and keyboard navigation before launch.

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 a webpage for WCAG 2.1 compliance?

To audit a webpage for WCAG 2.1 compliance, evaluate it against the Perceivable, Operable, Understandable, and Robust principles. This process checks text alternatives, color contrast, keyboard navigation, focus visibility, form labeling, and ARIA usage to identify accessibility issues.

What is the best way to ensure screen reader support for a new web feature?

The best way to ensure screen reader support is to verify WCAG 2.1 AA conformance levels. This involves checking text alternatives, proper form labeling, and correct ARIA usage so that digital content is fully perceivable and operable for screen reader users.

How do I fix keyboard navigation and focus visibility issues?

Fix keyboard navigation and focus visibility issues by applying WCAG 2.1 operable guidelines. This ensures all interactive elements are accessible via keyboard and provides visible focus indicators, allowing users to navigate web content without a mouse.

When do I need to check color contrast for web accessibility?

You need to check color contrast for web accessibility when ensuring digital content meets WCAG 2.1 perceivable guidelines. Evaluating contrast ratios guarantees that text and visual elements are distinguishable for users with visual impairments before website launch.

Does this WCAG audit cover both automated and manual testing checklists?

Yes, this WCAG audit covers both automated and manual testing checklists. It ensures compliance by systematically evaluating web content against established accessibility standards, addressing perceivability, operability, understandability, and robustness criteria.

Why is proper ARIA usage important for web accessibility?

Proper ARIA usage is important for web accessibility because it enhances the robustness of digital content. Following WCAG 2.1 guidelines ensures dynamic elements and interactive components are correctly announced to assistive technologies like screen readers.