skills.rest
abereghici
abereghiciCOMMUNITY
Explore all skills by this author →
Website𝕏@alexandrubrgGitHub

web-accessibility

Analyze web interfaces for accessibility gaps and generate remediation plans.

Updated Apr 2, 2026
Search Tags:#accessibility#a11y#wcag#forms#keyboard#semantic-html#aria
One-click install
npx skills add https://github.com/abereghici/skills --skill web-accessibility-abereghici
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-accessibility
Source: https://github.com/abereghici/skills/tree/main/skills/web-accessibility
Command: npx skills add https://github.com/abereghici/skills --skill web-accessibility-abereghici

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Practical guidance to build inclusive web experiences by ensuring HTML semantics, ARIA usage, keyboard accessibility, and WCAG compliance across interfaces.

Core Features & Use Cases

  • Semantic HTML-first guidance to improve accessibility automatically
  • ARIA best practices and patterns for dynamic content, forms, and widgets
  • Keyboard navigation, focus management, and landmarks for predictable user experiences
  • Real-world scenarios including forms, menus, dialogs, and interactive components with accessible patterns

Quick Start

Analyze a page for accessibility gaps and generate a prioritized remediation plan.

Frequently Asked Questions about web-accessibility

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

FAQPage Schema
How do I make web forms accessible with ARIA and semantic HTML?▼

Accessible web forms require semantic HTML elements first, supplemented by ARIA attributes for dynamic content. This provides practical guidance on accessible naming, keyboard navigation, and input patterns to ensure forms are usable with assistive technologies across websites and single-page apps.

What is the best way to manage keyboard navigation and focus in single-page apps?▼

Keyboard navigation in single-page apps requires proper focus management and landmark roles for predictable user experiences. This delivers ARIA patterns and focus management techniques for dynamic content, dialogs, and interactive components to maintain accessibility during route changes and UI updates.

When do I need ARIA attributes for dynamic content and widgets?▼

ARIA attributes are needed when dynamic content and custom widgets lack semantic HTML equivalents. This outlines ARIA rules and best practices for menus, dialogs, and interactive components, ensuring dynamic updates are announced correctly to assistive technologies.

How to check WCAG compliance and generate a remediation plan for an interface?▼

WCAG compliance checking involves analyzing a page for accessibility gaps and generating a prioritized remediation plan. This provides testing guidelines and practical fixes for semantic HTML, ARIA usage, and keyboard accessibility to satisfy WCAG requirements across interfaces.

Does this approach work for making interactive components like dialogs and menus accessible?▼

Yes, making interactive components like dialogs and menus accessible is covered through real-world scenarios and ARIA patterns. It supplies specific guidance for widgets, forms, and navigation, ensuring keyboard accessibility and proper semantic roles for complex UI elements.

Related Skills

Explore More Software Engineering Skills→
afonsolelisafonsolelis

codigo-html

Enforce clean, semantic HTML5 with mandatory boilerplate and validation.

Community
Basic
nvimcraftnvimcraft

wcag-audit

Audit web interfaces for WCAG compliance and remediation requirements.

Community
Advanced
nanorepublicananorepublica
61

Frontend Accessibility

Enforce frontend accessibility compliance in HTML, CSS, and JavaScript components.

Community
Basic
InnerScopeHearingInnerScopeHearing

wcag-audit-patterns

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

Official
Intermediate