Frontend Accessibility Best Practices
sergiodxa/agent-skills/skills/frontend-accessibility-best-practicesby sergiodxa40e21b46189dNo license90 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 months ago
Accessibility (a11y) best practices for React components. Use when creating UI components, forms, interactive elements, or reviewing code for accessibility compliance.
- 40e21b46189dCurrentcommit 40e21b4Published Oct 8, 2026
Source and attribution
Source:sergiodxa/agent-skillsinskills/frontend-accessibility-best-practicesat commit40e21b4
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from sergiodxa/agent-skills
Frontend React Best Practices
sergiodxa
React performance and composition guidelines covering bundle size, re-renders, rendering, hooks, and client patterns.
Frontend Testing Best Practices
sergiodxa
Guidelines for frontend testing that favor E2E tests, minimal mocking, and behavior-focused assertions.
Frontend Tailwind Best Practices
sergiodxa
Tailwind CSS styling conventions for frontend components, layouts, color schemes and responsive design.
More in Software Development
Playground
anthropics
Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.
M5 Onboard
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.
Cardputer Buddy
anthropics
Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.
Web Design Guidelines
vercel-labs
Reviews UI code against Web Interface Guidelines fetched from a remote source and reports findings as file:line entries.
Vercel React Native Skills
vercel-labs
React Native and Expo best-practice rules covering list performance, animation, navigation, UI patterns, state, and monorepo setup.
Vercel React Best Practices
vercel-labs
Vercel's React and Next.js performance guidelines, organized as 70 rules for writing, reviewing, and refactoring code.