Re:A Primer for Building Single Page Applications with React
by dagw on Tuesday March 24, 2015 @08:23AM
(#9256112)
Accessibility, SEO and bookmarkable resources aren't always a requirement. The GMail app (as opposed to the login page) for example doesn't need SEO. If you're targeting a known specific audience then you don't necessarily have to focus on accessibility. Bookmarkable resourecs doesn't always make sense either, for example if you're making a web based image editor (although I suppose you could create bookmarks into each images editing history or something if you're doing non-destructive editing) . Maintainability is of course important, but I've yet to see a convincing argument that one approach gives a priori better maintainability.
[ Parent
| on HN ]
Re:A Primer for Building Single Page Applications with React
by bphogan on Tuesday March 24, 2015 @03:31PM
(#9258871)
As a low vision computer user that supports disabled people on the web, and whose father spent 30 years working with disabled people, I can tell you for a fact that for some people, accessibility should be a requirement all the time.
Especially as more things go toward the web.
The disabled is a club anyone here can join, at any time.
Re:A Primer for Building Single Page Applications with React
by bronson on Tuesday March 24, 2015 @09:30PM
(#9260745)
Using the GP's example, it would take a huge amount of effort to make an online image editor accessible to the blind. I'm not sure that would be time well spent.
All the GP is saying is that the trade-offs will depend on your audience.