Frontend accessibility
Skill bg-szy/TOP-SKILLS/skills/marketplace/frontend-accessibility
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能,提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill frontend-accessibilityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Implement accessible user interfaces with semantic HTML, keyboard navigation, sufficient color contrast, screen reader support, ARIA attributes, and proper focus management. Use this skill when creating or editing React components (.tsx, .jsx files), when implementing forms with labels and inputs, when building interactive elements (buttons, modals, menus, dialogs), when implementing keyboard navigation, when choosing colors and ensuring contrast ratios, when adding ARIA attributes, when testing with screen readers, when implementing focus states and focus management, or when creating heading structures and page landmarks.
SKILL.md
1.9 KB, as published. Nobody here has run it
Frontend Accessibility
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle frontend accessibility.
When to use this skill
- When creating or editing React components in
.tsxor.jsxfiles - When implementing semantic HTML elements (nav, main, button, article, section, etc.)
- When building forms and ensuring all inputs have associated labels
- When implementing keyboard navigation and focus management
- When adding interactive elements like buttons, links, modals, or menus
- When choosing colors and verifying contrast ratios meet WCAG standards (4.5:1 minimum)
- When adding alternative text to images or icons
- When implementing ARIA attributes for complex UI patterns
- When testing components with screen readers
- When creating logical heading hierarchies (h1-h6)
- When implementing visible focus indicators for keyboard navigation
- When managing focus in dynamic content, modals, or single-page applications
- When ensuring touch targets are appropriately sized for accessibility
Instructions
For details, refer to the information provided in this file: frontend accessibility