Screen readers help people who are blind or have low vision use websites. VoiceOver, NVDA, and JAWS are the most common screen readers. Testing with them makes sure your site works for everyone.
This guide shows you how to test web apps step by step. You will learn to check headings, forms, buttons, and dynamic content. You will also find common problems and how to fix them.
Accessibility testing is important for legal reasons and because it helps all users. Using screen readers during development catches issues early. Your website will be more usable and inclusive.
Global
mkdir -p ~/.claude/skills/screen-reader-testingProject
mkdir -p .claude/skills/screen-reader-testingSource Repository
Accessibilityaddyosmani/web-quality-skills
Audit and improve web accessibility following WCAG 2.2 guidelines for inclusivity
Fixing Accessibilityibelick/ui-skills
Audit and fix HTML accessibility issues for a more inclusive web
Accessibility Compliancewshobson/agents
Build inclusive interfaces that everyone can use with ease and confidence
Wcag Audit Patternswshobson/agents
Audit websites for WCAG 2.2 compliance and fix accessibility violations
Next Intl Add Languagegithub/awesome-copilot
Easily add a new language to your Next.js internationalized app
Vscode Ext Localizationgithub/awesome-copilot
Localize VS Code extensions correctly for all languages using official best practices
Flutter Improving Accessibilityflutter/skills
Make your Flutter app usable for everyone with accessibility features
Accessibilityaffaan-m/everything-claude-code
Make your websites and apps accessible to all with WCAG 2.2 standards