With #WVUI and it's Storybook test site, there was an accessibility addon available that uses [[ https://www.deque.com/axe/ | axe ]] to provide accessibility testing for each story. [[ https://storybook.js.org/addons/@storybook/addon-a11y | See their docs ]] for details.
As we've moved away from Storybook in #Codex per T290912, we should prioritize replacing this critical functionality, whether it's building something similar for our demos in VitePress, or integrating an automated testing workflow into our processes elsewhere.
**Requirements**
The outcome of this spike should be a decision on how to move forward with automation, to be followed by an implementation task.
**Acceptance Criteria:**
- Audit of existing components for accessibility using out-of-the-box tool
- For each component's audit, create individual tasks that need addressing
- Modifying acceptance criteria for future components