Core expectations
The stable core includes these expectations for interactive components.
FG UI provides keyboard, focus, ARIA and display-mode behaviour designed to support accessible interfaces. Your application markup, content and testing still matter, so the kit treats accessibility as a shared responsibility rather than a marketing checkbox.
This page is built entirely with FG UI using the same components, layout primitives, icons and interactions available in the kit. No Bootstrap, Tailwind or external UI framework is required.
The stable core includes these expectations for interactive components.
Complex controls keep native or documented accessibility contracts.
role=combobox, list relationships and keyboard support.maxlength.Automated checks cover language/main/H1 structure, duplicate IDs, control names, menu and tab keyboard patterns, focus management and ARIA state.
Principal semantic colour pairs, reduced motion, forced colours, print behaviour and no-JavaScript fallback are part of release checks.
Supported widths, zoom-equivalent reflow, long/localised content, touch targets and mobile control sizing are checked.
Release validation includes real screen-reader testing, current desktop browsers, iPhone Safari, Android Chrome, operating-system high-contrast and reduced-motion review, high zoom and physical touch-device interaction.