skills.rest
Tahona-AI
Tahona-AIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

fixing-accessibility

Evaluate UI code for accessibility issues against WCAG guidelines.

Updated Mar 10, 2026
Search Tags:#accessibility#a11y#ARIA#UI#focus management#keyboard support
One-click install
npx skills add https://github.com/Tahona-AI/website --skill fixing-accessibility-tahona-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/Tahona-AI/website/tree/main/.agents/skills/fixing-accessibility
Command: npx skills add https://github.com/Tahona-AI/website --skill fixing-accessibility-tahona-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating user interfaces that are usable by everyone, including people with disabilities.

Core Features & Use Cases

  • Accessibility Auditing: Review UI code to identify accessibility violations such as missing labels or improper focus management.
  • Guideline Enforcement: Provide instructions and rules to improve keyboard navigation, focus traps, and semantic markup.
  • Use Case: When updating a website with modal dialogs, use this Skill to evaluate focus trapping and ARIA attributes to ensure compliance with accessibility standards.

Quick Start

Use the fixing-accessibility skill to review the accessibility of your form component.

Frequently Asked Questions about fixing-accessibility

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

FAQPage Schema
How do I check my UI code for accessibility issues?▼

To check UI code for accessibility issues, analyze code snippets against WCAG guidelines to identify violations like missing labels, improper focus management, and incorrect semantic markup.

How does focus management work for accessible modal dialogs?▼

Focus management for accessible modal dialogs works by implementing focus traps to keep keyboard navigation within the dialog, while using proper ARIA attributes to maintain accessibility compliance.

What is the best way to evaluate keyboard navigation in web interfaces?▼

The best way to evaluate keyboard navigation is to audit UI code for proper focus management and semantic markup, ensuring all interactive elements are reachable and operable without a mouse.

Can I audit a form component for ARIA attribute compliance?▼

Yes, you can audit a form component for ARIA attribute compliance by providing the UI code snippet for evaluation to detect missing labels and verify proper semantic markup.

When do I need to review ARIA attributes for WCAG compliance?▼

You need to review ARIA attributes for WCAG compliance when updating web interfaces with interactive elements like modal dialogs, ensuring keyboard support and semantic markup meet accessibility standards.

Why does my UI code fail keyboard support tests?▼

UI code fails keyboard support tests due to accessibility issues like missing focus management, improper focus traps, or lack of semantic markup, which prevent users from navigating without a mouse.

Related Skills

Explore More Content & Communication Skills→
junDevCodesjunDevCodes
2

web-design-guidelines

Enforce Web Interface Guidelines compliance across UI components and pages.

Community
Intermediate
rsmdtrsmdt
381

accessibility-standards

Apply WCAG 2.1 AA accessible design patterns to digital interfaces.

Community
Advanced
hulusi-tunchulusi-tunc
3

keyboard-review

Identify keyboard navigation and focus-management issues across UI interfaces.

Community
Intermediate
CivicActionsCivicActions
2

accessibility-audit

Audit web pages and components for WCAG 2.1 AA and Section 508 compliance.

Official
Advanced