[locknitpicker]

> that's just an <a href> link. the only latency is your browser pulling the (admittedly, unnecessarily large) page

I fail to see the relevance of your comment. So you came up with an explanation of why the page might have awful accessibility. How does this make the accessibility problem any better?

> would you prefer some static hydration garbage?

I think everyone would prefer to not wait 3 seconds to get feedback on what they clicked. We're talking about accessibility, right?

[kurisufag]

it's a link. if your browser doesn't have some visual cue that a load is occuring (for me it's a favicon indicator and a visual loading bar) you're having a client issue.

>How does this make the accessibility problem any better?

it's not a UX decision to load slowly on poor uplinks (fwiw it's near-instant on my machine). obviously nobody would /choose/ to do that.

toasts, though, are a definitely conscious UX choice.

[isleyaardvark]

The :active pseudoclass has been used to change the appearance of links since the beginning. (Probably in part because loading links was considerably slower back then.) Not giving links an :active style is a bizarre oversight.