note
· · to read

Duplicating this as a separate note since I forgot that Twitter doesn’t accept RSVP posts. There’s a virtual Homebrew Website Club tonight, and I think I’m going to attend. There’s stuff that’s been on the back burner for my websites, (finishing the import of my Facebook archive, for example), and I need to occupy my free time with something. #indieweb

note
· · to read

Spotify is apparently gobbling up podcast platforms, and Anchor is among them. Not that Anchor was particularly open before, but it definitely won’t be open now. given the way Spotify already handles podcasts, this will likely be yet another example of a site death. So, one more time for the folks in the back: Own your content! No, seriously, own your content. It’s one thing to syndicate to Spotify from your own site, because you still have control of the files. Using it as your primary platform, however, (as you will be if you primarily upload to Anchor), is still not a good idea if you care about your content being yours, available for as long as you decide, all of that. Plus there’s a really nasty long-standing bug with Spotify which keeps your feed from being updated if you have to update your original feed for any reason, like you accidentally uploaded the wrong version of a file. So yeah, own your content, because that one’s been around for two years at least and there’s no sign of them fixing it.

note
· · to read

Well WordPress, it seems as though you and I have outlasted a second romantic relationship. I suppose I should be grateful that this one was just under a year while the other was twelve years, but right now it hurts to think and I’m not in the headspace to considere things like that right now. I will get there eventually, but it won’t be today. The unreturned calls and emails and texts after a year of talking nearly every day is just too much. It’s not that I’m angry. It’s worse than that. I wish I could just be angry because that would be a lot easier to take. Right now I’m just crushed.

like

· · to read
Underlines Are Beautiful by Adrian Roselli (Adrian Roselli)
Underlines, the standard, built-in signifier of hyperlinks, the core feature of the web, are beautiful. This is objectively true. They are aesthetically one of the most delightful visual design elements ever created. They represent the ideal of a democratized information system. They are a frail monument to the worldwide reach…

This is probably the most poetic take on link underlines I’ve ever read.

note

· · to read

Dear M-Enabling Summit: seriously, why do accessibility pros have to keep passive-aggressively adding alt text to your images for you? It’s not like this is new or anything. This is, after all, 2019 and not 1995. It’s not even new by Twitter standards, and there are a metric ton of guides out there, some of them even written by accessibility pros, to show you how to use the feature. How is this not in the instructions you provide to your social media manager, assuming you have one? If you don’t, not adding it is even worse. If you can’t manage to do something as simple as adding alt text to your images, why on earth should anyone trust you to create a conference that provides valuable, accurate accessibility information?

read

· · to read
The practical value of semantic HTML by Bruce Lawson
It has come to my attention that many in the web standards gang are feeling grumpy about some Full Stack Developers’ lack of deep knowledge about HTML.

It’s easy to get cranky when semantic HTML is ignored by developers, and that’s usually my cue to quit for the day if possible. This is probably the funniest take I’ve read on the subject of HTML, and I kind of want to steal and modify slightly that footer text and use it on my personal site. This post is also written in a way that allows you to steal the points and add them to your notebook if you’re into that sort of thing.

watch

· · to read

Definitely some very useful information for developers. This stuff is core knowledge that needs to be grasped by developers before getting to the point of using tools or trying to test with assistive technology. I think it’s also useful information for testers as well as assistive technology users, if for no other reason than we are often tasked with doing advocacy work, and it’s to our advantage to try to make sure that the information we’re passing on is accurate so that accessibility problems can be fixed, and not just temporarily. Well, that’s the hope, anyway.