Challenge: Accessible, Themeable Component Library
Build a small “component library slice” that is accessible by default, themeable via design tokens, language-aware via i18n messages, and flexible via a headless dropdown API.
We'll cover the following...
Problem statement
Teams often ship UI components that look correct in one screen but fail when requirements change: a new theme, a new language, RTL layout, or a different visual treatment. The root issue is usually the same: logic, semantics, ...