Why is Base UI here?
Base UI is the unstyled behavior layer behind selected complex components. It does not define how QuackElements looks, how its tokens work, or how your generated source is organized.
Keyboard behavior
Focus movement and interaction patterns for complex controls.
Accessible semantics
A dependable foundation for screen readers and assistive technology.
State machinery
Open, closed, selected, and highlighted behavior that is easy to get wrong.
Base UI provides
- Accessible interaction primitives
- Focus and dismissal behavior
- Composable unstyled parts
QuackElements owns
- Visual language and theme tokens
- Generated component APIs
- CLI, registry, and source workflow
In short: Base UI helps the difficult interaction details remain dependable. The product design, component code, naming, tokens, and developer experience are QuackElements.