accessibility

Audit WCAG 2.2 accessibility and generate prioritized remediation plans.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/emilneuraz-ai/neuraz-web --skill accessibility-emilneuraz-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/emilneuraz-ai/neuraz-web/tree/main/.agents/skills/.agents/skills/accessibility
Command: npx skills add https://github.com/emilneuraz-ai/neuraz-web --skill accessibility-emilneuraz-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audit and improve WCAG 2.2 accessibility across web pages and applications.

Core Features & Use Cases

  • Audit WCAG 2.2 compliance across pages, forms, navigation, and dynamic content.
  • Remediation provide actionable fixes and guidance aligned with POUR principles.
  • Use Case run a11y audits for small sites or large web apps to ensure assistive technology compatibility.

Quick Start

Run an accessibility audit on the target page and output a prioritized 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 my web pages for WCAG 2.2 compliance?

To audit WCAG 2.2 compliance, evaluate web pages, forms, and navigation against established criteria. This process identifies accessibility barriers and generates actionable remediation steps with supporting evidence to ensure assistive technology compatibility.

What is the best way to fix keyboard navigation and screen-reader issues?

Fixing keyboard navigation and screen-reader issues requires enforcing POUR principles during an accessibility audit. This provides actionable fixes for dynamic content and forms, ensuring seamless interaction for users relying on assistive technologies.

Can I run an accessibility audit on large web applications with dynamic content?

Yes, you can audit large web applications with dynamic content. The audit evaluates complex forms and navigation across small sites and large apps, enforcing WCAG criteria and providing targeted remediation guidance for assistive technology compatibility.

How does an a11y audit identify violations against POUR principles?

An a11y audit identifies POUR principle violations by evaluating web pages against WCAG 2.2 criteria. It analyzes forms, navigation, and dynamic content, outputting a prioritized remediation plan with evidence detailing why specific elements fail compliance.

Why does my web application fail Lighthouse accessibility checks for screen readers?

Failing Lighthouse accessibility checks indicates issues with keyboard navigation, screen-reader compatibility, or dynamic content updates. A WCAG 2.2 audit isolates these failures, providing actionable remediation steps and evidence to resolve the underlying POUR violations.