skills.rest
drimchansky
drimchanskyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

_accessibility

Audits web interfaces for semantic HTML, ARIA, and keyboard navigation compliance.

Updated Feb 8, 2026
Search Tags:#inclusive design#accessibility#a11y#web development#keyboard navigation#aria
One-click install
npx skills add https://github.com/drimchansky/agents-kit --skill accessibility-drimchansky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: _accessibility
Source: https://github.com/drimchansky/agents-kit/tree/main/skills/_accessibility
Command: npx skills add https://github.com/drimchansky/agents-kit --skill accessibility-drimchansky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that web interfaces are usable by everyone, regardless of their abilities, by adhering to accessibility standards and best practices.

Core Features & Use Cases

  • Semantic HTML: Guides the use of native HTML elements for better accessibility.
  • ARIA Implementation: Provides rules for using ARIA attributes correctly when native elements are insufficient.
  • Keyboard Navigation: Ensures all interactive elements are operable via keyboard.
  • Visual Design: Addresses contrast ratios, color reliance, and touch target sizes.
  • Form Accessibility: Focuses on proper labeling, grouping, and error indication.
  • Use Case: Reviewing a new UI component to ensure it's navigable with a keyboard, announced correctly by screen readers, and has sufficient color contrast.

Quick Start

Apply accessibility best practices to the provided UI code snippet.

Frequently Asked Questions about _accessibility

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

FAQPage Schema
How do I make my web interface usable with keyboard navigation?▼

Keyboard navigation is achieved by ensuring all interactive elements are operable via keyboard. This involves using semantic HTML elements, implementing proper ARIA patterns, and managing focus states so users can navigate without a mouse.

When do I need ARIA attributes for web accessibility?▼

ARIA attributes are needed for web accessibility when native HTML elements are insufficient for conveying semantic meaning. You should use ARIA to provide correct screen reader announcements and roles for dynamic content updates and interactive UI components.

How to check color contrast for WCAG compliance?▼

To check color contrast for WCAG compliance, evaluate your visual design against WCAG guidelines for contrast ratios. Ensure text and interactive elements have sufficient contrast and do not rely on color alone to convey information.

What is the best way to handle form accessibility and error indication?▼

The best way to handle form accessibility is by using proper labeling, grouping related fields, and providing clear error indication. This ensures forms are announced correctly by screen readers and are fully operable by all users.

Does semantic HTML alone solve screen reader announcements?▼

Semantic HTML provides a strong foundation for screen reader announcements, but it does not solve everything. For dynamic content or complex interactive elements, you must supplement native elements with correct ARIA implementation to ensure proper accessibility.

Why does my dynamic content update not get announced by screen readers?▼

Dynamic content updates are not announced by screen readers when ARIA live regions or focus management are missing. You need to implement proper ARIA patterns to ensure accessibility tools recognize and announce changes in the web interface.

Related Skills

Explore More Design & Creative Skills→
JaivishChauhanJaivishChauhan
6

accessibility

Apply WCAG-compliant semantics to portfolio pages for keyboard and screen reader accessibility.

Community
Intermediate
samjhechtsamjhecht
4

frontend-accessibility-verification

Verify frontend UI accessibility compliance with axe-core, keyboard, screen reader, and Lighthouse audits.

Community
Advanced
remiconnessonremiconnesson

ui-design

Identify accessibility, layout, typography, color, form, and motion issues in HTML and CSS.

Community
Advanced
nimadorostkarnimadorostkar
25

accessibility

Audit web interfaces for WCAG 2.2 AA conformance.

Community
Advanced