accessibility

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many websites and web applications exclude people with disabilities because they lack clear guidance to follow WCAG 2.2, accessible patterns, and practical testing steps; this Skill helps teams identify gaps and produce actionable fixes so content is usable by everyone.

Core Features & Use Cases

  • Guidance mapped to WCAG 2.2: Concrete explanations of POUR principles, conformance levels (A, AA, AAA), and which criteria to prioritize.
  • Practical code patterns and patterns library: Copy-paste ready ARIA patterns, modal focus traps, skip links, form label examples, and live region handling for developers.
  • Testing checklist and workflows: Automated audit suggestions (Lighthouse, axe), manual test items (keyboard, screen reader, zoom), and prioritized remediation lists for product teams.
  • Use Case: Audit a nonprofit's public directory pages to fix missing alt text, improve color contrast, add keyboard support for interactive maps, and deliver a prioritized developer ticket list.

Quick Start

Audit the target URL for WCAG 2.2 AA issues, list critical failures with reproduction steps, and propose prioritized code or content fixes.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit a website for WCAG 2.2 accessibility issues?

Audit web page accessibility by checking color contrast, ARIA semantics, keyboard navigation, and media alternatives against WCAG 2.2 criteria, then produce prioritized remediation guidance with clear code examples and manual testing steps.

What is WCAG 2.2 conformance and how does it apply to web applications?

WCAG 2.2 conformance ensures web applications are usable by people with disabilities by meeting POUR principles across levels A, AA, and AAA, requiring validation of keyboard navigation, screen reader experiences, and semantic ARIA markup.

How do I fix keyboard navigation and ARIA markup for interactive web elements?

Fix keyboard navigation and ARIA markup by applying semantic HTML, implementing focus traps for modals, adding skip links, and using correct live region handling, validated through manual keyboard and screen reader testing workflows.

Does this accessibility audit work with Lighthouse and axe-style testing tools?

Yes, the accessibility audit integrates Lighthouse and axe-style automated checks to identify initial DOM and CSS failures, then supplements them with manual testing items for keyboard and screen reader usability.

What is the best way to prioritize web accessibility remediation for developers?

Prioritize accessibility remediation by mapping failures to WCAG 2.2 conformance levels, categorizing critical issues like missing alt text and poor color contrast, and delivering a ticket list with reproduction steps and copy-paste ready ARIA code patterns.

When should I manually test screen reader experiences instead of relying on automated audits?

Manually test screen reader experiences when interactive elements like maps or modals require keyboard support, because automated Lighthouse and axe audits cannot validate usable focus traps, live regions, or complex semantic flows.