4 ms·

> There is no reason why your page should refuse to load plain text without Javascript enabled. Sure there is. You prefer writing javascript and you want to se

> There is no reason why your page should refuse to load plain text without Javascript enabled. Sure there is. You prefer writing javascript and you want to serve your site through a CDN. You might not think that's a good reason, but that's certainly a reason.

Franciscouzo 7y ago
What does a CDN has to do with it?
- Spivak 7y ago
  Because if your application bundle is a fixed asset — like a JS SPA that fetches it’s data from an API then you can distribute your entire application via an inexpensive CDN. As soon as your application bundle is rendered on your servers dynamically then only part of your site can be delivered via CDN. Basically going all-JS gives you an app model where your sever side code doesn’t even know or care about HTML or the web or whatever. It just pushes JSON or whatever around and it largely client independent. Great model when you need to support iOS, Android, web, desktop.
  - deleted 7y ago
    [deleted]
- penagwin 7y ago
  Using a CDN like their talking about likely means your html is static and only served from the CDN. For many SPA's the only actual html is a header, container div, and a call to the app's js. Ignoring the header there might only be say half a dozen lines total.
geggam 7y ago
Until the ADA comes along and demands you create an accessible to the blind site. I've often wondered when the laws would start to be applied and I think its coming
- CalRobert 7y ago
  I have a website that's a full page map. I care about accessibility - is there any way I can make this meaningfully accessible to the blind?
  - gnud 7y ago
    I suspect you're being glib, but you could look at https://wiki.openstreetmap.org/wiki/OSM_for_the_blind https://wiki.openstreetmap.org/wiki/OSM_for_the_blind
  - EpiphanyMachine 7y ago
    Look at WCAG 2 (web content accessiblity guidelines) they specify tags and elements common screen readers will understand to help make you site accessible. This is a really good resource: https://accessibility.18f.gov/ https://accessibility.18f.gov/ A lot of frameworks now have some accessiblity built in if you add the correct attributes.
- lucasmullens 7y ago
  I'm confused. Why would a blind person be any less likely to use JavaScript?
  - geggam 7y ago
    To test for a blind persons ability to render your website a good method is a CLI browser. Neither the blind persons device or a CLI browser will render javascript
    - zaroth 7y ago
      I’m no expert in this space, but if free, common, and easily accessible tools render your site readable and usable, I’m not sure how refusing to use those tools would be a claim under ADA. There are plenty of real ways that sites are unusable by screen readers, using Javascript to download dynamic content shouldn’t be one of them.
    - deleted 7y ago

Franciscouzo 7y ago

What does a CDN has to do with it?

Spivak 7y ago
Because if your application bundle is a fixed asset — like a JS SPA that fetches it’s data from an API then you can distribute your entire application via an inexpensive CDN. As soon as your application bundle is rendered on your servers dynamically then only part of your site can be delivered via CDN. Basically going all-JS gives you an app model where your sever side code doesn’t even know or care about HTML or the web or whatever. It just pushes JSON or whatever around and it largely client independent. Great model when you need to support iOS, Android, web, desktop.
- deleted 7y ago
  [deleted]
penagwin 7y ago
Using a CDN like their talking about likely means your html is static and only served from the CDN. For many SPA's the only actual html is a header, container div, and a call to the app's js. Ignoring the header there might only be say half a dozen lines total.

geggam 7y ago

Until the ADA comes along and demands you create an accessible to the blind site. I've often wondered when the laws would start to be applied and I think its coming

CalRobert 7y ago
I have a website that's a full page map. I care about accessibility - is there any way I can make this meaningfully accessible to the blind?
- gnud 7y ago
  I suspect you're being glib, but you could look at https://wiki.openstreetmap.org/wiki/OSM_for_the_blind https://wiki.openstreetmap.org/wiki/OSM_for_the_blind
- EpiphanyMachine 7y ago
  Look at WCAG 2 (web content accessiblity guidelines) they specify tags and elements common screen readers will understand to help make you site accessible. This is a really good resource: https://accessibility.18f.gov/ https://accessibility.18f.gov/ A lot of frameworks now have some accessiblity built in if you add the correct attributes.
lucasmullens 7y ago
I'm confused. Why would a blind person be any less likely to use JavaScript?
- geggam 7y ago
  To test for a blind persons ability to render your website a good method is a CLI browser. Neither the blind persons device or a CLI browser will render javascript
  - zaroth 7y ago
    I’m no expert in this space, but if free, common, and easily accessible tools render your site readable and usable, I’m not sure how refusing to use those tools would be a claim under ADA. There are plenty of real ways that sites are unusable by screen readers, using Javascript to download dynamic content shouldn’t be one of them.
  - deleted 7y ago