skills.rest
Aytsuu
AytsuuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Apply WCAG 2.2 Level AA standards with semantic ARIA and platform traits.

Updated May 28, 2026
Search Tags:#inclusive design#accessibility#ARIA#WCAG 2.2#digital compliance
One-click install
npx skills add https://github.com/Aytsuu/codemini --skill accessibility-aytsuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/Aytsuu/codemini/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/Aytsuu/codemini --skill accessibility-aytsuu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the need for designing, implementing, and auditing inclusive digital products that comply with WCAG 2.2 Level AA standards, ensuring a POUR experience for all users.

Core Features & Use Cases

  • Accessibility Implementation: Automates the application of WCAG 2.2 standards like Target Size and Focus Appearance.
  • Code Auditing: Identifies and resolves accessibility barriers in existing code.
  • Platform Support: Generates semantic ARIA for Web and accessibility traits for iOS/Android.
  • Use Case: A web developer can use this Skill to ensure their application is accessible to users with disabilities, improving the overall user experience.

Quick Start

Run the accessibility skill to generate ARIA roles for your web component and ensure compliance with WCAG 2.2 standards.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit existing code for WCAG 2.2 accessibility barriers?▼

Generating semantic ARIA roles for web components requires applying WCAG 2.2 Level AA standards to ensure an inclusive POUR experience. This process identifies accessibility barriers in your code and provides the appropriate semantic roles for web elements.

How do I implement WCAG 2.2 Level AA standards like Target Size and Focus Appearance?▼

Implementing WCAG 2.2 standards like Target Size and Focus Appearance is automated to enhance digital product accessibility. This applies the required Level AA criteria directly to your interfaces, resolving barriers and ensuring a POUR experience for all users.

Can I use this to generate accessibility traits for iOS and Android platforms?▼

Yes, you can generate accessibility traits for iOS and Android platforms. Alongside providing semantic ARIA for web applications, this capability ensures your digital products comply with WCAG 2.2 Level AA standards across multiple platforms.

Do I need prior knowledge of ARIA roles and WCAG 2.2 to use this?▼

Yes, you need knowledge of WCAG 2.2 and ARIA roles to effectively use this capability. It automates the application of accessibility standards and generates semantic code, but requires your understanding to properly implement the inclusive design recommendations.

What is the best way to ensure my web application provides a POUR experience for all users?▼

Ensuring a POUR experience for all users requires applying WCAG 2.2 Level AA standards to your digital products. By auditing code to identify barriers and generating semantic ARIA roles, you can resolve accessibility issues and achieve inclusive design compliance.

Related Skills

Explore More Software Engineering Skills→
ScarletFishScarletFish

frontend-design

Generate HTML, CSS, and JavaScript components with WCAG 2.2 AA accessibility.

Community
Advanced
mastepanoskimastepanoski
44

wcag-accessibility-audit

Identify and remediate WCAG 2.1/2.2 accessibility barriers across websites and apps.

Community
Advanced
pascallammerspascallammers
1

accessibility-wcag

Ensure web applications meet WCAG 2.1/2.2 accessibility standards.

Community
Intermediate
cvs-healthcvs-health
366

iOS SwiftUI Accessibility

Enforce WCAG 2.2 accessibility patterns in SwiftUI source code.

Official
Intermediate