accessibility

Generate semantic ARIA attributes for web and native platforms per WCAG 2.2.

2|Updated Apr 14, 2026

Search Tags:#inclusive design #accessibility #semantic HTML #ARIA #WCAG 2.2

Ready to run

npx skills add https://github.com/klu-dev/porting-ecc-to-vscode --skill accessibility-klu-dev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/klu-dev/porting-ecc-to-vscode/tree/main/.github/skills/accessibility
Command: npx skills add https://github.com/klu-dev/porting-ecc-to-vscode --skill accessibility-klu-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps ensure digital products are accessible to all users, including those with disabilities, by applying WCAG 2.2 standards and generating ARIA semantics.

Core Features & Use Cases

WCAG 2.2 Compliance: Implement technical standards for Perceivable, Operable, Understandable, and Robust (POUR) digital interfaces.
ARIA Semantics: Generate semantic ARIA attributes for Web and Native platforms (iOS/Android).
Use Case: Use this Skill to design a button on a website that is accessible to users with screen readers or keyboard navigation.

Quick Start

Use the accessibility skill to generate ARIA semantics for a Web button with the text "Submit".

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I add ARIA semantics to a web button for screen reader compatibility?▼

To add ARIA semantics to a web button, apply semantic HTML attributes and ARIA roles to ensure screen reader compatibility. This generates accessible UI components compliant with WCAG 2.2 standards, enhancing navigation for users with disabilities.

Can I generate WCAG 2.2 compliant accessibility traits for native iOS and Android platforms?▼

Yes, you can generate WCAG 2.2 compliant accessibility traits for native iOS and Android platforms. The process creates semantic ARIA attributes and properties specifically targeting native mobile environments to enhance digital accessibility.

What is the best way to ensure my dynamic web content meets WCAG 2.2 POUR principles?▼

The best way to ensure dynamic web content meets WCAG 2.2 POUR principles is by implementing technical standards for Perceivable, Operable, Understandable, and Robust interfaces. This generates semantic ARIA attributes for dynamic content accessibility.

Do I need semantic HTML to implement ARIA patterns for keyboard navigation?▼

You need semantic HTML to effectively implement ARIA patterns for keyboard navigation, as it provides the foundational structure for accessibility traits. This combination ensures digital products are operable and compliant with WCAG 2.2 standards.

When should I use ARIA properties instead of native HTML elements for UI accessibility?▼

Use ARIA properties instead of native HTML elements for UI accessibility when standard elements cannot convey dynamic content changes or complex interactions. This generates necessary semantic attributes ensuring robust accessibility compliance under WCAG 2.2 guidelines.

Why does my web interface fail WCAG 2.2 perceivable requirements for users with disabilities?▼

A web interface fails WCAG 2.2 perceivable requirements when it lacks semantic ARIA attributes and proper accessibility traits. Generating these properties ensures digital products present information in ways all users, including those with disabilities, can perceive.