Skip to content

Search documentation

Search guides, examples, and component APIs.

Quick links
↑↓ NavigateEnter OpenEsc Close
Get started

Documentation navigation

Accessibility

Accessibility is part of the component contract. Weini uses native elements, relationship IDs, keyboard interaction, and predictable focus restoration. Application labels, validation messages, and theme choices remain your responsibility.

Labels and forms

Give every control a visible label. Use for and id for native inputs and supply an accessible name for icon-only actions. Named controls inside Form read provider initial values and connect validation errors through aria-describedby and aria-invalid. See forms and localization.

Keyboard and focus

Keep the complete public compound composition when using Select, Dialog, Tabs, and menus. Their foundation owns keyboard navigation and ARIA relationships. Dialog opening chooses an explicit initial-focus target or the first available control; closing normally returns focus to its trigger. Preserve Escape dismissal and native links.

Pointer targets and motion

The effective responding control must contain at least a 24 × 24 CSS px square unless a documented WCAG exception applies. Compact icon actions target 32 × 32 px and touch-oriented controls aim for 44 × 44 px. See design foundations. Respect reduced-motion preferences, preserve visible focus states, and check both light and dark themes after changing tokens.

Positioning and application state

Anchored popups use fixed positioning within their component subtree. Avoid clipping or transformed ancestors that establish a different containing block. Modal surfaces use the native dialog top layer. Consumer-controlled selection stays parent-owned; reconcile removed asynchronous options explicitly. invalid alone does not block native form submission.

Testing boundaries

Automated tests exercise models, keyboard behavior, semantics, SSR, and browser geometry. They do not certify screen-reader output, WCAG conformance, Safari, or touch devices. Test your application with NVDA, VoiceOver, actual mobile devices, forced colors, and 200%/400% zoom. Consumer theme overrides can reduce contrast, so verify the resulting colors.