Topic: Accessibility

These days, the arguments for a baseline font size of 16 pixels are widely accepted. But there are plenty of reasons to go even larger!… More

We’re thrilled to announce that we’ve added accessibility tree snapshots to Pleasantest. These snapshots incorporate important accessibility details into your tests, helping you to understand, track, and maintain the accessibility of your interfaces. We believe Pleasantest is the first testing… More

In Cloud Four’s core values, we state our belief in “the web as a unifying platform to provide access to information for all people of all abilities.” This inspires us to follow best practices (writing semantic HTML, for… More

Pleasantest is a library that integrates with Jest to help you write UI tests that interact with real browsers. It uses Puppeteer to launch and control browsers, Testing Library to find elements on the page, and jest-dom to make assertions… More

Some of the largest sporting goods e-commerce sites don’t provide an accessible experience for sale prices. A few small changes can significantly enhance the experience. More

By leveraging native browser controls, we can make accessible and high-performing components with just a dash of JavaScript. More

Website speed and performance are a question of equity. Fast and lightweight sites mean that everyone can access your content equally. It’s not only an economic imperative; it’s a moral imperative. More

Our accessibility best practices have changed a lot in recent years, which we're reflecting in the next version of our design system. More

If you’ve ever tried to use a CSS transition on an element with the hidden attribute or display: none;, you know this can be a challenge. I’ve run into this problem a number of times and decided to write… More

A loosely organized and inexhaustive list of feedback and suggestions I frequently give designers. More