4 ms·

My comment is off-topic and likely to annoy people here, but I'll say it anyway: that entire page appears to have been generated in Javascript. If you view sour

My comment is off-topic and likely to annoy people here, but I'll say it anyway: that entire page appears to have been generated in Javascript. If you view source, there is no HTML at all. What would a user with a screen reader hear if he or she were to visit that page? If the page had been written in plain HTML and CSS, it might be about 10-15k in size. At the moment, written in Javascript, it's over 300K in page weight. So both inaccessible and bloated in page weight. This is really bad practice.

epidemian 11y ago
> What would a user with a screen reader hear if he or she were to visit that page? Well, the page still renders paragraphs and titles to good ol' <p>s and <hX>s, so i'd presume a screen reader would just read those things as the page content. Wouldn't it?
- habitue 11y ago
  the screen reader needs to execute the javascript before it can read the tags. I'm not sure if they do that
  - girvo 11y ago
    Most do, thankfully, and have done for a while now :)
danneu 11y ago
Two years ago, 97.6% of screen-reader users surveyed had Javascript enabled. http://a11yproject.com/posts/myth-screen-readers-dont-use-javascript/ http://a11yproject.com/posts/myth-screen-readers-dont-use-ja...
bphogan 11y ago
Depends on the screenreader. And unfortunately, also depends on the screenreader + browser. If the proper HTML tags are used, and role attributes are applied, it should work fairly well. The concern, however, is the weight of the page. But don't let React fool you - they try to do the same thing - rendering HTML with JSX. And the same problems can present themselves there.