[swiley]

Also, making webpages inaccessible usually takes work. Reasonable use of semantic HTML, styling, and alt tags for images are probably good enough. It's when you start doing ridiculous things with SPA frameworks (something no asked for or wants) that this gets hard.

[tiew9Vii]

The art of standard serverside generated HTML and progressive enhancement or a page composed of JavaScript apps/widgets for interactive elements seems lost today. In the age of React everything is a SPA first by design from observations.

Having previously worked and taking a great interest in the schematic web last decade, progressive enhancement, accessibility, page size, etc etc the modern web is disappointing when what should be a simple HTML website instead be a blank white screen while it downloads 2mb+ of assets then a SPA bootstrap to show something loading json blobs embedded in the page and leaking information with the insistence of doing everything client side.

[robertoandred]

SPA frameworks don’t make accessibility any harder.

[extra88]

I disagree. Even if an SPA framework (or more likely a library add-on) does a good job of reinventing the wheels of traditional HTML requests (e.g. announcing the name of the new "page" when it loads and setting focus), there are always going to be more details that will be at least a little harder to implement on each site.

I'm not fundamentally opposed to JavaScript frameworks, even when used to make SPAs. I think their downsides can be worth using them anyway and issues like accessibility can be overcome. They are a paradigm that are chosen too often without enough thought about the downsides and are a bad choice as default.