accessibility-audit

Audit and correct WCAG 2.1 AA issues in web UI code.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/MoxyWolfLLC/moxywolf-plugins --skill accessibility-audit-moxywolfllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/MoxyWolfLLC/moxywolf-plugins/tree/main/plugins/saas-frontend-designer/skills/accessibility-audit
Command: npx skills add https://github.com/MoxyWolfLLC/moxywolf-plugins --skill accessibility-audit-moxywolfllc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility-audit helps you quickly find and fix common barriers that prevent keyboard users and screen reader users from using your web interface effectively.

Core Features & Use Cases

  • WCAG AA-focused checklist: Covers semantic HTML, heading structure, keyboard navigation, focus management, color contrast, media alternatives, form accessibility, and ARIA patterns.
  • Actionable, example-driven fixes: Provides concrete implementation guidance for typical UI patterns (dialogs, custom controls, form errors, tables, landmarks).
  • Practical validation steps: Includes a screen reader testing quick check to verify announcements, landmarks, headings, and dynamic updates.

Quick Start

Use accessibility-audit to audit your current web page and rewrite the UI so it follows WCAG 2.1 AA guidance for semantics, keyboard navigation, focus states, contrast, and labeled forms.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I make my web UI pass WCAG 2.1 AA accessibility checks?

To pass WCAG 2.1 AA accessibility checks, audit your web interface to correct keyboard navigation failures, enforce semantic HTML structure, fix broken focus management, and ensure sufficient color contrast for screen reader operability.

How do I fix keyboard navigation and focus management issues in HTML?

Fix keyboard navigation and focus management by enforcing keyboard operability, implementing visible focus indicators, and applying dialog focus trapping to ensure custom UI controls remain accessible without a mouse.

What is the best way to add semantic HTML and ARIA patterns for screen readers?

The best way to support screen readers is applying semantic HTML, correcting heading hierarchy, and using appropriate ARIA patterns to label forms and announce dynamic content or errors properly.

Can I use this to audit color contrast and missing alt text in my web interface?

Yes, you can audit color contrast to meet WCAG AA standards and remediate inaccessible media by adding appropriate alt text and ensuring dynamic content updates are screen-reader friendly.

How do I validate that my form fields are properly announced by screen readers?

Validate form field announcements by running a screen reader testing quick check to verify that labels, landmarks, headings, and dynamic error messages are correctly exposed to assistive technologies.

When do I need to trap focus in web dialogs for accessibility compliance?

You need to trap focus in web dialogs when implementing custom UI components to meet accessibility compliance, ensuring keyboard users cannot tab out of the dialog until it is explicitly closed.