Accessible components do not replace application decisions. Core wires control semantics and documented focus behavior; your application supplies meaningful text, state and the outcome of an action. This is an integration guide, not a claim of complete WCAG certification.
Visit the field using Tab. Its label supplies the name and hint supplies guidance. Activate Create project without a valid name to see errorMessage; Core associates that error with the input. Type a valid name and activate the icon button to hear the result region.
The icon-only Button uses ariaLabel. It keeps native keyboard activation; the application supplies the result in aria-live. The add icon is Button’s minimal fallback, not a general icon catalog.
Open the example with the keyboard, move through its controls and close it. Core contains focus while open and restores it when restoreFocus permits. Your application supplies title and decides how to handle closeRequested. Rejecting the proposal must leave the dialog and its focus usable.
Test meaningful names, Tab order, visible focus and the announced result in your application. Repeat in your actual theme and with browser zoom. Component API pages specify keyboard details; do not assume every control has the same arrow-key contract.
