epic-ui-guidelines

To build accessible React components with Tailwind CSS and Radix UI, use semantic HTML, proper ARIA attributes, and keyboard navigation patterns. This ensures consistent styling and accessible interactions across forms, dialogs, and navigation.

Managing focus and color contrast in React dialogs involves applying accessible ARIA attributes and responsive layout patterns. Using Radix UI helps enforce correct focus management and semantic structure for modal interactions.

Yes, you can use these UI patterns for forms and dashboards in any React project. The guidelines apply across component libraries, pages, and layouts, ensuring your components adhere to established UI conventions.

Yes, Epic UI design requires a frontmatter-defined skill entry with specific name and description fields. This structural requirement ensures the UI guidelines are properly documented and applied across the development workflow.

Keyboard accessibility matters when building navigation components because it ensures users can navigate without a mouse. Implementing semantic HTML and ARIA attributes provides the necessary structure for screen readers and keyboard focus management.

You need ARIA attributes for accessible UI components whenever native semantic HTML does not convey the necessary interaction or state. They are essential for ensuring screen readers properly interpret forms, dialogs, and dynamic navigation patterns.