Single-page applications are bad for accessibility too and I'd like people to stop making excuses for them.
Conversation
Replying to
SPAs mean breaking all the standard browser functionality and then reimplementing them in ways that are almost never compatible with screen-readers, link discovery, etc.
1
8
Every time I raise these issues I'm told you _can_ fix them therefore SPAs are okay except I've literally never seen a SPA that was as functional as a server-side rendered page w/ minimal or no JavaScript.
I'm including Google et al. here too. If they can't make it work...who?
1
8
Worse, re-implementing that native browser functionality in an extremely hostile (JavaScript) environment that is subject to high churn (frontend devs are turbo-magpies)
1
6
My client gig right now is ripping out a SPA written by relatively elite devs and rewriting the entire product as a traditional web app. This is something I've done before. It's always faster, simpler, everything works better. I have copious examples.
1
14
Show replies
🤷♂️ it's very possible to make a SPA that does everything right. There's been tons that don't. But newer frameworks do a great job in guiding you in the right direction. And the UX gains and app flexibility are totally worth it.
1


