skills.rest
SpinBoxx
SpinBoxxCOMMUNITY
Explore all skills by this author →
GitHub

fixing-accessibility

Audit HTML accessibility issues for WCAG compliance in web interfaces.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility defects in web interfaces cause barriers for keyboard and screen-reader users.

Core Features & Use Cases

  • Audit and fix ARIA labels, keyboard navigation, focus management, color contrast, and form errors.
  • Use when adding interactive controls, dialogs, or reviewing WCAG compliance.

Quick Start

Review a UI component and apply accessibility fixes following the guidelines.

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 for WCAG compliance issues in web interfaces?▼

To audit HTML for WCAG compliance, review interactive controls like buttons and dialogs to identify ARIA gaps, keyboard navigation barriers, and focus management defects. This process targets accessible names, color contrast, and form error handling to resolve screen-reader barriers.

What is the best way to fix keyboard navigation and focus management in web dialogs?▼

Fixing keyboard navigation and focus management requires auditing interactive controls to ensure proper focus trapping and logical tab order. You apply targeted ARIA attributes and structural HTML fixes to resolve accessibility gaps and restore keyboard operability.

How do I handle form error accessibility for screen reader users?▼

Handling form error accessibility involves auditing HTML forms to ensure errors are programmatically linked to inputs using ARIA. You apply targeted fixes to provide accessible names and ensure keyboard users receive proper validation feedback.

Can I use this approach to check ARIA labels and color contrast across buttons?▼

Yes, you can check ARIA labels and color contrast across buttons by auditing the HTML components. The process identifies missing accessible names and insufficient contrast ratios, allowing you to apply targeted fixes for full WCAG compliance.

Why do my interactive web controls fail keyboard accessibility tests?▼

Interactive web controls fail keyboard accessibility tests when HTML lacks proper ARIA roles, accessible names, or focus management. Auditing the interfaces identifies these specific gaps, enabling targeted fixes for keyboard navigation and screen-reader compatibility.

Related Skills

Explore More Software Engineering Skills→
AgentiveCityAgentiveCity
2

nextjs-ui-component-smith

Design and refactor reusable UI components in Next.js App Router with TypeScript, Tailwind, and shadcn/ui.

Official
Intermediate
unthinkmediaunthinkmedia

ux-accessibility-reviewer

A comprehensive accessibility review tool for the design and implementation of user interfaces.

Community
Intermediate
Community-AccessCommunity-Access
387

Contrast Master

Audit color contrast and visual accessibility for WCAG AA compliance.

Official
Advanced
InnerScopeHearingInnerScopeHearing

wcag-audit-patterns

Audit web content for WCAG 2.2 compliance with automated testing and remediation guidance.

Official
Intermediate