4 ms·

Lecturing about accessibility with latency so high that you have no idea if any clicks are actually meaningful. I click "banners" and there's no indication any

Lecturing about accessibility with latency so high that you have no idea if any clicks are actually meaningful. I click "banners" and there's no indication anything is happening until 3 seconds later, when it takes me to a page that doesn't directly talk about banners until later. Then there is a link there that says "banners", and takes me to a different page, 3 seconds later. No indication that anything is happening or waiting during that time.

kurisufag 11mo ago
that's just an <a href> link. the only latency is your browser pulling the (admittedly, unnecessarily large) page -- would you prefer some static hydration garbage?
- locknitpicker 11mo ago
  > 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 11mo ago
    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 11mo ago
      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.
- projektfu 11mo ago
  It's not a real link - some JS magic is happening behind the scenes. Otherwise there would be a confirmation something is happening like the browser's usual spinner.
ErroneousBosh 11mo ago
All of the links respond instantly for me, even on a slow 4G connection. Is it possible that your browser or internet connection are slow?
- projektfu 11mo ago
  I think it is likely that there is a slow/high latency part of the connection. This is usually represented to the user by showing a loading spinner or something like that. However, it is using some partial reloading in the background instead of just following a link, and as a result is not letting the browser tell me that it is loading, and it doesn't have any sign of loading presented otherwise.
  - ErroneousBosh 11mo ago
    It does not appear to be doing partial reloading, it's just serving a page.
    - projektfu 11mo ago
      Then very strange behavior. It does not show active loading.

kurisufag 11mo ago

that's just an <a href> link. the only latency is your browser pulling the (admittedly, unnecessarily large) page -- would you prefer some static hydration garbage?

locknitpicker 11mo ago
> 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 11mo ago
  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 11mo ago
    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.
projektfu 11mo ago
It's not a real link - some JS magic is happening behind the scenes. Otherwise there would be a confirmation something is happening like the browser's usual spinner.

ErroneousBosh 11mo ago

All of the links respond instantly for me, even on a slow 4G connection. Is it possible that your browser or internet connection are slow?

projektfu 11mo ago
I think it is likely that there is a slow/high latency part of the connection. This is usually represented to the user by showing a loading spinner or something like that. However, it is using some partial reloading in the background instead of just following a link, and as a result is not letting the browser tell me that it is loading, and it doesn't have any sign of loading presented otherwise.
- ErroneousBosh 11mo ago
  It does not appear to be doing partial reloading, it's just serving a page.
  - projektfu 11mo ago
    Then very strange behavior. It does not show active loading.