Guide
Accessibility
Current accessibility practices and what to verify in product usage.
Native inputs
Inputs expose native attributes such as `id`, `name`, `autocomplete`, and `tabindex`. Use them consistently with labels and form context so screen readers and browser autofill can understand the field.
Keyboard and focus
Interactive components need visible focus, predictable tab order, disabled states, and keyboard behavior for enter, escape, arrows, and selection. Components that open overlays should also return users to a stable trigger state after close.
ARIA
The shared `INmorphA11yProps` shape includes role and aria label fields. Use explicit ARIA only when native semantics are not enough, and test components in the final page context.