skills.rest
alslimany
alslimanyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

fixing-accessibility

Identify and fix accessibility issues in UI components and interaction patterns.

Updated Apr 15, 2026
Search Tags:#accessibility#a11y#ui-design#keyboard-navigation#inclusive-design#focus-management#a11y-guidelines
One-click install
npx skills add https://github.com/alslimany/tams --skill fixing-accessibility-alslimany
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fixing-accessibility
Source: https://github.com/alslimany/tams/tree/main/.cursor/skills/fixing-accessibility
Command: npx skills add https://github.com/alslimany/tams --skill fixing-accessibility-alslimany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify and resolve accessibility issues in user interfaces, ensuring inclusive design and usable interfaces for all users.

Core Features & Use Cases

  • Automated checks for accessible names, keyboard navigation, and focus management.
  • Guidance for applying ARIA where appropriate without compromising native semantics.
  • Use Case: Review common UI components such as buttons, forms, dialogs, and menus for accessibility gaps.

Quick Start

Review the current UI components for focus visibility and add or adjust aria-labels as needed.

Frequently Asked Questions about fixing-accessibility

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

FAQPage Schema
How do I fix keyboard navigation and focus management issues in UI components?▼

Fix keyboard navigation and focus management issues by reviewing UI components for focus visibility, adjusting focus states, and resolving interaction pattern gaps to ensure accessible focus management across dialogs and menus.

When do I need to add ARIA attributes for accessible names on buttons and forms?▼

Add ARIA attributes when native semantics are insufficient for accessible names. Apply aria-labels to buttons and forms to meet accessibility guidelines without compromising underlying HTML semantics, ensuring inclusive design for all users.

What is the best way to audit web and app UIs for inclusive design gaps?▼

Auditing UIs for inclusive design gaps involves checking buttons, forms, dialogs, and menus for accessible names, keyboard access, focus management, and semantic correctness aligned to provided accessibility guidelines.

Does this approach work for both web and mobile app UI accessibility?▼

Yes, this approach works across web and app UIs, resolving accessibility issues in interaction patterns and components like menus and dialogs to ensure usable interfaces for all users.

Why are my ARIA semantics breaking native HTML accessibility?▼

ARIA semantics break native HTML accessibility when applied unnecessarily or incorrectly. This skill provides guidance to apply ARIA appropriately without compromising native semantics, ensuring semantic correctness and accessible names.

Related Skills

Explore More Design & Creative Skills→
shawn-sandyshawn-sandy

wcag-compliance-reviewer

Identify WCAG 2.1 AA accessibility violations in HTML/CSS and React/TypeScript code.

Community
Intermediate
BWCbewchanBWCbewchan
5

web-accessibility

Implement WCAG-aligned ARIA patterns and keyboard navigation in web applications.

Community
Intermediate
Higashi-KotaHigashi-Kota

ui-component

Build accessible React UI components with design tokens and ARIA patterns.

Community
Advanced
lord-vinayaklord-vinayak

full-accessibility-audit

Orchestrate multiple audit-category skills into a unified accessibility report.

Community
Advanced