Storybook

React server component testing example for Next.js notes app: "note editor saves note and redirects after submitting note"

Full speed ahead on component testing for React Server Components!

✅ vitest-plugin-rsc canary now on npm
✅ vite RSC refactor for testing support
✅ @nextjs.org context providers
✅ Notes app demo with tests

👉 github.com/kasperpeulen...

homer-gaines-webinar-manual-vs-automated-a11y-testing

👀 Reminder: our webinar’s tomorrow

A11y testing isn’t either/or.
Automated checks catch the obvious. Manual testing catches the weird stuff.

Used together = fewer bugs in prod.

Join us + Homer Gaines, CPACC to break down a workflow that scales.

🎫 Save your spot: us02web.zoom.us/webinar/regi...

automated vs manual a11y testing webinar

Automated a11y tests = fast + scalable.
Manual a11y testing = real-world coverage.

Used together? You catch more bugs before they ship.

Join us + accessibility expert Homer Gaines to build a workflow that works.

🗓️ Tues, Aug 5 — 12PM EDT
🎟️ register here → us02web.zoom.us/webinar/regi...

Component Test with Storybook and Vitest Best-in-class Component Testing at your fingertips

Have you tried component testing in Storybook yet? We partnered with @vitest.dev to build the *best* tool for testing your components in the ways that matter.

👆 Interaction tests
♿️ Accessibility tests
🖼️ Visual tests
🛡️ Coverage reports
🚥 Test widget to run tests automatically

Exciting early success with component testing for @react.dev server components (RSC) in @vitest.dev by @kasperpeulen.bsky.social!

github.com/kasperpeulen...

Accessibility debt adds up fast—especially with limited time, lean teams, and legacy code.

Join @a11ymel.bsky.social (HashiCorp) & @ericwbailey.website (GitHub) for a live session on how to fix A11y debt without burning out your team or blowing up your roadmap.

Registration link in comments 👇

The accessibility pipeline for frontend teams How Storybook 9 integrates accessibility into every part of the development lifecycle

The accessibility pipeline for frontend teams

#accessibility #a11y #frontend

Accessibility debt piles up fast. Fixing it shouldn’t burn out your team.

Join @a11ymel.bsky.social (HashiCorp) and @ericwbailey.website (GitHub) for a live session on how to reduce A11y debt without overwhelming your team.

🗓 July 24, 12PM EDT
🔗 save your spot: us02web.zoom.us/webinar/regi...

Community Showcase (Q2 2025) An update on what the community has been up to in Q2 of 2025

just some of the highlights of the great work the @e18e.dev community has been doing in the last few months. awesome work by everyone involved, and big thanks to all the maintainers who collaborated ❤️

Do I know anyone that is:

- Looking for a new job
- Is an expert in frontend tooling like @vite.dev, Webpack, and custom setups
- Knows a lot about @storybook.js.org
- Loves to help customers
- Works in a Europe-ish timezone

Then come join us as a Senior Solutions Engineer at @chromatic.com!

YouTube video by Chromatic Lessons learned from reducing bloat in Storybook

If you'd prefer to watch a live discussion on this topic, we've got you covered:

youtu.be/h863b0nfsWg

Thanks to @43081j.com and the rest of our friends at @e18e.dev for their help!

Storybook bloat? Fixed. How we cut Storybook’s bundle size in half

We've added a lot of features, and a bit of bloat, over the years. Storybook 9 addressed that concern by removing complexity and reducing the size by half.

🗜️ Cut install size by over 50%
🧹 Overhaul internal dependency structure
📦 Move key addons into core
🪶 Support dev-only “minimal” install

Storybook 9 is leveling up UI testing with Michael Shilman In this episode of PodRocket, Michael Shilman, product lead at Storybook, joins us to explore the major updates in Storybook 9. We dive into component testing, browser mode in Vitest, AI workflows, Re...

Frameworks are shifting. Testing is evolving.
Storybook’s keeping pace—and pushing forward.

🎧 @shilman.net on PodRocket:

✅ Vitest browser mode
✅ Built-in a11y audits
✅ AI dev workflows
✅ RSC + Next.js, Svelte, React Native support

Listen here: podrocket.logrocket.com/storybook-9-...

Promo image saying "How we cut bloat in Storybook", featuring Jeppe and James, Storybook, e18e and Chromatic

This week I'm chatting with @43081j.com from @e18e.dev about how we reduced the bundle size in @storybook.js.org 9, and what we learned from it! 🤩

Come join us! It will be live, it will be fun, and there will be plenty of time for Q&A with the audience. 💬

us02web.zoom.us/webinar/regi...

Tomorrow, we're showing you how we cut 48% of Storybook’s bundle size.

Join Jeppe Reinhold (Storybook core) and James Garbutt (aka 43081j, head of e18e) for a live breakdown with Q&A.

🔗 Grab your spot: us02web.zoom.us/webinar/regi...

Want to cut your app’s bundle size in half?

Storybook just slashed its bundle by 48%. Now the devs behind it—@reinhold.is & @43081j.com —are showing how you can do the same.

✅ What they cut
✅ How to find & fix bloat
✅ What’s next for optimization

📍 Save your seat: us02web.zoom.us/webinar/regi...

🚀 Accessibility Testing is live in Chromatic!

Run a11y checks in Storybook.
Catch regressions in CI.
Track progress in the new dashboard.

Join us tomorrow for a live demo of the full pipeline + AMA.

🗓 July 10 · 12PM EDT

🔗 Sign up here: us02web.zoom.us/webinar/regi...

🚀 Chromatic's Accessibility Testing & Dashboard are now live!

Powered by Storybook & axe, we're making accessibility compliance seamless across your entire dev lifecycle—without slowing you down.

🚀 Accessibility Testing drops next week in Chromatic.

Join us for a live demo + AMA:
See how to catch issues in Storybook, prevent regressions in CI, and track fixes over time—without slowing down your team.

🗓 July 10 · 12:00 PM EDT / 18:00 CET

👉 Save your spot: us02web.zoom.us/webinar/regi...

S1 filing mentions Storybook

whoa we were mentioned in Figma's S1 filing 🤯

The accessibility pipeline for frontend teams How Storybook 9 integrates accessibility into every part of the development lifecycle

Lots more details in the post!

Accessibility dashboard with realtime reports

👀 Keep an eye on new violations with Chromatic’s new Accessibility Regression Testing and reporting

Just starting to tackle a11y issues and overwhelmed with violations? Chromatic allows you to temporarily accept existing violations and continue to track new or updated ones.

Storybook reports a11y test status in the sidebar

🚥 Automate a11y checks in Storybook, CLI, and CI

Make sure you never ship another UI a11y violation.

Automate accessibility checks across all of your stories alongside your component tests. Works in the Storybook app, the CLI (❤️ @vitest_dev), and CI.

Zoomed-in view of a violation's "Copy link" button

🔗 Copy a link to a violation to share with others

Copy a link to the violation you’re looking at with a click. Then share it with your teammates when you have questions or need some help. They’ll see exactly what you’re seeing.

An expanded group of "insufficient color contrast" violations, showing many details including a link to learn how to resolve them

🔧 Fix violations with actionable tips

Each violation provides the details you need to find and fix it, including details about the violating element, a button to jump to it in the canvas, and most importantly, a link to learn more about resolving it.

Storybook's Accessibility addon panel with violations highlighted in the canvas

🔎 Spot issues fast with the redesigned Accessibility addon

Same reliable checks as before with axe-core. Completely rethought to help you find and fix violations more quickly.

And we now automatically detect and wait for animations to finish.

The accessibility pipeline for frontend teams How Storybook 9 integrates accessibility into every part of the development lifecycle

Scrambling to figure out accessibility automation?

Storybook 9 ships an integrated accessibility pipeline. Let’s break down how it all works together from development to CI.

🧵Read on…

we're trying Cynthia :)