Ensure your web applications work with screen readers like VoiceOver, NVDA, and JAWS. This skill provides testing checklists, keyboard commands, and code patterns for accessible development.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「screen-reader-testing」を使用しています。 How do I test my form with NVDA?
期待される結果:
Use NVDA+F7 to open the elements list and navigate to form fields. Press F to jump between fields. Check that each input announces its label, required state, and any error messages. Use Tab to navigate and verify logical focus order.
「screen-reader-testing」を使用しています。 What is the VoiceOver rotor?
期待される結果:
The VoiceOver rotor (VO+U) is a navigation tool that lets you quickly jump to specific element types: headings, links, form controls, landmarks, and more. Use left/right arrows to change category, up/down arrows to navigate within the category.
セキュリティ監査
安全All 61 static findings are FALSE POSITIVES. The skill is a documentation/guide for screen reader accessibility testing. The scanner detected markdown formatting characters (backticks in code blocks, tildes in tables) and legitimate documentation URLs, misinterpreting them as security risks. No actual code execution, credential access, or malicious network activity exists.
品質スコア
作れるもの
Accessibility Audit
Conduct a comprehensive screen reader compatibility audit before launching a new web application.
Code Review for Accessibility
Review frontend code to ensure ARIA attributes and semantic HTML support screen reader users.
Learn Screen Reader Commands
Get quick reference guides for VoiceOver, NVDA, JAWS, and TalkBack keyboard navigation.
これらのプロンプトを試す
Help me test my web page with screen readers. What are the key things to check for VoiceOver on macOS?
Create a testing script for NVDA on Windows. What keyboard commands should I use to navigate forms and check for proper labeling?
I have a modal dialog that screen readers cannot access properly. Show me the correct ARIA implementation with focus management.
Explain how to use aria-live regions to announce dynamic content updates to screen reader users. Give code examples.
ベストプラクティス
- Test with actual screen readers, not just browser simulators
- Always test both browse mode and focus/forms mode
- Verify focus management when opening and closing modals
- Use semantic HTML before adding ARIA attributes
回避
- Relying solely on automated accessibility testing tools
- Using aria-label when visible text is available
- Setting tabindex values greater than 0
- Ignoring focus order in single-page applications