accessibility

Audit UI code for WCAG 2.2 AA compliance and generate accessibility attributes.

2|Updated May 11, 2026
One-click install
npx skills add https://github.com/himanshu231204/AI_Research_agent --skill accessibility-himanshu231204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/himanshu231204/AI_Research_agent/tree/main/.opencode/skills/accessibility
Command: npx skills add https://github.com/himanshu231204/AI_Research_agent --skill accessibility-himanshu231204

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inaccessible digital products that exclude users with disabilities, create compliance risks with WCAG 2.2 Level AA standards, and deliver poor experiences for assistive technology users.

Core Features & Use Cases

  • Cross-Platform Accessibility Implementation: Generate semantic ARIA for web applications and accessibility traits for iOS and Android native apps.
  • Compliance Auditing: Identify WCAG 2.2 barrier gaps in existing UI code and get actionable fixes for issues like insufficient target size, poor focus management, and missing labels.
  • Use Case: A product team building a new e-commerce checkout flow can use this Skill to ensure all form fields, buttons, and navigation elements are accessible to screen reader and keyboard-only users, avoiding costly retrofits after launch.

Quick Start

Use the accessibility skill to audit the mobile app's onboarding flow for WCAG 2.2 AA compliance and generate the required accessibility labels and traits for all interactive elements.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit my UI components for WCAG 2.2 AA compliance?

To audit your UI for WCAG 2.2 AA compliance, review interactive elements for barrier gaps like insufficient target size, poor focus management, and missing labels, then apply semantic ARIA or native traits to resolve them.

How do I implement ARIA attributes and accessibility traits for cross-platform apps?

Implement cross-platform accessibility by mapping semantic ARIA attributes for web applications and configuring native accessibility traits for iOS and Android UI components to ensure assistive technology compatibility.

What is the best way to ensure assistive technology compatibility for a new checkout flow?

The best way to ensure assistive technology compatibility is to validate that all form fields, buttons, and navigation elements have proper ARIA labels, focus management, and semantic markup for screen reader and keyboard-only users.

Can I use this approach to map accessibility attributes across web, iOS, and Android?

Yes, you can map accessibility attributes across web, iOS, and Android by translating semantic ARIA implementation for web into native accessibility trait configurations for iOS and Android development workflows.

Why does my screen reader skip interactive elements during navigation?

Your screen reader skips interactive elements due to poor focus management and missing semantic labels, requiring actionable fixes like ARIA implementation and native accessibility trait configuration to restore navigation order.

When do I need to perform an accessibility barrier audit on my digital product?

You need an accessibility barrier audit when your digital product excludes users with disabilities, creating compliance risks with WCAG 2.2 Level AA standards and delivering poor experiences for assistive technology users.