Habilidades screen-reader-testing
📖

screen-reader-testing

Seguro

Test Accessibility with Screen Readers

Também disponível em: wshobson

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.

Suporta: Claude Codex Code(CC)
🥉 75 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 "screen-reader-testing". How do I test my form with NVDA?

Resultado esperado:

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.

A utilizar "screen-reader-testing". What is the VoiceOver rotor?

Resultado esperado:

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.

Auditoria de Segurança

Seguro
v1 • 2/25/2026

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.

2
Arquivos analisados
581
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
85
Conteúdo
50
Comunidade
100
Segurança
100
Conformidade com especificações

O Que Você Pode Construir

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.

Tente Estes Prompts

Basic Screen Reader Test 
Help me test my web page with screen readers. What are the key things to check for VoiceOver on macOS?
NVDA Testing Guide 
Create a testing script for NVDA on Windows. What keyboard commands should I use to navigate forms and check for proper labeling?
Fix Accessibility Issues 
I have a modal dialog that screen readers cannot access properly. Show me the correct ARIA implementation with focus management.
Live Region Implementation 
Explain how to use aria-live regions to announce dynamic content updates to screen reader users. Give code examples.

Melhores Práticas

  • 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

Evitar

  • 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

Perguntas Frequentes

Which screen readers should I test with?
Minimum: NVDA+Firefox (Windows) and VoiceOver+Safari (macOS). Comprehensive: add JAWS+Chrome, TalkBack+Android, and Narrator+Edge.
What is the difference between Browse mode and Focus mode?
Browse mode uses arrow keys for content navigation. Focus mode uses arrow keys for widget control. NVDA auto-switches when entering forms or ARIA applications.
How do I test dynamic content updates?
Use aria-live regions. Set aria-live='polite' for non-critical updates, aria-live='assertive' for urgent alerts. Test that content changes are announced.
What is focus trapping and why does it matter?
Focus trapping keeps keyboard focus inside a modal or dialog until it closes. This prevents screen reader users from accidentally navigating behind the modal.
Can I test screen readers in CI/CD?
Automated tools like axe-core can catch many issues but cannot replace manual screen reader testing. Use CI for automated checks, manual testing for the full experience.
What is the VoiceOver modifier key?
The VoiceOver modifier (VO) is Ctrl+Option. All VoiceOver commands use this combination. For example, VO+Right Arrow moves to the next element.

Detalhes do Desenvolvedor

Autor

sickn33

Licença

MIT

Repositório

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/screen-reader-testing

Referência

main

Estrutura de arquivos

📁 resources/

📄 implementation-playbook.md

📄 SKILL.md