Receber por email
← Voltar para o catálogo

frontend-accessibility

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 navi

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/frontend-accessibility/svg)](https://www.skillteca.com.br/skills/frontend-accessibility)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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 .tsx or .jsx files
  • 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](../../../agent-os/standards/frontend/accessibility.md)

Compartilhar X LinkedIn