component-qa

Run Storybook Test Runner with pnpm test-storybook against a running Storybook instance. It uses axe-core via axe-playwright to audit each rendered story for WCAG 2.1 AA violations like color contrast, missing aria-labels, and invalid ARIA attributes.

Use grep with the regex pattern for hex codes and pixel values against the component source directory. Any match outside comments or justified cases indicates a token violation that should be replaced with theme tokens.

Storybook Test Runner mounts each story in a headless Playwright browser, checking for runtime errors, console warnings, and play function interactions. With the a11y addon configured, it also runs axe-core accessibility audits on every rendered variant.

Yes, use the CI mode which builds a static Storybook and runs the test runner against it. If Storybook cannot run at all, fall back to building the package, running the token grep check, and validating the story file statically.

Skip QA if the component is not yet migrated, if you are debugging a runtime crash, or if you only need a code review of a feature diff. QA assumes the component exists and should already compile and render.