accessible-html-jsx
Write clean, modern, and highly accessible HTML & JSX code, using semantically correct elements and attributes. Use when writing or reviewing HTML/JSX markup, creating forms, handling ARIA attributes, building interactive widgets, or implementing keyboard navigation.
- License 许可
- MIT
- 最近更新
- 2026-10-23
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- accessible-html-jsx
- description
- Write clean, modern, and highly accessible HTML & JSX code, using semantically correct elements and attributes. Use when writing or reviewing HTML/JSX markup, creating forms, handling ARIA attributes, building interactive widgets, or implementing keyboard navigation.
- user-invocable
- false
02 资源文件 1
- 参考文档REFERENCE.md4.4 KB
03 SKILL.md 正文
Accessible HTML & JSX
Accessibility is a baseline requirement, not an enhancement. Follow eslint-plugin-jsx-a11y-x recommended rules enforced in this repo (same rule set as upstream jsx-a11y, rule prefix jsx-a11y-x/).
Semantic HTML First
- PREFER semantic elements (
header,nav,main,section,article,aside,footer,fieldset,legend) over genericdiv/span - PREFER
<button>over<div role="button">— native elements provide focus, keyboard activation, and AT announcement for free - NEVER use
<a href="#">or<a href="javascript:void(0)">— use<button>for actions,<a href="/path">for navigation - Use correct heading hierarchy (
h1→h6) without skipping levels; headings must contain accessible text - Use
<ul>/<li>for lists and navigation menus (as theSidebarcomponent does)
ARIA Rules
- PREFER native HTML semantics over ARIA — ARIA is a supplement, not a replacement
- NEVER put
aria-hidden="true"on focusable elements — hides from AT but remains in tab order - ALWAYS use valid ARIA attributes (
aria-labelledbynotaria-labeledby), valid roles, and correct value types - NEVER add redundant roles (
<button role="button">) - NEVER use
tabIndex > 0— breaks natural tab order; only use0or-1 - Mark decorative icons with
aria-hidden={true}(e.g.,<HomeIcon aria-hidden />) - Use
aria-invalidon inputs with validation errors — this repo styles it viaaria-invalid:ring-destructive/20 aria-invalid:border-destructive - Use
aria-pressedfor toggle buttons,aria-expandedfor collapsible controls,aria-controlsto link triggers to controlled elements
Forms & Inputs
- ALWAYS associate
<Label>with form controls viahtmlFor— ESLint enforceslabel-has-associated-controlwith custom components:Label,FieldLabel,Input,PasswordInput(depth: 3) - PREFER specific input types (
email,url,tel,search,number) - Wrap related fields in
<FieldSet>with<FieldLegend>(fromsrc/components/ui/Field) - Use
<FieldError>withrole="alert"for validation errors — announces to screen readers immediately - On submit failure, focus the first invalid input using the
focusFirstErrorutility fromsrc/lib/utils/focusFirstError
Interactive Elements & Keyboard
- EVERY
onClickmust have a keyboard equivalent (onKeyDown/onKeyUp) — or just use<button>/Base UI components which handle this natively - EVERY
onMouseOver/onMouseOutmust pair withonFocus/onBlur - ALWAYS provide visible focus indicators — use
focus-visible:border-ring focus-visible:ring-3 focus-visible:ring-ring/50(project standard)
Images & Media
- ALWAYS provide meaningful
alttext — never include "image", "photo", or "picture" in alt (screen readers already announce the type) - Use
alt="" aria-hidden={true}for purely decorative images <video>/<audio>must have<track kind="captions">
Screen Reader Support
- Use
sr-onlyclass for visually hidden text that screen readers need (icon-only buttons, sidebar toggles, close buttons) - For loading states: keep original content in the accessibility tree via
sr-only, show spinner visually witharia-hidden
Advanced Patterns
See REFERENCE.md for live regions, focus management, keyboard navigation patterns, and widget-specific requirements.
04 同仓库更多 Skills
web-security
Enforce web security and avoid security vulnerabilities.
typescript
Write clean, efficient TypeScript code that follows project conventions and advanced type patterns. Use when writing or reviewing TypeScript code, defining types, creating generics, handling errors, or working with React components, Zod schemas, and TanStack libraries.
tanstack-router
TanStack Router patterns for this repo — file-based routing, auth guards, search params, data loading, TanStack Query integration, navigation, and code splitting. Use when creating routes, adding pages, implementing auth flows, working with search/path params, or integrating loaders with TanStack Query.
tanstack-query
TanStack Query patterns for this repo — queryOptions/mutationOptions factories, query key hierarchies, service layer integration, optimistic updates, Suspense usage, error handling, and TanStack Router data loading. Use when creating queries, mutations, API services, query keys, cache invalidation, optimistic updates, or integrating data fetching with routes.
tanstack-form
Build forms using TanStack Form with the project's useAppForm composition, composable field components, Zod validation schemas, FormFieldWrapper error tracking, and form.AppField vs form.Field patterns. Use when creating new forms, adding form fields, writing form validation, or working with TanStack Form in this project.
react
Build clean, modern React components that apply common best practices and avoid common pitfalls like unnecessary state management or useEffect usage.