skills.rest
redongreen
redongreenCOMMUNITY
Explore all skills by this author →
GitHub

create-voice

Generate screen reader accessibility specs for VoiceOver, TalkBack, and ARIA.

236|32|Updated Jan 23, 2026
Search Tags:#accessibility#screen reader#figma#voiceover#aria#talkback
One-click install
npx skills add https://github.com/redongreen/uSpec --skill create-voice-redongreen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-voice
Source: https://github.com/redongreen/uSpec/tree/main/.cursor/skills/create-voice
Command: npx skills add https://github.com/redongreen/uSpec --skill create-voice-redongreen

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of screen reader accessibility specifications, ensuring your UI components are usable by everyone, regardless of their assistive technology needs.

Core Features & Use Cases

  • Platform-Specific Specs: Generates detailed accessibility information for VoiceOver (iOS), TalkBack (Android), and ARIA (Web).
  • Focus Order Mapping: Identifies and documents the correct tab order for interactive elements.
  • Announcement Patterns: Defines how screen readers should announce component states and properties.
  • Use Case: When designing a new button component, use this Skill to generate a comprehensive accessibility spec that details how screen readers will announce its label, state (e.g., disabled), and any associated actions.

Quick Start

Use the create-voice skill to generate a screen reader accessibility specification for the provided Figma component link.

Frequently Asked Questions about create-voice

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

FAQPage Schema
How do I generate screen reader accessibility specs from a Figma design?▼

To generate screen reader accessibility specs, provide a Figma link or screenshot along with an optional component description to automatically document focus order, platform-specific properties, and announcement patterns.

What is the best way to document VoiceOver and TalkBack focus order for UI components?▼

Documenting VoiceOver and TalkBack focus order requires mapping interactive elements to define the correct tab sequence and platform-specific announcement patterns organized by component state.

Can I create ARIA documentation for web components using a screenshot?▼

Yes, you can create ARIA documentation by providing a component screenshot and optional context, which allows the system to automate the generation of web accessibility properties and announcement behaviors.

Does this screen reader spec generator work for both iOS and Android platforms?▼

Yes, the screen reader spec generator works for both iOS and Android by producing detailed accessibility information specifically tailored for VoiceOver and TalkBack respectively, alongside web ARIA standards.

How are component states and properties announced by screen readers documented?▼

Component states and properties are documented by defining specific announcement patterns that dictate how screen readers should vocalize element labels, states like disabled, and associated actions.

Do I need a Figma link to generate an accessibility specification?▼

No, a Figma link is not strictly required; you can also provide a component screenshot and an optional component description to generate the screen reader accessibility specification.

Related Skills

Explore More Design & Creative Skills→
clawpod-appclawpod-app
46

design-critique

Identify usability and visual-design issues in Figma links, screenshots, or descriptions.

Community
Advanced
MinhAnh-CorpMinhAnh-Corp

accessibility-compliance

Implement WCAG 2.2 compliant interfaces and ARIA patterns for UI components.

Official
Intermediate
codesour-designcodesour-design

apply-design-system

Reconnects existing Figma designs to published design system components.

Community
Advanced
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate