smukh Accessible component review
Review every supported state and input path of one reusable component.
Workflow
- Inventory states, variants, input methods, content slots, and expected semantics.
- Select the native element that already provides the behavior. Use ARIA patterns only when native HTML cannot provide the required interaction.
- Apply references/component-checklist.md to each state.
- Run deterministic rules, keyboard behavior, forced-colors, reduced-motion, zoom/reflow, and pointer target checks. Record manual judgment separately.
- Trace failures to the component source and repair the smallest shared layer that owns the defect.
- Add tests for user-visible behavior and verify consuming examples do not regress.
Boundaries
Do not add ARIA that duplicates or conflicts with native semantics. Do not treat a single Storybook example as coverage of every consumer. Do not assert that an accessible name is meaningful without content context.