> All users, when possible, should get a basic “minimum functionality” as part of the HTML file. Then, you can progressively layer in enhancements through your CSS and JavaScript.
> If the CSS or JS fail, the user still gets a usable, albeit less flashy, experience.
https://gomakethings.com/progressive-enhancement-the-new-hotness/
Seeing "Photo was not tagged with any alt text" as the default alt text on Pixelfed kind of worries me. Better provide an empty alt tag, no? I'm not a screen reader user, but I wouldn't want to hear this a million times over. #a11y
Bookmarked https://www.nomensa.com/blog/2020/how-build-accessible-cards%E2%80%93block-links.
Promised I’d revisit this, and JavaScript seems like a pretty nifty solution here.
Bookmarked https://a11yproject.com/posts/title-attributes/.
> HTML title attributes are often perceived as an accessibility (and SEO) bonus, but the opposite is true.
Bookmarked: https://sarahmhigley.com/writing/whats-in-a-name/.
> While an improperly added name is a step up from a missing one, it will often give the illusion of accessibility while masking an underlying problem that remains unaddressed.
Bookmarked: https://css-tricks.com/block-links-are-a-pain-and-maybe-just-a-bad-idea/.
Hmm, dang. *adds to to-do list*
> All in all, I’d say block links are just a bad idea.
