accessibility-reviewer

Identify and report accessibility gaps in UI designs.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/saranskumar/anti-slop --skill accessibility-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-reviewer
Source: https://github.com/saranskumar/anti-slop/tree/main/skills/accessibility-reviewer
Command: npx skills add https://github.com/saranskumar/anti-slop --skill accessibility-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams assess if UI designs meet accessibility standards across keyboard navigation, screen reader compatibility, contrast, focus management, and semantic structure.

Core Features & Use Cases

  • Accessibility review of UI components, forms, dialogs, and dynamic content.
  • Guidance on focus order, labeling, color contrast, motion respect, and assistive technology support.
  • Real-world example: review a signup form to ensure all controls are reachable via keyboard and properly announced by screen readers.

Quick Start

Review a UI mockup or component in your project and generate a prioritized accessibility fixes list.

Frequently Asked Questions about accessibility-reviewer

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

FAQPage Schema
How do I check if my UI design supports keyboard navigation and screen readers?

An accessibility review evaluates UI components against standards for keyboard reachability, screen reader announcements, semantic HTML, focus order, and color contrast. It generates a prioritized list of concrete fixes for developers to implement.

What is focus management and why does it matter for dynamic UI content?

Focus management controls where keyboard focus moves during dynamic UI changes, like opening dialogs or menus. It ensures interactive elements remain reachable and logically ordered for keyboard and screen reader users.

How do I audit color contrast for accessibility compliance in UI components?

You audit color contrast by evaluating foreground and background color pairs against WCAG contrast ratio thresholds. This identifies visual accessibility gaps and provides concrete fixes to ensure text remains readable for users with visual impairments.

Can I review complex forms and dialogs for screen reader compatibility?

Yes, you can review complex forms and dialogs for screen reader compatibility by checking semantic structure, labeling, and focus management. This ensures all controls are properly announced and reachable via keyboard navigation.

What is the best way to document accessibility fixes for developers?

The best way to document accessibility fixes is to generate a prioritized list mapping specific gaps in keyboard support, contrast, or semantics to concrete implementation requirements. This documentation provides actionable steps for developers to resolve issues.

Does semantic structure affect keyboard navigation in web applications?

Yes, semantic structure directly affects keyboard navigation by establishing logical tab order and context for assistive technologies. Using proper semantic elements ensures keyboard users can navigate menus, tables, and forms efficiently without missing interactive controls.