FWIW, it's a few years later -- I was able to log in via elinks (a lynx variant used by one of our members), and though the interface was a little messy it worked. Search seemed to not work (or I wasn't using it right), but I could browse. Writing a reply to a post seemed impossible though, as I got "403 forbidden." Have not tried with JAWS or the like yet. I'm not sure if this is on the roadmap to change but here is a quick note that these are the results as of June 2018.

Thanks for devoting some attention to this, appreciate it!

One question - as mentioned, some of my users typically just use email to browse mailing lists and etc. Is it possible to use nodeBB as a listserv in that way? That is, is there a way to get notifications for every new post and comment, and reply via email, etc, like you can with Yahoo groups or Google groups? That would also help with accessibility a bit.

OK, I also see that it's "read-only" in Lynx. I assume that means that people using it won't be able to post, just read the forums. Is that a bug or the desired behavior?

(I can't test it out because, as mentioned, the login doesn't work.)

I'm considering migrating a large forum of around 2000 people from Facebook to nodeBB.

Some of my users are visually impaired, and use a variety of different programs to browse the internet. One person uses Lynx, which is a text-only browser that's easier for her to read. Another uses JAWS, which is a popular screen reader for the visually impaired. Both users tend to supplement with email notifications as needed.

I'm curious just how strong nodeBB's accessibility support is. Searching the archives didn't yield much. This was a dealbreaker when I was considering Discourse, so I'm hoping it's better here.

How do you recommend visually impaired people use nodeBB?