Themes
Accessibility
Preserve semantics, labels, focus, and keyboard interactions when composing controls.
Accessible components help provide expected semantics and interaction, but cannot infer an application’s meaning. Give controls accessible names, associate descriptions and errors, preserve heading order, and ensure focus remains visible. For dialogs and menus, verify keyboard entry/exit, focus movement, dismissal, and portal layering in the actual composed page.
Do not replace a native control’s semantics with visual styling alone. Model validation in application state, then project it to native validity and ARIA state with the app’s projectConstraintValidity helper; see validation. Review interactive examples with keyboard and assistive technology.