Could you elaborate on how it’s ableist?
As far as I’m aware, not only are they making a version that doesn’t even require JS, but the JS is only needed for the challenge itself, and the browser can then view the page(s) afterwards entirely without JS being necessary to parse the content in any way. Things like screen readers should still do perfectly fine at parsing content after the browser solves the challenge.
Because the easiest solution for them is a simple web scraper. If they don’t give a shit about ethics, then something that just crawls every page it can find is loads easier for them to set up than a custom implementation to get torrent downloads for wikipedia, making lemmy/mastodon/pixelfed instances for the fediverse, using rss feeds and checking if they have full or only partial articles, implementing proper checks to prevent double (or more) downloading of the same content, etc.
Yeah, though I feel like it’s hard to do anything too crazy with a calendar app.
I’d expect larger changes for apps related to music, tools like photo editing ones, photo galleries, etc, since they have a lot more subjectivity as to how they can be designed without it feeling confusing to use.
I have a feeling there’s a reason they picked the calendar app first, and it’s precisely because the changes weren’t hard for them to do comparatively.