Thanks for the mention :) Let's hope that browser vendors won't remove their XSLT implementations: news.ycombinator.com/item?id=4495...

I'd rather go for a real (unstyled) HTML button, as it handles everything out of the box (focusable, correct role, activates on space and enter etc.). You should also add an accessible name for screen readers users (e.g. via aria-label), so they know what the button does when activated.

Hey Cassidy, that's an interesting approach, but unfortuntely not accessible: keyboard users are excluded as they can't open the full-size image.

Is the newsletter available via RSS as well? I've only found a feed for your blog.

Yes, please! The main way I follow other photographers is RSS. Mastodon, Pixelfed, Glass and Flickr support it by default. Blusky supports RSS, but doesn't include images. I've even built myself a tool to grab all the feeds every night and build a single page containing all the photos in one "feed".

Looks good! :)

Thanks for the hint. I thought I would have to host Bluesky on my own domain, but it's just a TXT DNS entry :)

3. Alt text
Bluesky has an inclusion ethos. To be a good blootizen, consider alt text on images and gifs so those using text readers and assistive technology can participate. If you are prone to forgetting like me, turn on a forcing function-

Settings--> Accessibility--> require alt text.

Many platforms support alt text natively (Instagram, Pixelfed, Mastodon). But for the ones that don't, I would leave out the "Link to a photo of" prefix. On a gallery page, the "link" part will be already announced to screen readers. And on a single photo page, there is no link.