Accessibility Guidelines

Purpose: Ensure components are accessible by default. Audience: Developer, Product Prerequisites: Familiar with shadcn/ui and Radix primitives.

Radix usage

• Prefer Radix components (@radix-ui/*) which include ARIA attrs and keyboard support.
• Example primitives used throughout (e.g., Dialog, Tabs, Tooltip).

Focus management

• Ensure focus visible states and return focus on modal close.
• Use aria-* labels for icon-only buttons.

Keyboard

• Tab order follows DOM; avoid tabindex>0.
• Provide keyboard shortcuts only as enhancements.

Color and contrast

• Tailwind tokens from shadcn ensure contrast in light/dark.
• Validate with system tools when customizing palettes.

Forms

• Labels linked to inputs; use aria-invalid and aria-describedby for errors.

Next steps

• See docs/ui/style-guide.md for component patterns.
• Audit key flows (auth, listing create) for A11y issues.