skills.rest
sjmontano
sjmontanoCOMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web accessibility against WCAG 2.2 guidelines and generate prioritized fixes.

Updated May 29, 2026
Search Tags:#accessibility#a11y#usability#wcag#lighthouse#aria#web-a11y
One-click install
npx skills add https://github.com/sjmontano/SafeRoutes-Popayan --skill accessibility-sjmontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/sjmontano/SafeRoutes-Popayan/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/sjmontano/SafeRoutes-Popayan --skill accessibility-sjmontano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

Core Features & Use Cases

Comprehensive guidelines and practical patterns to assess and enhance accessibility across web content, interfaces, and components. It covers POUR principles, contrast, keyboard navigation, ARIA patterns, and accessibility code patterns with ready-to-use references.

Quick Start

Run a WCAG 2.2 accessibility audit and generate a prioritized list of fixes for keyboard navigation and screen reader support.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I run a WCAG 2.2 accessibility audit on my web app?▼

Run a WCAG 2.2 accessibility audit by evaluating your web app against POUR principles, keyboard navigation, screen reader support, and color contrast to generate a prioritized list of fixes.

What is the best way to fix ARIA patterns and semantic HTML for screen reader support?▼

Improve screen reader support by applying correct ARIA patterns and semantic HTML improvements to ensure web content is programmatically determinable and operable.

How does keyboard navigation testing work for web accessibility compliance?▼

Keyboard navigation testing checks if users can access all interactive elements without a mouse, ensuring web interfaces meet WCAG operable principles and functional accessibility requirements.

Can I use Lighthouse and axe style audits to check color contrast and usability?▼

Yes, you can integrate Lighthouse and axe style audits to automatically detect color contrast failures and usability issues, generating actionable code patterns for remediation.

Do I need to follow POUR principles for both development and QA accessibility contexts?▼

Yes, applying POUR principles across both development and QA contexts ensures web content is perceivable, operable, understandable, and robust for all users during the entire lifecycle.

When should I not use automated accessibility audit tools?▼

Avoid relying solely on automated accessibility audit tools for complex interactive components, as manual testing is required to validate keyboard navigation flows and dynamic ARIA pattern behavior.

Related Skills

Explore More Content & Communication Skills→
VMRam95VMRam95

web-design-guidelines

Audit React and HTML code for WCAG accessibility and Vercel design compliance.

Community
Intermediate
smart-village-solutionssmart-village-solutions
4

wcag-audit-patterns

Audit web content for WCAG 2.2 issues using axe-core, pa11y, and Lighthouse.

Official
Advanced
aroidoaroido

accessibility-audit

Audit web components for WCAG 2.1 AA accessibility issues.

Official
Intermediate
KhoiwallKhoiwall

accessibility-audit

Audits UI components for WCAG compliance and accessibility barriers.

Community
Intermediate