Winnie - a11y member

@bosibori.bsky.social

Lover of Life. Anything web accessibility and Inclusive design #a11y

Code only becomes hard to generate when it's built on existing tech debt that was haphazardly designed. For the longevity of code, it needs to be readable, maintainable, and documented, otherwise you will neither be able to verify it or generate it without a full rewrite

Imagine following AI advice without a second opinion for the sake of “compliance” to avoid legal fines. I heard about a company having an enthusiastic blind customer reaching out about a11y issues. A coworker proposed hiring them. Sadly, the firm rather contracted an infamous a11y company instead.

I'm thinking of a thing in 2026 which is to start a weekly office hour to talk with the web community about anything CSS or design-related. Who is up for that? 😃

Eventually writing code with more bugs in more places that are harder to fix will start to cause major problems that can't be ignored. People will learn the hard way the lesson that should've been obvious from the start: bugs are bad.

While there's valid criticism to make about Tailwind, and I'm even starting to move away from it, some of the tired anti-Tailwind dunks need to die in 2025. Nothing annoys me more than when someone criticizes something worth criticizing but for the wrong reasons. Takes we should all abandon in 2026:

Anyone can make something that looks designed, but that doesn’t mean that design has happened. An interesting essay by Christopher Butler, on, how even if anyone can build a page with a CMS, or ask AI for a design, most people don’t have the fundamentals for good design...

The Fundamentals Problem - Christopher Butler

A few months ago, a client was reviewing a landing page design with my team. They had created it themselves using a page builder tool — one of those

chrbutler.com

I just want the outline property to take two or more outlines instead of just one so we don't have to hack our way around creating better outlines using box-shadow anymore. I'll take this over a few of the fancy new features added to #CSS and that I use less frequently any day. 🥹

Yes, but it isn’t recommended to do so because it can be a very poor user experience. They can make navigation confusing, require more keystrokes to explore layers, lack headers that are meaningful for each section, they can break row/column associations, and increase cognitive load dramatically.

The amount of AI generated art in slides at this conference, primarily used by older scientists, is killing me. Scientists please. Don’t use these ai platforms to make your figures or slides. They look bad and I have yet to see them meaningfully improve the message of talks.