Building websites that everyone can use is important. This skill shows you how to make forms and interactive parts work with screen readers and keyboard navigation. It covers semantic HTML, correct ARIA attributes, and proper focus management.
You will learn how to connect labels to inputs, mark required fields, and link error messages. These patterns help people who rely on assistive technology. They also make your code cleaner and more reliable.
Whether you are building a simple form or a complex modal, these tips help you avoid common accessibility mistakes. Use them during development or in code review to catch issues early.
Global
mkdir -p ~/.claude/skills/frontend-a11yProject
mkdir -p .claude/skills/frontend-a11ySource 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
Screen Reader Testingwshobson/agents
Test websites with screen readers for full accessibility and user inclusion