VMware's Angular and Web Components system, tuned for data-dense enterprise and infrastructure tooling.
Why we like it
Clarity's neat idea was shipping one design language two ways: Angular-native components, and Clarity Core, a set of Lit-based web components that drop into React, Vue or plain JavaScript. Same look, same behavior, whatever your stack, built on a deliberately minimal foundation that avoided re-implementing what frameworks already do.
It backed that with a real accessibility trail for enterprise buyers, targeting WCAG 2.1 AA and publishing a formal VPAT so teams could verify the claim rather than take it on faith.
Where it fits
Clarity fits data-dense enterprise apps that need one component implementation across several frameworks, and it's a strong reference for the web-components-core approach.
The important thing to know: the Clarity Core repo was archived and marked no longer supported in February 2026, so we'd point to it as a case study to learn from rather than a system to start building on today.
Ideas to borrow
- 01.
Architecture
Build your core as framework-agnostic web components (here, Lit), so one implementation serves Angular, React and Vue through custom elements.
- 02.
Accessibility practice
Publish a VPAT so enterprise buyers can verify your accessibility claims independently, instead of trusting a badge.