3 ms·
Don't you still have to render server side for crawlers and screen readers (accessibility)?
by stock_toaster 15y ago
Don't you still have to render server side for crawlers and screen readers (accessibility)?
- bill-nordwall 15y agoNope. Screen readers have been able to handle javascript-generated content for years. According to WebAIM's most recent screen-reader survey, 98.4% of screen reader users have javascript enabled: http://webaim.org/projects/screenreadersurvey3/#javascript http://webaim.org/projects/screenreadersurvey3/#javascript
- mmahemoff 15y agoCrawlers, less so. The major search engines are getting smarter about it, but for now, you still need some kind of HTML output from the server if you really want to be indexed properly. It doesn't rule out a pure client-side app at all, but you do have some extra work involved to output HTML from the server. Which is why NodeJS will ride on the coat-tails of this approach; less redundancy.
- techwraith 15y agoHah! "The major search engines" - you mean Google, right? ;)
- eropple 15y agoHow effective is Javascript with screen readers, though? It's been a while since I played with a screen reader (late 2009 or so), but when I did even really simple things like a pop-up div confused it. It didn't inform the user that something new was being rendered or anything.
- bill-nordwall 15y agoSurprisingly effective. A colleague of mine published some techniques to add consistency to Javascript events across screen readers: https://github.com/ryanfitzer/Accessibility https://github.com/ryanfitzer/Accessibility
- jashkenas 15y agoMany of these client-side JS-heavy apps are private "workspace"-like pages ... nothing that would ever need to be indexed by the Googlebot. If you want to serve screen readers, then yes, you need to make sure you're serving only reader-compatible HTML and JavaScript.
- stock_toaster 15y agoYeah, that makes sense.