Run storybook axe scans on CI builds

[kendallgassner]

We noticed in #5559 that our axe-scans do not run on every storybook story. This PR aims to fix that.

Closes #

Changelog

New

Changed

Removed

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 154e062

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks!

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	104.54 KB (0%)
packages/react/dist/browser.umd.js	104.88 KB (0%)

[joshblack]

Hi here, @kendallgassner! 👋

Just providing some context, storybook axe scans currently run through playwright (for example) instead of in Jest so that we can get contrast checks reported accurately. We still have some old test suites that use this technique but we can get rid of them (I think 😅)

If you're seeing a story not being checked against axe it'd be great to add them to the corresponding e2e test

[kendallgassner]

👀 Thanks @joshblack! Is there a reason we don't do this for every story?

[joshblack]

@kendallgassner I don't think so, definitely would make sense to run it on every story. It would be worth it to add a dedicated test for this so that each component e2e test doesn't have to add it explicitly which I think is likely the root cause if something is not being checked.

[kendallgassner]

@joshblack cool! I'll convert this PR to aim to do that

[kendallgassner]

I don't know how I feel about this but the details story feels like it's incorrectly erroring here.

[kendallgassner]

Closing for now while I play around with this locally.