skills.rest
xobotyi
xobotyiCOMMUNITY
Explore all skills by this author →
𝕏@xobotyiGitHub

accessibility

Enforce WCAG 2.2 AA compliance in HTML, CSS, and JavaScript.

19|Updated Jan 30, 2026
Search Tags:#accessibility#web development#keyboard navigation#wcag#semantic html#aria
One-click install
npx skills add https://github.com/xobotyi/cc-foundry --skill accessibility-xobotyi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/xobotyi/cc-foundry/tree/main/plugins/frontend/skills/accessibility
Command: npx skills add https://github.com/xobotyi/cc-foundry --skill accessibility-xobotyi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that web content is usable by everyone, regardless of ability, by adhering to accessibility standards for semantic HTML, ARIA, and keyboard navigation.

Core Features & Use Cases

  • WCAG Compliance: Guides development and review against Web Content Accessibility Guidelines (WCAG).
  • Semantic HTML & ARIA: Promotes the use of native HTML elements and correct ARIA implementation.
  • Keyboard Navigation: Ensures all interactive elements are operable via keyboard.
  • Use Case: When writing new UI components, this skill will help you ensure they are perceivable, operable, understandable, and robust for all users, including those using screen readers or keyboard-only navigation.

Quick Start

Review the provided HTML code for accessibility issues and suggest improvements.

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 components WCAG compliant?▼

To make web components WCAG compliant, you must enforce semantic HTML, correct ARIA usage, and full keyboard navigation. This ensures UI components are perceivable, operable, understandable, and robust for all users.

How do I review HTML code for accessibility issues?▼

Reviewing HTML for accessibility issues involves checking against WCAG 2.2 AA criteria. You must validate the use of native semantic HTML, verify ARIA implementation, and test keyboard access to ensure screen reader support.

When do I need ARIA attributes for semantic HTML?▼

You need ARIA attributes when native semantic HTML cannot convey the necessary semantics. ARIA supplements HTML to ensure WCAG compliance, improving screen reader support and keyboard operability for interactive UI components.

Does this skill help fix CSS and JavaScript for screen reader support?▼

Yes, it applies to refactoring and debugging HTML, CSS, and JavaScript. It enforces WCAG standards for perceivability, operability, understandability, and robustness, specifically targeting screen reader support and keyboard access.

What are the limitations of using semantic HTML for web accessibility?▼

Semantic HTML alone cannot cover all custom widget interactions, requiring ARIA implementation to fill the gaps. WCAG 2.2 AA compliance also demands thorough testing of keyboard navigation to ensure all interactive elements are operable.

Related Skills

Explore More Design & Creative Skills→
sigmadigitalzasigmadigitalza
1

frontend-accessibility-review

Audit web frontends for WCAG 2.2 AA conformance with static and live checks.

Official
Advanced
Sir-chawakornSir-chawakorn
33

accessibility-audit

Audit web content for WCAG 2.1 compliance and fix accessibility issues.

Community
Intermediate
raybargasraybargas

Frontend Accessibility

Enforce frontend accessibility compliance in web UI code.

Community
Basic
thiagoooo34252thiagoooo34252
1

engineer-accessibility

Scan web applications for WCAG 2.2 violations using axe-core.

Community
Advanced