8 ms·
Single page apps and accessibility are completely unrelated concepts. With any app, single page or otherwise, you must take a11y into consideration when designi
by rnicholus 7y ago
Single page apps and accessibility are completely unrelated concepts. With any app, single page or otherwise, you must take a11y into consideration when designing and coding the site. Again, nothing really specific to SPAs here. What you’re complaining about here are designers and developers that don’t strongly prioritize (or understand) UX and a11y. I’ve seen plenty of more traditional multi page/server driven apps with terrible UX and no concern for accessibility. Many, oh so many of those, in fact. And I’ve also seen plenty of SPAs with excellent care for UX and a11y. So, you seem to have an axe to grind here, as nothing you’ve said here is really specific to SPAs. As far as disabling JS... well, I suppose for a static site or one with a simple form that’s certainly something to consider. But otherwise: it’s 2019. Let’s not hold the all web apps back just because some feel the need to block JS. Responsible developers and designers: that’s the goal.
- guitarbill 7y ago> As far as disabling JS... [...] it’s 2019. Ads, tracking, and things like Magecart are still a huge scourge. Meanwhile that SPA isn't such a big "value add" to my life. I agree that devs working with JS need to be responsible, need to accept downsides and the upsides. And they've repeatedly proven they can't be trusted with this when business interests conflict. I realise this probably makes me a luddite, but blocking or tampering with JS, however crude that is, is one of the only avenues left for controlling web content as a consumer.
- lobotryas 7y agoGo ahead and control JS and your web experience. Just don’t complain when sites break because of this and don’t be surpriyed when this very niche case is poorly supported.