accessibility-optimizer

Audits and fixes UI accessibility issues against WCAG 2.2 standards.

Updated May 24, 2026
One-click install
npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill accessibility-optimizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-optimizer
Source: https://github.com/haJ1t/senior-dev-squad-skills/tree/main/plugins/senior-dev-squad/skills/accessibility-optimizer
Command: npx skills add https://github.com/haJ1t/senior-dev-squad-skills --skill accessibility-optimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of ensuring UI accessibility, providing a comprehensive auditing and automated fixing solution for UIs.

Core Features & Use Cases

  • WCAG 2.2 AA/AAA Auditing: Performs audits against WCAG 2.2 standards, covering Perceivable, Operable, Understandable, and Robust principles.
  • Automated Fixing: Automatically corrects issues found during the audit, including color contrast, keyboard navigation, and screen reader compatibility.
  • Use Case: When developing a web application, use this Skill to ensure all UI components meet accessibility standards before deployment.

Quick Start

Run the accessibility-optimizer skill to audit and fix accessibility issues in your web application.

Frequently Asked Questions about accessibility-optimizer

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

FAQPage Schema
How do I audit my web application for WCAG 2.2 compliance?

Auditing for WCAG 2.2 compliance involves checking UI components against Perceivable, Operable, Understandable, and Robust principles. This process evaluates ARIA usage, color contrast, keyboard navigation, and screen reader compatibility to identify accessibility issues.

Can I automatically fix color contrast and keyboard navigation issues in my UI?

Automated fixing corrects UI accessibility issues like insufficient color contrast and broken keyboard navigation. It adjusts ARIA attributes and structural formatting to ensure screen reader compatibility without requiring manual code adjustments.

What is included in a WCAG 2.2 AA and AAA accessibility audit?

A WCAG 2.2 AA and AAA accessibility audit evaluates web UIs across four core principles: Perceivable, Operable, Understandable, and Robust. It tests screen reader compatibility, keyboard navigation, color contrast ratios, and ARIA implementation.

Does automated accessibility fixing work with ARIA attributes and screen reader compatibility?

Automated accessibility fixing works by evaluating and correcting ARIA attributes to ensure screen reader compatibility. It adjusts UI components during the audit process to meet WCAG 2.2 requirements for operability and robustness.

When do I need to run an accessibility audit before deploying a web application?

You need to run an accessibility audit before deploying a web application to ensure all UI components meet WCAG 2.2 standards. This prevents deploying non-compliant interfaces by verifying keyboard navigation and screen reader support.

What is the best way to ensure UI components meet accessibility standards?

The best way to ensure UI components meet accessibility standards is through comprehensive WCAG 2.2 auditing combined with automated fixing. This validates color contrast, keyboard navigation, and ARIA usage to guarantee compliance.