accessibility-wcag

Ensure web applications meet WCAG 2.1/2.2 accessibility standards.

1|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill accessibility-wcag-pascallammers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-wcag
Source: https://github.com/pascallammers/mylo-travel-concierge-v2/tree/main/.factory/skills/accessibility-wcag
Command: npx skills add https://github.com/pascallammers/mylo-travel-concierge-v2 --skill accessibility-wcag-pascallammers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures web applications are usable by everyone, regardless of ability, by adhering to established accessibility standards.

Core Features & Use Cases

  • WCAG Compliance: Guides development to meet WCAG 2.1/2.2 AA or AAA standards.
  • Semantic HTML & ARIA: Promotes correct use of HTML elements and ARIA attributes for assistive technologies.
  • Keyboard Navigation & Focus Management: Ensures all interactive elements are accessible via keyboard and focus is managed logically.
  • Use Case: When developing a new modal dialog, use this skill to ensure it's properly announced by screen readers, navigable with the keyboard, and has appropriate ARIA attributes.

Quick Start

Use the accessibility-wcag skill to ensure the main navigation menu is fully keyboard accessible.

Frequently Asked Questions about accessibility-wcag

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

FAQPage Schema
How do I make my web application accessible with WCAG guidelines?

To make web applications accessible, ensure compliance with WCAG 2.1/2.2 standards by applying perceivable, operable, understandable, and robust design principles. This involves using semantic HTML, managing keyboard navigation, and implementing correct ARIA attributes for assistive technologies.

How do I add ARIA attributes for screen reader compatibility?

Add ARIA attributes to ensure screen reader compatibility by using semantic HTML elements correctly and managing focus logically. This guarantees interactive elements like modal dialogs are properly announced and navigable by assistive technologies.

What is the best way to ensure keyboard navigation and focus management in a modal dialog?

The best way to ensure keyboard navigation in a modal dialog is to manage focus logically and apply appropriate ARIA attributes. This guarantees all interactive elements are operable via keyboard and properly announced to screen readers.

When do I need to use semantic HTML for inclusive UI component development?

You need to use semantic HTML for inclusive UI component development whenever building interactive elements like navigation menus. It ensures perceivable and operable structures that meet WCAG AA or AAA standards for assistive technologies.

Does this approach support building inclusive web applications for WCAG AAA standards?

Yes, this approach supports building inclusive web applications by guiding development to meet WCAG 2.1/2.2 AA or AAA standards. It focuses on robust design principles, semantic HTML, and screen reader compatibility.