fixing-accessibility

Identify and fix UI accessibility violations with code-level fixes per WCAG guidelines.

Updated Jul 15, 2023
One-click install
npx skills add https://github.com/ulasalyesil/personal-website-v2 --skill fixing-accessibility-ulasalyesil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/ulasalyesil/personal-website-v2/tree/main/.agents/skills/fixing-accessibility
Command: npx skills add https://github.com/ulasalyesil/personal-website-v2 --skill fixing-accessibility-ulasalyesil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses and rectifies accessibility issues within user interfaces, ensuring digital products are usable by everyone, regardless of ability.

Core Features & Use Cases

  • Issue Identification: Pinpoints specific accessibility violations in UI elements.
  • Violation Explanation: Clearly states why a violation is problematic.
  • Concrete Fixes: Provides actionable, code-level suggestions for remediation.
  • Use Case: When developing a new form, use this Skill to review the input fields and ensure they have proper labels and error messaging for screen reader users.

Quick Start

Use the fixing-accessibility skill to review the file main.jsx for accessibility violations.

Frequently Asked Questions about fixing-accessibility

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

FAQPage Schema
How do I fix accessibility issues in my web UI?

Fix accessibility issues by identifying specific WCAG violations in UI elements, explaining why they are problematic, and providing concrete code-level fixes for keyboard access, focus management, and semantics.

How do I ensure my form inputs meet WCAG keyboard navigation guidelines?

Ensure form inputs meet WCAG keyboard navigation guidelines by applying concrete code fixes that enforce proper accessible names, error messaging, and logical focus management for screen reader users.

What is the best way to debug a11y violations in interactive dialogs?

The best way to debug a11y violations in interactive dialogs is to analyze the UI structure against WCAG standards, identify missing semantics or focus traps, and apply targeted code-level remediation.

Can I use this to automatically correct poor color contrast in user interfaces?

Yes, you can correct poor color contrast in user interfaces by reviewing the code against WCAG contrast requirements, identifying the specific violations, and applying the suggested code-level adjustments.

Does this work for reviewing existing JSX files for screen reader compatibility?

Yes, this works for reviewing existing JSX files by scanning the interactive UI elements and forms to identify screen reader compatibility issues and providing actionable code modifications.