Accessible Angular Components
NgNova UI docs explain the semantic contract behind each component, including keyboard paths, screen reader behavior, focus handling, and validation states.
Baseline expectations
Components preserve native semantics first, then add ARIA only where the pattern needs it.
Keyboard activation with a consistent two-pixel blue focus-visible ring Associated labels, helper text, and errors Documented focus handling for overlays
Translated built-in labels
From 1.1.0, every component with built-in text exports a typed labels provider, so accessible names and status messages can be translated once per application.
Call provideUiModalLabels({ close: 'Fermer' }) and similar providers in bootstrapApplication Providers merge partial overrides and can be scoped to a route or component An explicit input on an instance still wins over provided labels Counts, ranges, step positions, and file sizes are label functions, so translations control word order