Habilidades wcag-audit-patterns
📦

wcag-audit-patterns

Seguro

Audit websites for WCAG 2.2 accessibility compliance

Também disponível em: wshobson

Manual accessibility audits are slow and error-prone without structured guidance. This skill provides systematic WCAG 2.2 checklists, automated testing integration, and proven remediation patterns.

Suporta: Claude Codex Code(CC)
🥉 74 Bronze
1

Baixar o ZIP da skill

2

Upload no Claude

Vá em Configurações → Capacidades → Skills → Upload skill

3

Ative e comece a usar

Testar

A utilizar "wcag-audit-patterns". Audit my navigation menu for accessibility issues

Resultado esperado:

Found 4 WCAG violations: Missing skip link (2.4.1 A), keyboard trap in dropdown (2.1.2 A), missing aria-expanded state (4.1.2 A), and insufficient focus indicator contrast (2.4.7 AA). Fixed navigation code includes skip link, proper focus trapping, ARIA states, and 3px solid focus outline with 4.5:1 contrast.

A utilizar "wcag-audit-patterns". Fix color contrast errors on my login form

Resultado esperado:

Original gray text (#888888) has 2.8:1 contrast on white background. Updated to #595959 for 4.5:1 AA compliance. Error state now uses red (#D32F2F) with icon and text message, not color alone. Focus indicator changed to 3px blue outline visible at 4.6:1 contrast ratio.

Auditoria de Segurança

Seguro
v1 • 2/25/2026

Static analyzer flagged 76 patterns but all are false positives. The skill contains Markdown documentation with code examples, not executable code. Detected backticks are markdown fences, URLs are reference links, and no actual shell execution, network calls, or credential access exists.

2
Arquivos analisados
586
Linhas analisadas
0
achados
1
Total de auditorias
Nenhum problema de segurança encontrado
Auditado por: claude

Pontuação de qualidade

38
Arquitetura
100
Manutenibilidade
87
Conteúdo
50
Comunidade
100
Segurança
91
Conformidade com especificações

O Que Você Pode Construir

E-commerce Accessibility Audit

Audit an online store for WCAG 2.2 AA compliance before a product launch. Run automated scans on key pages, perform manual keyboard testing on checkout flow, and fix critical barriers like missing form labels and keyboard traps.

Government Website Compliance

Review a public sector website for Section 508 and ADA compliance. Document all violations, prioritize by user impact, and provide remediation code that meets federal accessibility standards.

Accessibility Lawsuit Remediation

Respond to an accessibility demand letter by auditing the cited pages, identifying all WCAG violations, and implementing fixes with documented evidence for legal defense.

Tente Estes Prompts

Quick Accessibility Scan 
Audit the homepage of my website for WCAG 2.2 Level A violations. List all issues found, explain why each violates WCAG, and provide fixed code examples for each problem.
Component Accessibility Review 
Review my custom dropdown menu component for accessibility issues. Check keyboard navigation, focus management, ARIA attributes, and screen reader compatibility. Provide corrected code that passes WCAG 2.2 AA.
Full Site WCAG 2.2 AA Audit 
Conduct a complete WCAG 2.2 AA audit of my e-commerce site. Include automated testing setup with axe-core, manual testing checklist for keyboard and screen reader flows, and a prioritized remediation plan with code fixes for all violations.
Color Contrast and Visual Accessibility 
Analyze my design system colors for WCAG 2.2 contrast compliance. Test all text-background combinations at normal and large sizes, check UI component contrast ratios, and suggest accessible color alternatives that maintain brand identity.

Melhores Práticas

  • Start accessibility testing during design phase, not after development
  • Use semantic HTML elements before adding ARIA attributes
  • Test with keyboard only and at least one screen reader before publishing

Evitar

  • Relying only on automated testing tools without manual verification
  • Hiding focus outlines for visual design preferences
  • Using color as the only indicator for errors or required fields

Perguntas Frequentes

What WCAG level should my website meet?
Most regulations require WCAG 2.2 Level AA including ADA lawsuits, Section 508, and EU accessibility laws. Level AAA is recommended for specialized audiences but AA is the legal baseline for most organizations.
Can automated tools catch all accessibility issues?
No. Automated tools detect only 30-50 percent of accessibility issues. Manual testing for keyboard navigation, focus order, screen reader flows, and cognitive accessibility requires human evaluation.
Do I need to make my entire website accessible or just key pages?
All public-facing pages should be accessible. Courts have rejected partial compliance arguments. Prioritize high-traffic pages and user journeys like checkout, but plan for site-wide remediation.
How often should I re-audit my website for accessibility?
Audit after each major release, when adding new components, and at least quarterly for active sites. Accessibility regressions commonly occur during routine updates and feature additions.
What is the difference between ARIA and semantic HTML?
Semantic HTML uses native elements like button, nav, and main that have built-in accessibility. ARIA adds accessibility metadata to custom elements. Always prefer semantic HTML first, use ARIA only when native elements cannot achieve the needed behavior.
Can I be sued for accessibility violations even if I am working on fixes?
Yes. Ongoing remediation is not a legal defense. However, documented good-faith efforts and a public accessibility statement can reduce damages. Prioritize critical barriers that block task completion.

Detalhes do Desenvolvedor

Autor

sickn33

Licença

MIT

Repositório

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/wcag-audit-patterns

Referência

main

Estrutura de arquivos

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md