3 ms·
The site does have an odd architecture. I can't even find the article text in one of the downloaded files. Kinda looks like they serialized a large JS object in
by sp332 7y ago
The site does have an odd architecture. I can't even find the article text in one of the downloaded files. Kinda looks like they serialized a large JS object into a string inside one of the JS files, wonder if it's in there.
In addition to being un-archivable, it's probably also impossible to use with a screen reader.
Edit: ok I don't really know anything about screen readers. I just miss graceful degradation being a priority of web design.
- dymk 7y agoThe DOM of the loaded page clearly has the article content in it (just right click -> inspect), and is visible to a screen reader.
- komali2 7y agoPop a screenreader on for yourself and see - I just tried and it read the "empty" ember-div div and then stopped. If I have my eyes closed, I have no way of knowing content rendered 20 seconds after it finished (when the text content finally loaded).