skills.rest
stamatim
stamatimCOMMUNITY
Explore all skills by this author →
GitHub

fixing-accessibility

Identify and fix HTML accessibility issues in UI components.

Updated Aug 23, 2026
Search Tags:#accessibility#a11y#usability#wcag#focus#keyboard#aria
One-click install
npx skills add https://github.com/stamatim/agent-skills --skill fixing-accessibility-stamatim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/stamatim/agent-skills/tree/main/.agents/skills/fixing-accessibility
Command: npx skills add https://github.com/stamatim/agent-skills --skill fixing-accessibility-stamatim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and fix HTML accessibility issues across UI components to meet WCAG guidelines, including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.

Core Features & Use Cases

  • ARIA labeling and semantic improvements for interactive controls
  • Keyboard navigation improvements and focus management
  • Color contrast enhancements and accessible error messaging
  • Use case: reviewing a modal dialog and ensuring all focus is trapped while open

Quick Start

Run an accessibility audit on the current UI and apply fixes for ARIA labels, keyboard navigation, and focus management.

Frequently Asked Questions about fixing-accessibility

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

FAQPage Schema
How do I audit HTML accessibility issues in my UI components?▼

ARIA attributes improve accessibility when native HTML elements lack semantic meaning. Apply them to interactive controls, forms, and dialogs to provide screen reader labels, define roles, and manage focus states when standard HTML cannot convey the necessary context.

How do I manage keyboard focus inside a modal dialog?▼

Accessible form error handling requires providing text-based error messages linked to inputs via ARIA attributes. This ensures screen readers announce validation failures clearly, meeting WCAG compliance for accessible error messaging and keyboard focus management.

Does this work for reviewing WCAG compliance across existing web interfaces?▼

Yes, it can review WCAG compliance across existing web interfaces by evaluating interactive controls, forms, and dialogs. It checks for ARIA labeling, keyboard navigation, focus management, color contrast, and accessible error handling to identify and fix violations.

What is the best way to fix accessibility issues in interactive HTML controls?▼

The best way to fix accessibility issues in interactive HTML controls is to audit them for WCAG compliance and apply semantic improvements. This involves correcting ARIA labels, ensuring proper keyboard navigation, and verifying color contrast meets usability standards.

Related Skills

Explore More Software Engineering Skills→
suhwansuhwan

web-design-guidelines

Analyze UI source code for accessibility, semantic HTML, and keyboard navigation issues.

Community
Intermediate
serkan-ozalserkan-ozal
7

accessibility-audit

Audits web accessibility via ARIA snapshots, AX tree analysis, WCAG validation, and keyboard navigation testing using browser-devtools-cli.

Community
Intermediate
nist0nist0

html-css

Generates semantic HTML/CSS code with accessibility and responsive design.

Community
Advanced
pvillegapvillega
23

wcag-audit

Detect WCAG violations via ESLint plugins and axe-core runtime scans.

Community
Advanced