WCAG is evolving. Since 1999, the Web Content Accessibility Guidelines have defined accessibility in binary terms: either a success criterion is met or not. But real user experience is rarely that simple. WCAG 3.0 rethinks the model — prioritizing usability over compliance and shifting the focus toward the quality of access rather than the mere presence of features. Could this be the start of a new era in accessibility?
Over five years ago, I transitioned from architecture to UX design. At the time, the internet was full of think pieces drawing parallels between the two disciplines: how both are about designing systems for people, how architects shape physical spaces while UX designers shape digital ones. I agreed with all of it — and I still do. The conversation largely focused on what UX can borrow from architecture: structure, planning, conceptual thinking.
This topic is especially close to my heart. Over the years, I’ve run close to 100 workshops, coached designers through dozens more, and even created some of my own formats along the way. It’s safe to say I’ve learned a lot about what makes a workshop truly effective (and what doesn’t) — and I’m excited to share some of that with you.
In this article we’ll look at 12 things you can do on your website to make it load faster. But first, let’s take a look at what website performance is all about and how it’s measured.
For years, our industry has debated (and sometimes derided) the concept of the “UX unicorn,” that mythical professional who can do it all: qualitative research, quantitative research, design, content strategy, and more. Over the past decade, we’ve concluded that specialization is more practical, especially as larger design organizations and focused roles became the norm. As AI reshapes our field, we’re seeing an interesting shift: the return of the generalist.
Are you also getting lost in all the files, deliverables, shared docs, PDFs, and reports related to your UX work? What about decisions scattered everywhere between email, Slack conversations, Dropbox folders, SharePoint, Notion, and Figma?
The cursor CSS property affects user experience as they interact with webpage elements. It signals possible actions through visual cues. By adjusting cursor type, developers can indicate if an element is clickable, selectable, or interactive.
Clear navigation is key to a great charity website. In this post, we’ll share five easy steps to simplify a cluttered menu.
Many developers view accessibility as an overwhelming task, requiring a lot of extra effort or specialized knowledge. But a few basic practices can make a significant impact.
Lost in a sea of UX files, docs, PDFs, and scattered decisions across Slack, Dropbox, Notion, and Figma? We talk a lot about organizing Figma, but what about a sensible folder structure for all UX assets? Let’s fix that. Kindly powered by
