I’d rather find out why people abandon a federal application halfway through than build another accordion from scratch. That’s what I like about the U.S. Web Design System (USWDS). It gives teams a head start on accessibility and makes common interactions predictable. Using it still means working through React integration, piecing together documentation, and keeping interfaces consistent across teams. Recent governance changes also raise questions about how future releases will be reviewed. So what does USWDS solve for us, and what do we still have to get right? […]
Its reputation was built on innovation and exceptional design. But decades of late-adopted technologies, questionable UX decisions, and fiercely loyal consumers raise an uncomfortable question: how much of that reputation does Apple still deserve? […]
In this week's "Bad UX for the week" (J/K - I actually don't facilitate a weekly "Bad UX" finds, sorry) – Indeed's 2FA gate (pretty sure it's not only Indeed. Battle.Net does the same).
And here's an example of a rapid UX and accessibility evaluation: https://blog.vernard.net/accessibility-usability-audits/kbh/ "Rapid" because I specifically targeted only 2 flows: homepage and acquisition; but boy, for a rapid one, that was a big catch.
Meta quietly open-sourced Astryx, a design system framework built over eight years and battle-tested across thirteen thousand internal applications. It is not another component library. It is an indictment of every one we have been calling a “system.” […]