skills.rest
jscraik
jscraikCOMMUNITY
Explore all skills by this author →
Website𝕏@jscraikGitHub

fixing-accessibility

Audit and fix HTML accessibility issues against WCAG 2.2 criteria.

8|4|Updated Jan 15, 2026
Search Tags:#html#accessibility#web development#keyboard navigation#wcag#aria
One-click install
npx skills add https://github.com/jscraik/Agent-Skills --skill fixing-accessibility-jscraik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/jscraik/Agent-Skills/tree/main/frontend/website/fixing-accessibility
Command: npx skills add https://github.com/jscraik/Agent-Skills --skill fixing-accessibility-jscraik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses and rectifies issues related to web accessibility, ensuring digital content is usable by everyone, including individuals with disabilities.

Core Features & Use Cases

  • Audit and Fix: Identifies and corrects accessibility violations in HTML, including ARIA labels, keyboard navigation, focus management, color contrast, and form errors.
  • WCAG Compliance: Ensures adherence to WCAG 2.2 success criteria.
  • Use Case: When developing a new interactive component or form, use this Skill to audit it against accessibility standards and receive concrete suggestions for improvement, ensuring it's usable via keyboard and screen readers.

Quick Start

Use the fixing-accessibility skill to audit the file 'button.html' 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 fix HTML accessibility issues for keyboard navigation and ARIA labels?▼

To fix HTML accessibility issues, audit your interactive controls to ensure proper ARIA labels, keyboard navigation, and focus management. Apply minimal, targeted fixes to meet WCAG 2.2 success criteria for screen reader compatibility.

How do I audit a web form for WCAG 2.2 compliance?▼

Audit web forms for WCAG 2.2 compliance by checking for proper focus management, color contrast, and form error identification. Ensure all interactive elements are fully operable via keyboard and screen readers to rectify accessibility violations.

What is the best way to ensure focus management in interactive HTML dialogs?▼

The best way to ensure focus management in HTML dialogs is to apply targeted fixes that trap focus within the dialog and restore it upon closure. This ensures keyboard navigation and screen reader interactions meet WCAG accessibility standards.

Can I use this accessibility audit on existing HTML files?▼

Yes, you can audit existing HTML files for accessibility issues. The tool identifies and corrects violations in ARIA labels, keyboard navigation, and color contrast, providing concrete suggestions for improvement without requiring a full rewrite.

Why does my interactive control fail keyboard navigation despite having ARIA labels?▼

Interactive controls may fail keyboard navigation if focus management is missing or incorrectly implemented. Proper accessibility requires both ARIA labels for screen reader identification and logical tab order to meet WCAG 2.2 success criteria.

Related Skills

Explore More Design & Creative Skills→
lord-vinayaklord-vinayak

accessible-forms

Assess form accessibility for label association, validation, input types, and keyboard navigation.

Community
Advanced
ulasalyesilulasalyesil

wcag-audit-patterns

Audit websites against WCAG 2.2 with checklists and remediation examples.

Community
Advanced
thec3ukthec3uk

Frontend Accessibility

Guide frontend code to meet accessibility standards like ARIA and keyboard navigation.

Official
Basic
JhabbigJhabbig

wcag-audit-patterns

Audit web interfaces for WCAG 2.2 accessibility violations.

Community
Advanced