reviewing-accessibility

Review implemented UI code for WCAG AA compliance and accessibility violations.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/mattobee/skills --skill reviewing-accessibility-mattobee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-accessibility
Source: https://github.com/mattobee/skills/tree/main/skills/reviewing-accessibility
Command: npx skills add https://github.com/mattobee/skills --skill reviewing-accessibility-mattobee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps identify accessibility issues in implemented UI code to ensure WCAG AA compliance, reducing risk for users with disabilities and avoiding legal or reputational problems.

Core Features & Use Cases

  • Semantic HTML review to verify appropriate element usage and proper heading structure.
  • Keyboard navigation and focus management checks to ensure all interactive elements are reachable and usable.
  • ARIA usage and color-contrast review to validate accessible names and visual clarity across themes.
  • Use Case: A development team performs an accessibility audit on a new component before release to surface WCAG violations and generate actionable fixes.

Quick Start

Run a quick accessibility review on a page or component to generate a findings report and remediation suggestions.

Frequently Asked Questions about reviewing-accessibility

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

FAQPage Schema
How do I audit my UI code for WCAG AA compliance?

To audit UI code for WCAG AA compliance, review implemented components to identify accessibility violations across semantic HTML, keyboard navigation, focus management, ARIA usage, and visual contrast. This process generates a findings report with actionable remediation suggestions for pre-release workflows.

What is checked during an accessibility review for keyboard navigation and focus management?

An accessibility review for keyboard navigation verifies that all interactive elements are reachable and usable without a mouse. Focus management checks ensure the focus order is logical and visible, validating that users navigating via keyboard can operate the UI effectively.

Can I use this to check ARIA usage and color contrast in my components?

Yes, you can check ARIA usage and color contrast in your components. The review validates ARIA implementation to ensure accurate accessible names and verifies visual contrast to maintain clarity across different visual themes for WCAG alignment.

Does this accessibility review check semantic HTML and heading structure?

Yes, this accessibility review checks semantic HTML to verify appropriate element usage. It validates proper heading structure to ensure the document outline is logical, which helps assistive technologies interpret the page content accurately.

What is the best way to find accessibility violations before a component release?

The best way to find accessibility violations before a component release is to run a dedicated UI accessibility audit. This surfaces WCAG failures in semantic HTML, keyboard navigation, and ARIA, providing actionable fixes to integrate into your code review process.

Why do I need to review implemented UI code for accessibility?

You need to review implemented UI code for accessibility to reduce risk for users with disabilities and avoid potential legal or reputational problems. Identifying WCAG AA violations during development ensures interactive elements are usable and visually clear.