baseline-ui

To enforce accessibility in Tailwind CSS, validate that components use accessible primitives like Radix or React Aria, require aria-labels on icon-only buttons, and ensure AlertDialog is used for destructive actions to prevent rebuilding focus and keyboard behavior by hand.

Common Tailwind CSS layout anti-patterns include using h-screen, arbitrary z-index values, and heavy backdrop-filters. To fix performance issues, replace these with size-* utilities for squares and enforce a safe-area alongside a fixed z-index scale.

Validate React and Tailwind animations by checking that durations and easing choices are limited, ensuring compositor-only properties are used, and verifying that reduced-motion preferences are respected to avoid janky or distracting motion.

Maintain typography scale and readability in Tailwind CSS by enforcing text-balance usage, applying tabular numbers for data displays, and forbidding arbitrary letter-spacing to preserve visual rhythm across UI components.

Yes, you can audit a design system update in a pull request by running a UI consistency check on React or Tailwind utility files to list exact violations, explain why each matters, and provide concrete code-level fixes.

Yes, checking Tailwind CSS UI constraints requires adhering to Tailwind CSS conventions, using motion/react for JavaScript animations, and applying the cn utility for class logic to properly evaluate accessibility and animation property rules.