skills.rest
alexejluft
alexejluftCOMMUNITY
Explore all skills by this author →
GitHub

building-accessibly

Enforce web accessibility standards including WCAG compliance and keyboard navigation.

Updated Aug 27, 2026
Search Tags:#accessibility#a11y#screen reader#keyboard navigation#wcag#aria#focus states
One-click install
npx skills add https://github.com/alexejluft/brudi --skill building-accessibly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: building-accessibly
Source: https://github.com/alexejluft/brudi/tree/main/skills/building-accessibly
Command: npx skills add https://github.com/alexejluft/brudi --skill building-accessibly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make web applications usable by everyone, including individuals with disabilities, by adhering to accessibility standards.

Core Features & Use Cases

  • Keyboard Navigation: Ensures interactive elements can be accessed and operated using only a keyboard.
  • Screen Reader Support: Provides necessary semantic information for assistive technologies.
  • WCAG Compliance: Guides development towards meeting Web Content Accessibility Guidelines.
  • Focus States: Mandates visible focus indicators for keyboard users.
  • Form Labels: Enforces proper labeling for all form elements.
  • Color Contrast: Advises on sufficient contrast ratios for text and UI elements.
  • ARIA Usage: Recommends appropriate use of ARIA attributes when native HTML is insufficient.
  • Reduced Motion: Supports users sensitive to animations.

Quick Start

Use the building-accessibly skill to ensure all interactive elements have visible focus states and that all form inputs are properly labeled.

Frequently Asked Questions about building-accessibly

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

FAQPage Schema
How do I make web applications accessible for screen reader users?▼

To make web applications accessible for screen reader users, you must provide necessary semantic information for assistive technologies. This involves using appropriate ARIA attributes when native HTML is insufficient and ensuring proper form labels are present.

What are the WCAG compliance requirements for keyboard navigation?▼

WCAG compliance for keyboard navigation requires ensuring all interactive elements can be accessed and operated using only a keyboard. This includes mandating visible focus states so keyboard users can clearly see which element is currently active.

How do I implement visible focus states for accessible web forms?▼

Implementing visible focus states for accessible web forms requires mandating visible focus indicators for keyboard users. Additionally, you must enforce proper labeling for all form elements to ensure they are fully accessible.

When do I need to use ARIA attributes for web accessibility?▼

You need to use ARIA attributes for web accessibility when native HTML is insufficient to convey semantic information. Appropriate ARIA usage provides screen reader compatibility and ensures interactive elements are properly identified.

How do I handle reduced motion preferences for accessibility compliance?▼

Handling reduced motion preferences for accessibility compliance involves supporting users sensitive to animations. This ensures your web application accommodates individuals who experience motion sensitivity by adjusting animation behaviors accordingly.

How do I ensure sufficient color contrast for accessible UI elements?▼

Ensuring sufficient color contrast for accessible UI elements involves advising on contrast ratios for text and UI components. This practice guides development towards meeting Web Content Accessibility Guidelines (WCAG).

Related Skills

Explore More Software Engineering Skills→
balkhaevbalkhaev

shadcn

Manage shadcn/ui component lifecycle and enforce Tailwind CSS patterns.

Community
Advanced
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate
Arnutt-NArnutt-N

accessibility-helper

Provide WCAG-compliant accessibility utilities, components, and hooks for HR-IMS frontends.

Community
Advanced
Montte-erpMontte-erp
6

wcag-audit-patterns

Audit web pages for WCAG 2.2 violations with automated and manual checks.

Official
Intermediate