iiinova — where your digital self keeps evolving

Sarah Higley @codingchaos.bsky.social · 08/04/2026

Surprise, I’ve been an eldritch horror all along

120

Sarah Higley @codingchaos.bsky.social · 08/04/2026

Surprise, AI has been an eldritch horror all along

100

Sarah Higley @codingchaos.bsky.social · 07/04/2026

Bonus attempt #2 as a watermark. The date is more reasonable, but still wrong.

A different crop of the same screenshot, showing a different AI-generated attempt at the same seal, this time lighter and as a watermark behind document text. The text in the seal says "The state of Massich" before being cropped, and other indistinguishable text that seems to have the word carolicain in it. This time it has the date 1816, which is at least in the past.

120

Sarah Higley @codingchaos.bsky.social · 07/04/2026

Think I should be worried about the RѤS DĘĀEƃALTH OF MASŢꜺITꝻꝞTTƎ.Ꜭ (est. 2816) revoking my drivers license?

Cropped screenshot of the header an AI-generated court notice for traffic violations from the Commonwealth of Massachusetts. The document text looks official, but The seal in the top left looks vaguely like the massachusetts state seal until you try to read the image's text. The date at the bottom of the seal reads 2816.

140

Sarah Higley @codingchaos.bsky.social · 06/10/2025

There’s also the translation angle 🫠 github.com/w3c/csswg-dr...

130

Sarah Higley @codingchaos.bsky.social · 03/10/2025

There are so many people who take the time to really listen and care and do things well. And then something like CSS carousels comes along and a11y folks end up spending their time and energy on damage control instead of their own a11y spec improvements.

060

Sarah Higley @codingchaos.bsky.social · 03/10/2025

I feel this post deep in my bones, Alice gets right to the heart of why working on a11y in standards can feel like killing your soul by degrees. And also why it’s hard to stop. alice.boxhall.au/articles/a-t...

alice.boxhall.au

A threat model for accessibility on the web - Alice

A explanation of the primary threat to accessibility on the web, and a call to action for the web standards community

1165

Sarah Higley @codingchaos.bsky.social · 26/09/2025

I’m so glad you liked it! It was such a weird experience going last, because I didn’t really get a chance to talk to other folks there about it. Also you’d be a good pick yourself, and @sarasoueidan.com

020

Sarah Higley @codingchaos.bsky.social · 23/09/2025

It’s also pretty common to just invert the foreground/background tokens for a given control in forced colors. All of which should provide an accessible approach to state changes, often better than not adding custom color styling.

010

Sarah Higley @codingchaos.bsky.social · 23/09/2025

Color changes that meet 3:1 contrast are not considered “color alone” by wcag. While you can’t know the contrast of user-selected colors, I think it’s fair to assume they were selected because that user can perceive them.

210

Sarah Higley @codingchaos.bsky.social · 22/09/2025

To be more explicit, as long as this overrides OS-level user caret styles, this is a terrible idea, and really showcases what spec work looks like when a11y isn’t involved at all.

010

Sarah Higley @codingchaos.bsky.social · 22/09/2025

Adrian is wrong about exactly one thing in his post, which is that “when the caret is no longer a stick” is an *excellent* pun. Added to this: in my experience running user tests with low vision users, customizing the caret is actually pretty common as an accessibility affordance.

131

Sarah Higley @codingchaos.bsky.social · 22/09/2025

To be fair, I only considered it because of all the bugs my team gets because of it 😅 It’s one of those fun instances of tension between writing the most accessible UX *now* vs. writing what will remain an accessible UX 😭

100

Sarah Higley @codingchaos.bsky.social · 19/09/2025

If it’s a bug then it might! I think the Edge team handles a lot of the forced colors issues, and they’re all lovely (my post isn’t a dig at them personally, these decisions are old). The issue with backplate is it’s functioning as intended, so there’s nothing to fix from the browser’s POV

100

Sarah Higley @codingchaos.bsky.social · 18/09/2025

For anyone who pays attention to high contrast / forced colors mode styles: I wrote up an explanation of why forced-color-adjust: none is nearly unavoidable and how it sets up your codebase for downstream bugs: sarahmhigley.com/writing/forc...

sarahmhigley.com

forced-color-adjust: none is an unavoidable foot gun | Sarah Higley

A very long treatise on why text backplates were a bad idea. Most of the time.

2188

Sarah Higley @codingchaos.bsky.social · 04/07/2025

Carving weird little guys onto mugs to deal with existential angst

Unfired clay mug with a light purple to green gradient, dark green thin leaves, and an upside down, belly up black tardigrade that somehow looks like it’s smiling

The same mug, from another angle. The handle is to the right and a side-facing tardigrade reaches toward and grasps one of the dark green plant tendrils

A different more squat mug with a light purple to reddish gradient, light green leaves, and three tardigrades popping down from the rim, out from the handle, and up from the bottom

020

Sarah Higley @codingchaos.bsky.social · 09/05/2025

I don’t currently, but I’d be interested in case I do in the future!

110

Sarah Higley @codingchaos.bsky.social · 09/05/2025

This is so much fancier than a brush shoved into a pile of clay, which is where I still am 😅

100

Reposted by Sarah Higley

Frank Elavsky (he/him) ⌁ @frank.computer · 14/04/2025

I've been thinking about accessibility overlays and what it means for personalization quite a lot the past couple of years. I've drafted up some thoughts on it: www.frank.computer/blog/2025/04...