fixing-accessibility

Audit HTML documents for accessibility issues and suggest WCAG-based fixes.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/wpsadi/stock-agent --skill fixing-accessibility-wpsadi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/wpsadi/stock-agent/tree/main/.agents/skills/fixing-accessibility
Command: npx skills add https://github.com/wpsadi/stock-agent --skill fixing-accessibility-wpsadi

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses HTML accessibility issues, ensuring compliance with WCAG standards and enhancing user experience for keyboard and screen reader users.

Core Features & Use Cases

  • Accessibility Audit: Identifies and reports HTML accessibility issues.
  • Fix Recommendations: Provides concrete suggestions for fixing identified issues.
  • Use Case: When you need to ensure your web content is accessible, use this Skill to scan your HTML files and receive detailed reports on potential issues.

Quick Start

Apply the fixing-accessibility skill to the current page to check for accessibility issues.

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 files for WCAG 2.1 accessibility issues?

To audit HTML files for WCAG 2.1 accessibility issues, apply an automated audit to scan your web documents and receive detailed reports identifying potential compliance errors.

What's the best way to fix HTML accessibility problems for screen reader users?

The best way to fix HTML accessibility problems is to scan your code against WCAG guidelines to identify issues and apply concrete fix recommendations to improve screen reader compatibility.

Do I need to know WCAG standards to fix web accessibility issues?

Yes, fixing web accessibility issues requires knowledge of HTML and WCAG 2.1 standards to properly understand audit reports and implement the suggested code fixes.

How does an accessibility audit identify keyboard navigation barriers in HTML?

An accessibility audit identifies keyboard navigation barriers by evaluating HTML documents against WCAG standards, detecting missing focus states or semantic tags, and suggesting concrete fixes.

What HTML accessibility issues can I expect to find during a WCAG audit?

During a WCAG audit, you can find HTML accessibility issues like missing ARIA attributes, incorrect semantic structure, and inadequate keyboard navigation support, all reported with concrete fix suggestions.

Can I use automated accessibility audits for large HTML web workflows?

Yes, you can use automated accessibility audits for web development workflows to ensure large-scale HTML compliance with accessibility standards and improve user experience.