TheGoat395/Codex-Skills / skills/react-accessible-components
react-accessible-components
VerifiedImplement semantic names, keyboard and focus.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1007 B |
| agents/openai.yaml | config | 290 B |
| references/react-accessible-components-guide.md | markdown | 3.1 KB |
references/react-accessible-components-guide.md
View on GitHub# React Accessible Components Guide
## Purpose
Make polished UI actually usable by keyboard, screen reader, and reduced-motion users.
## Use When
- A visible React component is interactive.
- The UI includes menus, modals, accordions, tabs, forms, icon buttons, carousels, cards, or navigation.
- A premium site needs accessible focus, hover, active, disabled, loading, and error states.
## Do Not Use When
- The task is pure content editing with no UI behavior.
- Existing semantics and behavior are correct and the task does not change or review them. Existing primitives do not exclude a requested accessibility repair.
- The project is non-React and another accessibility skill applies better.
## Discovery Questions
- Is the element a button, link, input, heading, list, landmark, or disclosure semantically?
- How does the component work with keyboard only?
- What is the accessible name and state?
- Where should focus move when opening, closing, submitting, or navigating?
## Decision Tree
- Start with semantic HTML before ARIA.
- If a component is complex, prefer Radix/shadcn-style primitives where already available.
- If building custom behavior, define keyboard support before animation polish.
- If using icons only, add accessible labels and tooltips where helpful.
- If motion changes focus or visibility, respect reduced-motion preferences.
## Implementation Rules
- Use `<button>` for actions and `<a>`/`Link` for navigation.
- Never remove visible focus without replacing it with a clear custom focus style.
- Make disabled/loading states programmatically and visually clear.
- Labels, errors, descriptions, and required state must connect to fields.
- Do not use ARIA to disguise non-semantic div soup.
## Useful Patterns
- Icon button: visible icon, `aria-label`, stable square size, focus ring, disabled state.
- Modal dialog: focus containment, Escape, labelled title, intentional close behavior, restore focus and scroll lock. Nonmodal dialogs/popovers preserve ordinary focus navigation.
- Tabs: roving focus or library primitive, selected state, panel association.
## Anti-Patterns
- Clickable divs.
- Hover-only content needed for comprehension.
- Focus rings hidden because they look less sleek.
- Menus that animate beautifully but cannot be operated with keyboard.
## QA Checklist
- Tab through the changed UI.
- Test Enter/Escape/Space/Arrow behavior where relevant.
- Check accessible names for icon buttons and fields.
- Run available accessibility lint/audit tools when present.
## Acceptance Criteria
- The component works without a mouse.
- Semantics match behavior.
- Accessibility states look designed, not bolted on.
## Shared scope
For applicable substantial web work, reuse the [shared scoped web contract](../../website-operating-rules/references/scoped-web-contract.md) when available. Preserve current authorization, stack and requested scope; this optional reference does not require another planning or approval cycle.
## Official Source Anchors
- React Learn: https://react.dev/learn
- React reference: https://react.dev/reference/react
- Next.js docs overview: https://nextjs.org/docs
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |