Interesting: The chapters I'm reading today in both "Accessibility for Everyone" by Laura Kalbag & "Sustainable Web Design" by Tom Greenwood are somewhat anti carousals.
They use significantly more energy to render than a grid of thumbnails, and can be tricky to make accessible. So make sure it's worth it!
@alcinnz Carousel is right up there with <marque>, <blink>, and autoplay audio with my top Web haet haet haet
uBlock Origin element blocker and/or Stylish CSS editor.
Immediately.
@dredmorbius Btw <marque> & <blink> can also be recreated using CSS keyframe animations, so it's probably a good idea for me to allow disabling autoplayed animations. I certainly won't support autoplay videos! (Not that I can if I wanted to)
@alcinnz One CSS hack I apply to any GIF image (not alwyas animations, but very nearly so) is to set opacity to 0 unless hovered over.
(This had ... interesting effects ... on a commercial DSL modem before I flashed OpenWRT onto it. One of the key UI buttons was in fact a non-animated GIF.)
I'd like to swap out the image for some placeholder but to date haven't been able to do that. There's :before and :after pseudo-elements, but if the element they're referencing is transparent, so are they.
There are other animation formats, including ... webp and/or webm, and SVG.
SVG is ... a really unfortunate story. So many cool things that can be done with them, so much margin for rampant abuse.
@dredmorbius You know the thing I find interesting about SVG? How long librsvg got away with the most naive of CSS engines! To the degree it called into question the need for CSS styled SVGs.
(Now librsvg has been ported to Rust & uses Servo's CSS engine)
@alcinnz @dredmorbius Concur with the margin for rampant abuse comment. I was disgusted to discover that #SVG includes #JavaScript support, which is why we can't post SVG on most sites -- the site can't trust the general public not to inject malware.
@dredmorbius @resist1984 SVG really seems like it was designed by web browsers saying "we've already implemented CSS & JS elsewhere, so wouldn't be great if we did the same here? We've already got the code!"
Not taking into account they're not the only ones who would want to use a standard vector graphics format.
@resist1984 My sense with this, as well as a lot of technologies, is that it might be addressable through a gradated trust and capabilities model. Though experience suggests that the gradations of trust / capabilities are "none" and "none"....
But if that weren't the case:
Basic SVG with just shape/polygon and colour assignments.
Basic animation and CSS.
Full JS interactivity.
Thinking as I write: sandboxing might be another option, with SVG sandboxed out the wazoo to at least minimise abuse to the SVG itself.
Why is it that every time someone comes up with a "programmable document format" we discover it's a Really Fucking Bad Idea?
MS Word macro viruses in the 1990s. Website JS injection and SVGs in the 2020s.
(I'm not getting old. I am old.)
@alcinnz