Lmst

@mook OFC I do differenciate between "#WebApps" and #Websites to the point that #AnimateJS et. al. are the de-facto successor to #Flash as #Adobe literally supported it for that reason.

Then again, I think these techniques should be delegated to their specific use-cases (noone expects browser game slites like #Miniclip to be #accessible!) instead.

For a lot of of cases, #JavaScript is mostly unnecessary fluff.

Espechally when said #JS is not doing stuff that adds value but instead just adds #bloat.

I find it espechally insulting when stuff like #Mastodon prevents people from even looking up a profile or post at all cuz that's static content at the time of loading it and there's no legitimate reason to just offer a "lite" UI that just displays an otherwise hidden by #CSS & #JS banner that says sth. like: "this is just a lite preview. Certain functionality will not work, like commenting, boosting or liking. Please use a 3rd party client or activate JavaScript and reload the page if you want to use that."

But I guess that's something Developers at Mastodon are unwilling to accept cuz they have a nonchalant attitude of thinking they are perfect #TechBros!

#NoJSgang

@mook yeah, that's the way to make #accessibility work.

Like even #DuckDuckGo implements this.

And for all those that want to FUD re: DDoS and Scrapers and Bots, there's rate-limiting and blocking connections to counteract this...

TLDR: If a website doesn't work in #LynxBrowsers it's devs are #ableist and should be forced to fix it.

(Cuz there are way to workaround things! I.e. for sites like YouTube it would be perfectly fine to provide a link to a stream that any other application (i.e. #VLC) could just open)...