fixing-accessibility

Audit and fix HTML accessibility issues for WCAG compliance.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/Benjamindaoson/Financial_Asset_QA_System_master --skill fixing-accessibility-benjamindaoson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/Benjamindaoson/Financial_Asset_QA_System_master/tree/main/.agents/skills/fixing-accessibility
Command: npx skills add https://github.com/Benjamindaoson/Financial_Asset_QA_System_master --skill fixing-accessibility-benjamindaoson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and fix HTML accessibility issues across UI components to meet WCAG standards, ensuring inclusive experiences.

Core Features & Use Cases

  • ARIA labeling and semantics for all controls
  • Keyboard navigation, focus management, and modal behavior
  • Color contrast, error messaging, and focus states for forms
  • Use when building interactive controls, dialogs, or reviewing WCAG compliance

Quick Start

Audit a UI element for accessibility gaps and apply targeted fixes.

Frequently Asked Questions about fixing-accessibility

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

FAQPage Schema
How do I fix HTML accessibility issues for keyboard navigation and ARIA labeling?

Fix HTML accessibility issues by auditing interactive controls, forms, and modals to apply ARIA semantics, manage keyboard focus, and ensure WCAG compliance. This process targets interactive widgets to ensure inclusive user experiences.

What is the best way to manage focus when closing a modal dialog for WCAG compliance?

The best way to manage focus in a modal dialog is to trap focus while open and return it to the triggering element upon close. This focus-managed widget behavior ensures keyboard navigation meets WCAG standards.

How do I add accessible error messaging to UI forms?

Add accessible error messaging to UI forms by applying ARIA labeling to identify invalid fields and providing clear text descriptions of the errors. This ensures forms meet color contrast and WCAG compliance requirements.

Do I need ARIA attributes on every interactive control for WCAG compliance?

You need ARIA attributes on interactive controls only when native HTML semantics are insufficient. Auditing UI elements helps identify gaps where ARIA labeling and focus states are required to ensure proper keyboard navigation.

Does this accessibility audit apply to color contrast considerations and focus states?

Yes, the accessibility audit applies to color contrast considerations and visible focus states. It evaluates UI components to ensure forms and interactive controls maintain sufficient contrast and keyboard visibility for WCAG compliance.