accessibility-compliance-accessibility-audit
Audit Web Accessibility with WCAG
This skill helps developers conduct comprehensive WCAG compliance audits using automated tools and manual testing to identify accessibility barriers and provide remediation guidance.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「accessibility-compliance-accessibility-audit」を使用しています。 Run WCAG AA audit on example.com
期待される結果:
Accessibility Audit Results: Score 72/100. Critical Issues: 3 (missing alt text, form labels). Serious Issues: 5 (contrast, focus indicators). Recommended fixes with code examples provided.
「accessibility-compliance-accessibility-audit」を使用しています。 How do I fix keyboard trap in modal?
期待される結果:
To fix keyboard trap: 1) Add Escape key handler to close modal. 2) Ensure focus returns to trigger element. 3) Trap focus within modal while open. See code example with React and ARIA.
セキュリティ監査
安全Security review complete. All static findings are false positives. The skill provides legitimate accessibility testing examples using standard tools (axe-core, Puppeteer). No actual command injection, credential access, or malicious network requests present. Code examples are for local accessibility testing only.
品質スコア
作れるもの
Pre-release Accessibility Audit
Run comprehensive accessibility audit before launching a website to ensure WCAG AA compliance and identify barriers.
Remediation Guidance
Get step-by-step guidance on fixing specific accessibility violations with code examples.
Accessibility Education
Learn best practices for keyboard navigation, screen reader support, and inclusive design patterns.
これらのプロンプトを試す
Run a WCAG AA accessibility audit on my website at [URL]. Identify the top issues and provide remediation steps.
Test the login form component for accessibility. Check for proper labels, keyboard navigation, error handling, and screen reader announcements.
I have [specific accessibility issue]. Provide detailed code examples to fix this using React and ARIA attributes.
Create a GitHub Actions workflow to run automated accessibility tests on every pull request using axe-core.
ベストプラクティス
- Always test with real assistive technologies, not just automated tools
- Prioritize fixes by user impact (critical > serious > moderate > minor)
- Document accessibility decisions and rationale in code comments
- Include accessibility testing in your CI/CD pipeline
回避
- Relying solely on automated tools without manual testing
- Using color as the only means of conveying information
- Setting tabindex > 0 which disrupts logical tab order
- Adding ARIA attributes without understanding their meaning