Dear accessibility practitioners, please don’t use @medium as your primary publishing platform. Syndicate there if you must, but Medium doesn’t support alt text for images, and has given no indication that it plans to. Its last comment on the subject of alt text was made several years ago and amounts to “Sorry not sorry”. So, avoid Medium as your primary publishing platform, and go with a website of your own that you can control instead. Then, syndicate to Medium.
Read The boring front-end developer by Adam Silver

Cool front-end developers are always pushing the envelope, jumping out of their seat to use the latest and greatest and shiniest of UI frameworks and libraries. However, there is another kind of front-end developer, the boring front-end developer. Here is an ode to the boring front-end developer, BFED if you will.

I’m not saying that a framework or design style is automatically rendered inaccessible simply by virtue of its becoming trendy. It’s worth pointing out though that, if there were less emphasis on using the hottest thing and more on all the very unsexy parts of front-end development, (semantic HTML, properly written CSS, designing with things like color contrast in mind), the web would be a lot less problematic from an inclusive design standpoint.
Demand letters are the single most ineffective tool for creating meaningful improvements with regard to web accessibility, and are the quickest way to torpido the cultural and policy changes which allow technical fixes to be anything more than temporary, surface-level progress. Demand letters serve only to turn accessibility advocates into ambulance chasers. This is a hill I will absolutely die on and anyone who disagrees with me is more than welcome to bring it on.
Read WordPress 5.2: Mitigating Supply-Chain Attacks Against 33% of the Internet by Scott Arciszewski

WordPress 3.7 was released on October 24, 2013 and introduced an automatic update mechanism to ensure security fixes would be automatically deployed on all WordPress sites, in an effort to prevent recently-patched vulnerabilities from being massively exploited in the wild. This is widely regarded by security experts as a good idea.
However, the WordPress automatic update feature had one glaring Achilles’ heel: If a criminal or nation state were to hack into the WordPress update server, they could trigger a fake automatic update to infect WordPress sites with malware.
This isn’t just a theoretical concern, it could have happened if not for WordFence’s security researchers finding and disclosing an easy attack vector into their infrastructure.
WordPress 5.2 was released on May 7, 2019 and provides the first real layer of defense against a compromised update infrastructures: offline digital signatures.

Everybody is swooning over Google’s upcoming automated captions, except zero of the people who actually need them. I have to wondere how it is that as an industry we manage to convince ourselves that we’ve collaborated with people with disabilities on all this amazing new accessibility tech that helps us avoid the obvious solution: Do it right in the first place. I’m sure there were messages across email lists, or surveys, or whatever, with asks for testers, ETC. But the deaf community has been saying for years that automated captions aren’t an optimal solution, and it seems arrogant to me at worst and well-meaningly naive at best that all that advice about automated captions would be ignored for the sake of Google’s business goals. We know what accessibility advancements look like, because people with disabilities have been telling us what they need, for years. Maybe one day as an industry we’ll actually start listening. I’m not holding my breath for the foreseeable future though.