Accessibility Statement

Dizzy is built with accessibility in mind.

What has been tested?

Dizzy components as a rule target the WCAG 2.1 AA conformance level. This means I aim to provide you with a set of components that just work for all users, regardless of how they interact with the web.

Note, when it comes to authoring accessible components, you should always try to get away with using the least amount of ARIA as possible, as pointed out by the WAI-ARIA Authoring Practices guide, and it's a practice I've stuck to here as well.

AA Conformance

Conformance to WCAG is in some respects a constantly shifting job for you, the end-developer. Although I can provide you with components that I have tested and believe to be, in isolation, fairly accessible for most internet users, I am, at the end of the day, providing you with low-level building blocks that you will combine in new and exciting ways in your own application. This means that when you combine these components together in new ways, it is possible for you to create experiences that are not accessible to all users or do not meet the WCAG AA conformance level.

So long story short, accessibility is extremely important to me, and it's something I take very seriously, and if you purchase a license for Dizzy you can be assured I've done everything I can to make sure the components you're getting have been tested, in isolation, in all the ways I can think of doing. Ultimately, it is up to you to do your own testing on your final application and ensure that your application itself is still meeting the level of accessibility you need.

I would also encourage you to use the W3C accessibility statement generator for your site or application.

Focus Styling

This library makes the decision to define global focus (technically :focus-visible) styles up in the main CSS file in @layer base. One thing that always bothered me about Tailwind is that before Tailwind, no one really defined custom focus styles on a per-component basis. It's like people got their hands on the focus variant and just decided they were supposed to use it on every component differently. Focus styles aren't supposed to be like that. They're not supposed to be beautiful and bespoke. Focus should be a simple ring around every element. That's it. So that is defined at the global level and no components really need to do anything special with it. The only time we use the :focus variant is when that global ring does not work properly on a given component for some reason.

Explore Dizzy