Automated summary
Adds iOS VoiceOver accessibility attributes to React Native screens and components, including contrast and reduce-transparency handling specific to a Liquid Glass UI.
Strengths
- Provides a precise mapping table from element type to accessibilityRole and label guidance (buttons, tabs, images, inputs, switches, headers)
- Addresses Liquid Glass pitfalls: text taller than 65px, explicit PlatformColor('labelColor'), shadows or heavier font weight to reach WCAG AA
- Includes a reduceTransparencyChanged listener with proper cleanup and a fallback when glass is unsupported
- Covers element grouping, reading order and hiding decorative elements with accessible={false}
Limitations
- iPhone VoiceOver only: no Android TalkBack and no web ARIA
- Assumes a React Native project using @callstack/liquid-glass and its APIs
- No automated contrast checks or screen-reader tests, so results need manual verification
Use it when a React Native iOS screen or component must be readable by VoiceOver, especially on a Liquid Glass interface.
Avoid it for Android, web or Flutter apps, or when the need is automated accessibility testing rather than manually annotating components.
Security analysis
SafeThe skill is purely instructional content for editing React Native accessibility attributes: it gives code snippets for accessibilityRole/Label, reduce-transparency handling, and grouping. There is no file deletion, network access, credential handling, obfuscation, or safety-disabling behaviour, and no shell command is ever invoked. The only note is that Bash is granted without any use case, which slightly widens the agent's capability beyond what the workflow needs; Write/Edit are appropriate for the stated modifications.
- •`Bash` is declared in allowed-tools but never referenced in the instructions — unnecessary scope for a pure code-editing task
- •No verification/test command is specified, leaving the Bash grant unused and unguided
Examples
アプリ全体のアクセシビリティ対応をして。主要画面がVoiceOverで正しく読み上げられるようにラベルとロールを追加して設定画面のVoiceOver対応をお願い。アイコンボタンとトグルにラベルが足りていないので直してLiquid Glassのガラス上のテキストのコントラストを改善して、「透明度を下げる」設定がオンのときのフォールバックも入れてname: accessibility description: iPhoneのVoiceOver対応を中心にアクセシビリティを改善する。「アクセシビリティ対応して」「VoiceOver対応」「a11y改善」などのリクエストで使用する。 allowed-tools: Read, Write, Edit, Glob, Grep, Bash argument-hint: [対象画面名 or 省略で全画面]
アクセシビリティ改善スキル
iPhoneの VoiceOver を中心に、アクセシビリティ対応を実装する。
デザイン前提: Liquid Glass
本プロジェクトは @callstack/liquid-glass による Liquid Glass デザインを前提とする。
Liquid Glass はアクセシビリティ上の注意点が多い:
ガラス上テキストのコントラスト確保
- ガラスの背景ブラーにより、テキストの可読性が低下しやすい
LiquidGlassViewの高さが 65px超 の場合、テキスト色の自動適応が効かない。PlatformColor('labelColor')を明示的に使用する- WCAG AA 基準(コントラスト比 4.5:1 以上)を満たすよう、必要に応じてテキストに影 (
textShadowColor) やフォントウェイトの増加で補完する
「透明度を下げる」設定への対応
import { AccessibilityInfo } from 'react-native';
import { isLiquidGlassSupported } from '@callstack/liquid-glass';
const [reduceTransparency, setReduceTransparency] = useState(false);
useEffect(() => {
AccessibilityInfo.isReduceTransparencyEnabled().then(setReduceTransparency);
const sub = AccessibilityInfo.addEventListener(
'reduceTransparencyChanged',
setReduceTransparency,
);
return () => sub.remove();
}, []);
// reduceTransparency が true の場合、ガラスエフェクトを無効化し不透明背景にする
フォールバック
isLiquidGlassSupported === falseまたはreduceTransparency === trueの場合は、ガラスを使わず十分なコントラストを持つ不透明背景を提供する
対象ファイル
src/screens/**/*.tsx— 画面コンポーネントsrc/components/**/*.tsx— UIコンポーネント
引数が指定された場合はその画面のみ、省略時は全ファイルを対象とする。
手順
1. 対象要素の特定
以下の要素を検索し、アクセシビリティ属性の有無を確認する:
Pressable,TouchableOpacity,TouchableHighlight— ボタン系Image— 画像TextInput— 入力フィールドSwitch— トグルText(見出し相当) — ヘッダー
2. アクセシビリティ属性の適用ルール
ボタン / Pressable
<Pressable
accessibilityRole="button"
accessibilityLabel="戻る" // VoiceOverが読み上げるテキスト
accessibilityHint="前の画面に戻ります" // 操作の結果を説明(任意)
onPress={handleBack}
>
<ChevronIcon />
</Pressable>
| 要素の種類 | accessibilityRole | accessibilityLabel の指針 |
|-----------|-------------------|--------------------------|
| 通常ボタン | button | アクションを示す動詞(「保存する」「送信する」) |
| リンクボタン | link | 遷移先を示す(「設定を開く」) |
| 戻るボタン | button | 「戻る」 |
| アイコンボタン | button | アイコンの意味(「設定」「メニュー」) |
| いいねボタン | button | 状態を含む(「いいね、現在5件」) |
| タブバー項目 | tab | タブ名(「ホーム」「通知」「設定」) |
| 画像 | image | 画像の内容を説明する簡潔なテキスト |
| 装飾的画像 | — | accessible={false} を設定 |
| 入力フィールド | — | accessibilityLabel でフィールド名 |
| トグル | switch | 設定名と現在の状態 |
| 見出しテキスト | header | — (Text内容が自動で読まれる) |
画像
// 意味のある画像
<Image
source={{ uri: postImageUrl }}
accessibilityRole="image"
accessibilityLabel="投稿画像: カフェの外観写真"
/>
// 装飾的な画像(VoiceOverでスキップ)
<Image
source={decorativeBlob}
accessible={false}
/>
TextInput
<TextInput
accessibilityLabel="メールアドレス"
accessibilityHint="ログイン用のメールアドレスを入力してください"
placeholder="example@mail.com"
/>
見出し
<Text
accessibilityRole="header"
style={styles.sectionTitle}
>
基本情報
</Text>
状態を持つ要素
// いいねボタンの例
<Pressable
accessibilityRole="button"
accessibilityLabel={`いいね、現在${likesCount}件`}
accessibilityState={{ selected: isLiked }}
onPress={handleLike}
>
3. グループ化
関連する要素をまとめて1つの VoiceOver 項目にする:
// カードをグループ化
<View
accessible={true}
accessibilityRole="button"
accessibilityLabel={`${hirobaTitle}、メンバー${memberCount}人、投稿${postCount}件`}
>
<Text>{hirobaTitle}</Text>
<Text>{memberCount}人</Text>
<Text>{postCount}件</Text>
</View>
4. 読み上げ順序
重要な情報が先に読まれるよう、必要に応じて accessibilityElementsHidden や importantForAccessibility を使用:
// 装飾要素をVoiceOverから除外
<View accessibilityElementsHidden={true}>
<DecorativeBackground />
</View>
5. 絵文字アイコンの対応
絵文字をアイコンとして使用している箇所に accessibilityLabel を追加:
// Before
<Text>🏠</Text>
// After
<Text accessible={false}>🏠</Text>
// 親要素に accessibilityLabel を設定
ルール
accessibilityLabelは簡潔に、スクリーンリーダーで自然に聞こえる日本語にする- 装飾的な要素(背景画像、区切り線等)は
accessible={false}で除外する - 動的な値(カウント、状態)を含むラベルは変数で構築する
accessibilityHintは必須ではない。操作結果が自明でない場合のみ追加する- 既存の
accessibilityRole="button"は維持し、accessibilityLabelが未設定の場合のみ追加する - テスト: 変更後「VoiceOverで全画面を操作できるか」を基準とする
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/iphone-accessibility-improvement-mmlj2od2/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/iphone-accessibility-improvement-mmlj2od2' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/iphone-accessibility-improvement-mmlj2od2/download' --output '.skill-downloads/iphone-accessibility-improvement-mmlj2od2/SKILL.md.part' && mv '.skill-downloads/iphone-accessibility-improvement-mmlj2od2/SKILL.md.part' '.skill-downloads/iphone-accessibility-improvement-mmlj2od2/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Edit, Glob, Grep, Bash
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/iphone-accessibility-improvement-mmlj2od2/SKILL.md' && test -s '.skill-downloads/iphone-accessibility-improvement-mmlj2od2/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/accessibility' && cp -R '.skill-downloads/iphone-accessibility-improvement-mmlj2od2' '.claude/skills/accessibility'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/iphone-accessibility-improvement-mmlj2od2'openskills read 'iphone-accessibility-improvement-mmlj2od2'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/iphone-accessibility-improvement-mmlj2od2/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.