Tailwind CSS ↔ Assistive Technologies: Unresolved Decision on Automated Contrast Validation

Goal

Ensure every Tailwind‑styled component meets WCAG 2.1 AA color contrast and focus visibility requirements while remaining maintainable across light and dark modes.

Current Constraints

Tailwind’s core utilities do not provide automated contrast checks; developers must use external tools or custom helpers. The focus-visible variant exists but must be applied manually to each interactive element. ARIA attributes are not part of the utility set, requiring manual markup. Dark mode support via the dark: variant can unintentionally lower contrast if the same palette is reused.

Unresolved Decision

The Tailwind roadmap discusses a potential contrast utility that would validate and enforce WCAG 2.1 AA ratios during the build process. The community has not yet agreed on the design, scope, or implementation strategy.

Questions

• What design trade‑offs should guide the implementation of a build‑time contrast utility that balances developer ergonomics with strict WCAG compliance?
• How can such a utility be integrated with the existing dark: variant to automatically adjust color pairs while preserving the developer’s chosen palette?