My team has fixed over 18 THOUSAND #accessibility violations over the last few months in #Chromatic and we're continuing to make forward progress. SO stoked to see these kinds of results. How did we get so many?
Over the years, we have used our #Storybook as a tool to get excellent coverage of our various components in all their states. Everything from atomic components to full-on pages is captured. We even capture our email templates and #test those!
Capturing all of these states results in a fair amount of duplication (which I'm sure your apps and websites have as well in their reports). If a Button component has four accessibility violations, you will see those propagate to every view or component using that Button (as will your users).
You would be surprised at how many issues are caused by something so small. For example, one of our engineers discovered that changing one line of code led to the fixing of 7,000 violations.
Not only have we been making a concerted effort across our products to improve accessibility, but we also built out some pretty cool tools to aid in that quest...
The combination of Accessibility Regression #testing and the Accessibility Dashboard in #Chromatic are a SOLID combo, especially when paired with #Storybook, and I can tell you with confidence that they are continuing to improve. I can't wait to share a few updates we've been cooking up.

In the meantime, here's a blog post introducing some of our tools. These particular projects are a passion of mine and it's been a privilege to design and help build them. Let me know what you think! Thanks!

https://www.chromatic.com/blog/accessibility-testing-is-here/

Accessibility Testing & Dashboard are live

Introducing our component-driven approach to accessibility

Chromatic