accessibility

Audit web pages for WCAG 2.2 accessibility gaps and provide remediation guidance.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/AlvaGonz/A-prayer-request-app --skill accessibility-alvagonz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/AlvaGonz/A-prayer-request-app/tree/main/prayer-board/.agent/skills/accessibility
Command: npx skills add https://github.com/AlvaGonz/A-prayer-request-app --skill accessibility-alvagonz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility audits help teams identify and fix barriers on web pages to meet WCAG 2.2 standards, improving usability for all users.

Core Features & Use Cases

  • WCAG-driven audits covering text alternatives, keyboard navigation, color contrast, focus management, and screen reader compatibility.
  • Remediation guidance with concrete, implementation-level steps tied to real-world components like forms, navigation, and media.
  • Use Case: A development team wants to convert an inaccessible landing page into a compliant, accessible experience with prioritized fixes.

Quick Start

Audit a webpage for accessibility and provide remediation guidance.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit a web page for WCAG 2.2 accessibility compliance?

An accessibility audit identifies gaps in keyboard navigation, screen reader support, color contrast, and focus management based on WCAG 2.2 criteria, providing structured guidance and concrete implementation-level steps to fix barriers on web pages.

What is the best way to fix keyboard navigation and focus management issues on a website?

Fix keyboard navigation and focus management by following structured remediation guidance that provides concrete, implementation-level steps for real-world components like forms and navigation menus to meet WCAG 2.2 accessibility criteria.

Can I use this accessibility audit approach for single-page web apps?

Yes, this approach applies to both websites and web apps, auditing interactive components like forms and navigation for screen reader compatibility, keyboard navigation, and responsive behavior to meet WCAG 2.2 standards.

How do screen readers interact with web forms during an accessibility audit?

An accessibility audit evaluates screen reader compatibility with web forms by checking text alternatives and focus management, then outputs concrete implementation-level remediation steps aligned with WCAG 2.2 criteria to fix identified barriers.

What are common color contrast limitations found during website accessibility checks?

Color contrast limitations involve non-compliant text visibility that fails WCAG 2.2 standards; the audit identifies these barriers and provides structured guidance with references to remediate contrast issues across web pages.

When do I need an accessibility audit for my landing page?

You need an accessibility audit when converting an inaccessible landing page into a compliant experience, using WCAG-driven checks to identify barriers and output prioritized, actionable remediation steps for keyboard navigation and screen reader support.