Accessibility concerns re email, Lynx, JAWS

I hope this vision does not include “getting rid of” all visually impaired people ;).

Seriously though, Discourse should be a great choice for visually impaired, i.e. provide great accessibility – that also means it’s more compatible with alternative input methods (including voice) for anyone. Plus, it would be nice to cut back on some JS for simple reading and poking around, that’ll make Discourse even more accessible and also machine readable and thus crawlable by search engines (and no, SEs do not support JavaScript very well); e.g. make direct links to render on the server (i.e. render first visit on the server) instead of pushing all content including routing to the client and let it figure everything out by itself. This will also make Discourse faster (at least perceived speed, which is the most important measurement even if subjective).

See also the general discussion on JavaScript performance.

1 Like