// the find
angular/components
Component infrastructure and Material Design components for Angular
The official Angular Material library — Google-maintained UI components implementing Material Design 3 for Angular applications. It ships three distinct packages: `@angular/cdk` (headless primitives), `@angular/material` (opinionated Material components), and the new `@angular/aria` (WAI-ARIA pattern implementations). If you're building an Angular app and want a cohesive component set that tracks the framework itself, this is the default answer.
The CDK is the real gem here — overlay, virtual scroll, drag-and-drop, focus trap, and accessibility utilities are all production-grade and usable independent of Material Design. Accessibility is treated as a first-class requirement rather than an afterthought, with explicit screen reader testing across NVDA, JAWS, VoiceOver, and TalkBack. The new `@angular/aria` package for headless accessible directives is a meaningful addition — it separates WAI-ARIA behavior from visual opinions, which is exactly what teams building custom design systems need. Release cadence is tied directly to Angular's LTS schedule, so you don't have to play version roulette.
Material Design 3 theming via CSS custom properties is still awkward in practice — the token-based system requires understanding a deep SCSS/CSS variable hierarchy that's not well-explained for non-trivial customization. The component set has visible gaps: no date-range picker worth using in production, no rich text editor, no data grid with real feature parity against something like AG Grid. The Bazel build system makes contributing non-trivial; the dev environment setup for contributors is significantly heavier than a typical OSS project. And if your design system isn't Material Design, you'll spend a lot of effort overriding opinions rather than building on primitives — the CDK is the right layer for that, but the docs and examples consistently push people toward the Material layer first.