Accessibility
What is guaranteed, and what is not.
The API makes the accessible thing the default
IconButton requires aria-label at the type level, so an icon-only control cannot ship nameless. Alert and Toast pick role="alert" for urgent tones and role="status" for the rest, so they do not talk over the user. RadioGroup is a real <fieldset> with a <legend>, which names the group with no ARIA at all. Divider is a real <hr> unless labelled, and FAQ is native <details> — no ARIA, no JavaScript.
Overlays
Modal and Drawer trap focus, lock body scroll without layout shift, make the rest of the page inert, and return focus to the trigger. Combobox and CommandPalette move the active option with aria-activedescendant while DOM focus stays in the input, which is the pattern the ARIA spec actually prescribes.
How it is verified
Every component has automated axe assertions in its test suite, and the keyboard maps are covered by tests rather than described in prose.
Colour contrast is reasoned, not machine-verified. The axe contrast rule cannot run without a real browser, so every "axe clean" claim covers structure and ARIA but not contrast. A Playwright pass is on the roadmap.