Blog

Internet Explorer dialog: $website is not responding. No, this never fucking happens. At all.

Today’s best spam selections: Tax-free income just for me, and three hook-up notifications.

Some jazz while I finish up the rest of the work day I think.

Friday. It’s finally, finally Friday.

Time for lunch. Hey, it’s early today!

In goes coffee, out comes code. See how easy this is?

It’ll be that feature for Jaws 18 that gets highlighted next year at CSUN, to the horror of accessibility experts everywhere.

Nightmare senario: Blogging, from your screenreader, with the WordPress rest API.

Today we’re going to feed a custom post type with the WordPress rest API. Looking forward to this part, sort of.

Motley Crew while coding.

Ermagerd, content types.

Mmmm coffee. Lots of coffee.

I suppose since I’m not going to fall back to sleep, I might as well get up.

Thanks for hitting up my contact form, but no, I am not going to join your crazy-ass startup that’s invite only, of course.

Come eat some chemicals with me. Come eat some chemicals.

“We are back and ready for another wild alert tonight!” This is what happens when spammers use translation software.

It’s awesome when someone misconfigures their newsletter template and you can see their firstname script break.

$application has stopped working, check for a solution online or close the program. It’s too early for this shit. Why am I awake?

I am going to drink until I can’t distinguish the difference between an accessible and inaccessible website.

Aw crap that moment when you go to pour another cup of coffee, realize the pot’s empty, and have to make more.