accessibility

Audit web pages against WCAG 2.1 AA accessibility guidelines.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Matheusrlr/payment-orchestrator --skill accessibility-matheusrlr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/Matheusrlr/payment-orchestrator/tree/main/skills-catalog/skills/%28quality%29/web-accessibility
Command: npx skills add https://github.com/Matheusrlr/payment-orchestrator --skill accessibility-matheusrlr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure that web content is usable by everyone, including people with disabilities, by auditing and improving adherence to accessibility standards.

Core Features & Use Cases

  • WCAG Compliance: Provides guidelines and checks based on the Web Content Accessibility Guidelines (WCAG) 2.1.
  • Audit & Improvement: Helps identify and fix issues related to Perceivable, Operable, Understandable, and Robust (POUR) principles.
  • Use Case: A developer needs to ensure their new website meets accessibility standards for a government contract. They can use this Skill to audit their pages for WCAG AA compliance and receive actionable recommendations.

Quick Start

Audit the accessibility of the provided webpage URL according to WCAG 2.1 AA 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 AA compliance?

WCAG 2.1 AA compliance is audited by evaluating your webpage against Perceivable, Operable, Understandable, and Robust principles. This Skill checks keyboard navigation, screen reader support, color contrast, and ARIA usage to provide actionable improvement recommendations.

What are the most common web accessibility issues impacting users with disabilities?

Common web accessibility issues include poor keyboard navigation, lack of screen reader support, insufficient color contrast, and incorrect ARIA usage. These barriers prevent users with disabilities from perceiving, operating, and understanding web content effectively.

Can I use this to test keyboard navigation and screen reader support manually?

Yes, you can test keyboard navigation and screen reader support using the provided manual testing checklists. This Skill supports both automated and manual testing workflows to ensure your web content is fully operable by users relying on assistive technologies.

What is the best way to check ARIA usage and color contrast for inclusive design?

The best way to check ARIA usage and color contrast is applying WCAG 2.1 guidelines through an accessibility audit. This Skill identifies incorrect ARIA implementation and low contrast ratios, ensuring your web standards meet inclusive design requirements.

Does this Skill work for auditing government websites requiring strict accessibility standards?

Yes, this Skill works for auditing government websites by applying strict WCAG 2.1 AA guidelines. It identifies accessibility barriers across the four POUR principles, ensuring your web content meets legal and inclusive design standards required for government contracts.