Accessible by design. Tested in context.
staqui targets WCAG 2.2 AA. Its primitives provide a foundation; your content and application flows complete the experience.
Keyboard behavior
| Component | Interaction |
|---|---|
| Buttons and controls | Tab to focus; Enter or Space to activate according to native semantics. |
| Menus | Arrow keys, Home/End and typeahead; Escape closes and restores focus. |
| Modal | Focus stays in the dialog. Escape closes; the trigger regains focus. |
| Popover and tooltip | Escape dismisses. Tooltips appear immediately on keyboard focus. |
| Calendar | Arrow keys navigate dates; Page Up/Down changes months; Enter/Space selects. |
Labels and validation
Every field requires a label. hideLabel visually hides it while preserving the accessible name. Description and error text are connected by aria-describedby, and errors set aria-invalid. Keep required instructions visible outside tooltips.
Meaning beyond color
Use status words inside badges and banners. Loading actions expose aria-busy and prevent repeat activation. Choose meaningful link labels and alt text; decorative icons are hidden from assistive technologies.
Motion and target size
Reduced-motion preferences disable spinner rotation and transitions. Compact mode preserves visible focus and minimum target sizes. Check your application at 200% zoom, narrow widths and with long translated strings.
What validation can establish
The test suite runs structural axe checks on every catalog example and focused interaction tests for complex controls. Automated checks cannot certify WCAG compliance. Screen-reader output, high-contrast modes, touch behavior and custom brand overrides still require application-level testing.