CSS container queries help us to write a truly fluid components that change based on their container size. In the next few years, we’ll see less media queries and more container queries. In this interactive guide, I will explain the problems they solve, how they work, and how we can use them today in our workflows.

Theming, huh? There’s millions of ways to do it with various levels of complexity. We’ve started a new project which requires heavy, creative theming, so I made a prototype to test some ideas out.

Our 2024 analysis on the accessibility of the top 1,000,000 home pages saw a notable increase in the number of detected accessibility errors, though a small decrease in number of pages with WCAG conformance failures. Despite increased errors, there were several positive trends. Pages with fewer errors in the past generally got better, suggesting that increased focus on accessibility is impactful.

Sometimes, if I’m fixing an unrelated bug I spot the opportunity to make a quick “drive-by” accessibility tweak that is quick and easy and will give a disproportionately big boost to the user experience for people with accessibility needs. Here are some of my top faves.

The disabled attribute is totally fine and should be used when relevant! What’s important is not to use it when the element’s interactivity is necessary to proceed, or when the lack of discoverability is problematic. In these cases, the aria-disabled attribute is better to still convey the same semantics, without impairing on usability.