A fantastic, non-ranty post by @matuzo about the shortcomings of SPAs. This 100 % matches my experience with e.g. Next.js. SPAs are only good for some things and we need to be transparent about what they are *not* good at so that people stop building inaccessible, over-engineered, and slow projects that should have been static sites instead.
https://www.matuzo.at/blog/2023/single-page-applications-criticism/
If your SPA routing is not updating the URL and title of your page, your router is garbage and that's on you, not on SPAs. A SPA must and easily can update your URL, title and tab history with minimal effort nowadays. That's what History API was made for.
You can break accessibility in your site with only a line of CSS. It is not a matter of tools, it is a matter of knowledge and care.
A SPA can be accessible, fast and a joy to users and developers. But you have to make it right and use when it makes sense.
