accessibility

Audit web pages for WCAG 2.2 accessibility gaps and generate a prioritized remediation plan.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/mauroviveros/eventdex --skill accessibility-mauroviveros
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/mauroviveros/eventdex/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/mauroviveros/eventdex --skill accessibility-mauroviveros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audits and improves accessibility of web content to meet WCAG 2.2 guidelines, helping ensure inclusive experiences and reduce compliance risk.

Core Features & Use Cases

  • WCAG 2.2 conformance auditing
  • Accessibility recommendations for keyboard navigation, color contrast, alt text, and semantic markup
  • Use case: evaluate a landing page and generate a prioritized remediation list for a11y issues

Quick Start

Audit the current page for accessibility and generate an actionable remediation plan.

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 compliance?

WCAG 2.2 conformance auditing evaluates web pages, apps, or component libraries to uncover alt-text gaps, keyboard traps, and color contrast issues. It leverages automated checks and documented patterns to output a prioritized remediation plan.

How do I fix keyboard navigation traps in my web app?

Fixing keyboard traps involves evaluating your web app against WCAG 2.2 guidelines to identify focus issues. A documented accessibility audit generates actionable recommendations to resolve these traps and improve keyboard navigation.

Can Lighthouse be used to check color contrast and alt text issues?

Yes, Lighthouse can be used to check color contrast and alt text issues during a web accessibility audit. It works alongside axe-core to identify gaps and generate a prioritized remediation list for WCAG 2.2 conformance.

What is the best way to generate an accessibility remediation plan for a component library?

The best way to generate a remediation plan is to audit your component library against WCAG 2.2 guidelines. This uncovers semantic markup and landmark structure issues, outputting a prioritized list of actionable fixes.

Does an automated accessibility audit catch all WCAG 2.2 landmark structure issues?

An automated accessibility audit identifies many landmark structure issues but may not catch every WCAG 2.2 gap. It leverages automated checks alongside documented patterns to prioritize the most critical semantic markup issues for remediation.