[adwawdawd]

It will be 150mb when accessible due to even more frameworks.

[reconnecting]

Just on the contrary, critical applications such as government services or banking could provide a light version that just works, maybe a simple HTML/CSS frontend without heavy frameworks to ensure that the service is deliverable.

Once I faced an issue with the SBB ticket system (Swiss rail tickets) that was not working on my iPhone (maybe 8), not in Safari on macOS, and I needed to buy a ticket on the train as in this particular place there was no offline ticket service.

Such services indeed must have a minimal requirements version.

[Piraty]

less javascript + less dynamically loaded/changed content is the solution to web accessibility

[chrisldgk]

Tell that to the developers that are 5 years, 1 million lines and 500 TODOs deep into their legacy React banking frontend. Adding stuff on top of your existing hacks is easy, taking unnecessary code away is hard. Especially if all your training on web accessibility was a one-day workshop where you never actually learned how to do anything, only why you need to do it.

Source: I used a frontend developer working on a big bank frontend. The existing UI stack was horrendous and deadlines and bank politics wouldn’t allow you to refactor anything. Just build shit on top and hope that Jenga tower of a web application doesn’t fall apart halfway there.

[ahofmann]

This is unhinged FUD. I have some websites, that needs to adhere to the new rules. It was fairly easy to do. One of them is a react app with mantine components. I was done in less than a day and have not changed the asset size at all.

[Mashimo]

is that not mostly defined in the HTML part?