accessibility

Audit UI components for WCAG 2.2 AA compliance and generate semantic ARIA roles, traits, and Android semantics.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/betaTrident/manta --skill accessibility-betatrident
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/betaTrident/manta/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/betaTrident/manta --skill accessibility-betatrident

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of meeting global accessibility standards, ensuring digital products are inclusive and usable for individuals relying on assistive technologies.

Core Features & Use Cases

  • Compliance Auditing: Evaluate UI components against WCAG 2.2 Level AA success criteria.
  • Semantic Implementation: Generate correct ARIA roles, iOS accessibility traits, and Android semantics.
  • Use Case: When building a new navigation menu, use this skill to ensure the component is keyboard-navigable, has proper focus management, and provides descriptive labels for screen readers.

Quick Start

Use the accessibility skill to audit the current component design for WCAG 2.2 compliance and generate the necessary semantic attributes.

Frequently Asked Questions about accessibility

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

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

You audit UI components for WCAG 2.2 Level AA compliance by evaluating them against established success criteria to ensure proper semantic markup and assistive technology support. This process verifies that interfaces meet global accessibility standards and remain inclusive for users relying on assistive technologies.

How do I implement correct ARIA roles and semantics for screen readers?

You implement correct ARIA roles for screen readers by generating semantic attributes that provide descriptive labels and proper focus management. This ensures UI components are keyboard-navigable and screen reader users receive accurate content descriptions across their platforms.

Does this accessibility audit approach work with iOS and Android development workflows?

Yes, this accessibility audit approach works with iOS and Android development workflows. It applies inclusive design practices across web, iOS, and Android platforms by generating platform-specific traits and semantics to satisfy technical requirements for assistive technologies.

What's the best way to ensure keyboard-navigable menus and proper focus management?

The best way to ensure keyboard-navigable menus and proper focus management is to apply semantic markup with correct ARIA roles during component construction. This technique guarantees that interactive elements receive descriptive labels and are fully accessible via keyboard input.

When do I need to apply iOS accessibility traits and Android semantics?

You need to apply iOS accessibility traits and Android semantics when building digital interfaces that must meet WCAG 2.2 Level AA standards. This ensures mobile components provide accurate content descriptions and proper support for assistive technologies.