skills.rest
MS33834
MS33834COMMUNITY
Explore all skills by this author →
GitHub

Accessibility Audit

Audit user interfaces for WCAG conformance gaps and accessibility barriers.

Updated Aug 27, 2026
Search Tags:#accessibility#a11y#screen reader#frontend#wcag#ui audit
One-click install
npx skills add https://github.com/MS33834/AI-SKILL --skill accessibility-audit-ms33834
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Accessibility Audit
Source: https://github.com/MS33834/AI-SKILL/tree/main/skills/accessibility-audit
Command: npx skills add https://github.com/MS33834/AI-SKILL --skill accessibility-audit-ms33834

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch accessibility barriers in a UI or component before release, reducing the risk of keyboard traps, missing labels, poor contrast, and other usability failures for people who rely on assistive technology.

Core Features & Use Cases

  • WCAG-focused review: Evaluates keyboard navigation, screen reader support, contrast, motion, forms, and touch targets against a target conformance level.
  • Actionable remediation: Maps findings to specific WCAG criteria and pairs each issue with example fixes.
  • Practical QA support: Useful for pre-launch audits, component library reviews, and triaging accessibility bugs in web interfaces.

Quick Start

Ask the skill to audit your UI description or markup against your target WCAG level and return findings with fixes.

Frequently Asked Questions about Accessibility Audit

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

FAQPage Schema
How do I audit my web UI for WCAG conformance gaps and screen reader barriers?▼

To audit web UI for WCAG conformance, provide your UI description or markup to evaluate keyboard navigation, screen reader support, contrast, and form semantics. The process maps findings directly to WCAG criteria with severity levels and example fixes.

What is the best way to check a component library for accessibility barriers before release?▼

Checking a component library for accessibility barriers involves reviewing keyboard traps, missing labels, and motion issues against a target WCAG level. This returns WCAG-mapped findings with actionable fix examples and manual test guidance.

Can I use this approach to triage accessibility bugs in frontend components?▼

Yes, you can triage accessibility bugs in frontend components by evaluating UI markup against WCAG criteria. It identifies issues like poor contrast and missing form semantics, providing severity ratings and remediation examples for each bug.

Does an accessibility audit cover keyboard navigation and color contrast checks?▼

An accessibility audit covers both keyboard navigation and color contrast checks alongside screen reader support, motion, and touch target evaluation. It assesses these UI elements against your specified WCAG conformance level to identify failures.

How do I get actionable remediation guidance for missing form semantics and WCAG failures?▼

To get actionable remediation guidance for WCAG failures, audit your UI markup to receive mapped findings. Each accessibility issue is paired with specific fix examples, manual test instructions, and tool recommendations for resolution.

Related Skills

Explore More Software Engineering Skills→
FernanSuozaFernanSuoza

web-frontend-development

Implement accessible frontend UI components with design-system tokens and automated tests.

Community
Advanced
runkidsrunkids
11

accessibility

Audit web accessibility against WCAG 2.1 and generate remediation plans.

Community
Basic
BigPapiCBBigPapiCB
2

accessibility

Identify and enforce WCAG compliance, ARIA patterns, and keyboard operability in UI components.

Community
Advanced
nimadorostkarnimadorostkar
25

accessibility

Audit web interfaces for WCAG 2.2 AA conformance.

Community
Advanced