Hacker News new | ask | show | jobs
by est 909 days ago
> importance of HTML for accessibility

Can we simply say, Javascript driven SPA was a bad fad

2 comments

I'm curious why? I built a JS-driven website and did extensive testing with the screen readers available to me (phone, etc). Adding a few aria properties seemed to work wonders. I think the problem isn't the SPA concept but rather that people don't bother testing. However, a horrible screen reader experience can be achieved without an SPA too and many do.
a well designed JS-driven website is OK, but I've seen too many "learn-react-in-30min" style unnessesary SPA that barely works and buggy bullshit.

To name a few:

- hard-coded buttons disguised as a hyperlink

- customized textbox/dropdown disallow copy-paste

- poorly defined broken URLs and important pages without a proper URL

the first two are just as easily replicated with MPA too.
JavaScript driven SPA is fine as long as everyone remembers that the entire and only point at the end of the day is to create HTML.